AX2012 Technical Track - Entreprise portal, Czesia Langoswka

Editor's Notes

• #5: An Enterprise Portal site consists of a root SharePoint 2010 products site and collections of subsites. The subsites approximate the features and functionality of the modules in the Microsoft Dynamics AX client. An Enterprise Portal page can include standard Microsoft Dynamics AX Web parts, such as the toolbar, or User Control Web parts that display Microsoft Dynamics AX data. An Enterprise Portal page can also include standard SharePoint 2010 products Web parts, such as lists, announcements, and discussions. Users can modify these Web parts as needed. Note the following information about Enterprise Portal client connections and communications: All browser-based clients and Microsoft Dynamics AX clients access Role Centers through Enterprise Portal. Microsoft Dynamics AX clients use a browser control to display Role Centers. Enterprise Portal uses the Report Web part to display reports that exist on the SQL Server Reporting Services server and are displayed within Role center pages. Enterprise Portal uses ASP.NET user controls and the Enterprise Portal framework to display Microsoft Dynamics AX data and reports. Enterprise Portal uses Windows Communication Framework (WCF) and the .NET Business Connector to interact with an Application Object Server (AOS).
• #6: If you set up and configure Enterprise Portal with Role Centers, Role Center pages can include the following elements: Cues that provide a visual representation of records based on the status of the records. For example, there can be cues for pending sales orders or items that are on backorder. Key performance indicators (KPIs) that provide information from predefined data cubes. You can use this information to monitor business performance against a defined goal. A Report Web part that provides access to SQL Server Reporting Services reports.A Business Overview Web part that displays historical performance, such as year-over-year performance or month-over-month performance. A work list that displays action items generated either by a workflow or by an alert, according to business needs. Community links that provide access to items published on community sites for Finance, Services, and Sales and Marketing. Links that provide access to important internal and external sites.
• #8: Enhancements and improvements in Enterprise Portal for Microsoft Dynamics AX 2012:New SharePoint platform.Enterprise Portal requires Microsoft SharePoint Foundation 2010, which is a free download, or Microsoft SharePoint Server 2010. Improved appearance and behaviorThe following improvements have been made to the appearance and behavior of Enterprise Portal: Improved access to common tasks by using an Action Pane. Enterprise Portal pages include an Action Pane that provides easy access to common tasks. The Action Pane is divided into tabs that can contain button groups. Each button group contains action buttons that you can use to move to other pages and add records to list pages. You can also use the action buttons to perform common tasks for a selected record, such as creating a new sales order for a customer. Developers can customize the buttons available on a user's Action Pane.
• #9: Improved access to information by using FactBoxes. FactBoxes display information related to a selected record, or information displayed in a form or on a list page. Users can customize the type of information displayed in FactBoxes.
• #11: Enhanced integration with Microsoft Excel. Users can export data from grids to Microsoft Excel in static or dynamic mode. In a static export, the data in Excel remains unchanged, unless the user directly modifies the data. In a dynamic export, when the data is refreshed in the database, Excel retrieves the updated data from Microsoft Dynamics AX by using Query Services.
• #13: Show CFO Role CenterGotoSalles moduleShow howfast tabs are behavingfor customerShow unpayedinvoicesShow how we caneasilycreate Sales Order for customer
• #14: No compilation necessary. In earlier versions, you could not install Enterprise Portal on a server where the initialization checklist was not completed. The installation failed, because the Enterprise Portal X++ classes were not previously compiled on the server. You no longer have to compile these classes to install and deploy Enterprise Portal. Improved deployment and administration by using the AXUpdatePortal utility. Microsoft Dynamics AX includes the AxUpdatePortal utility, which you can use to deploy Enterprise Portal on remote servers, create sites, and deploy changes to existing sites. Enhanced AOT support for 32-bit clients. In earlier versions, administrators could not deploy changes to Enterprise Portal from the Application Object Tree (AOT) on a 32-bit client to a 64-bit Windows Server. In this version of Microsoft Dynamics AX, administrators can deploy changes from 32-bit clients to 64-bit clients by clicking a button.
• #15: Enterprise Portal automatically grants and denies access to data and Web pages according to the role-based security framework in Microsoft Dynamics AX 2012. Before users can view data or Enterprise Portal pages, administrators must configure role-based security.This version of Enterprise Portal also supports flexible authentication. Flexible authentication includes Active Directory Federated Services (ADFS), form-based authentication, or Windows Live ID authentication. Flexible authentication can help ease administrative overhead if your organization authenticates many external user accounts in Active Directory.
• #17: Show in Central SharePoint Administration how the Auithentication looks likeandthatFMFBAProvider is enabledRun comand in Dynamics AX Command ShellNew-AXUser -AccountTypeClaimsUser -AXUserId xxx -UserName xxx -UserDomainFMFBAProvider -CreateInProvider -ClearTextPassword “Xyz!!123"Show that user has beenadded on user formShow that we canconnectto EP as added user with Form BasedAuthentication
• #18: • Write Once/ Write Less for List Pages: Customers and partners want to share their development effort as much as possible between Client and EP, so that their work of enabling the application capability in both becomes simpler, easier to maintain, and ensures consistency. We took your feedback and implemented a model-driven, list-page approach that provides a holistic experience to the developers and end users. This is accomplished by basing the entire List Page on the Services infrastructure and reusing the metadata fully from the Application Object Tree (AOT). Developers define the user interface components in AOT one time and write the user interface application logic in a display agnostic way. Both Microsoft Dynamic AX 2012 Client & EP renders the list page using this common metadata and business logic, and reduces the development time and cost. This feature is only available for List Pages in Microsoft Dynamics AX 2012. The Task pages in EP are still being built in Visual Studio using C#.okMorphX EP enhancements: The Microsoft Dynamics AX cross-reference system allows you to see the relationships between objects. You can see which other objects use the current object and also which other objects the current object uses. This is a great tool for rapidly responding to changing business needs. As you make changes to one particular object, you can easily find out the other impacted objects and fix them in one go. In the previous version, EP artifacts in AOT were not covered by the cross-reference system. In this release, we bridged this gap and seamlessly integrated the Web controls developed in Visual Studio and the Web pages developed in SharePoint in their respective nodes with the cross-reference system, so making changes in EP is simpler for developers. Also, the code difference tool works with the EP artifacts in AOT.Visual Studio EP enhancements: The visual studio development experience for EP, Reports, and managed code development are integrated now with one set of tools to ensure consistency and familiarity. The Application Explorer in Visual Studio provides an easy way to pull content from Microsoft Dynamics AX 2012 to Visual Studio. The projects are now saved in AOT, so that the changes are instantly reflected in AOT and EP without the needing the user to manually add it to AOT or deploy to EP during development. Consuming X++ classes in C# are made simpler through the Proxy development project in Visual studio. Proxies could be easily shared between different projects and deployed seamlessly together without any conflict.• Development Environment: Multiple developers can use one shared Web server for development. The templates are deployed in a place where any user who has access to that machine can use it. In the previous version, manual steps were required to enable multi-user development scenario in single box. Developers can now use Windows 7 client 64 bit to develop EP. They no longer need to install a server operating system on their development box.
• #20: To create the list page formIn the AOT, right-click the Forms node, click New Form from template, and then click ListPage. The Forms window opens and shows the new form. Right-click the new form, and then click Properties. The properties window opens. In the properties window, click the Name property of the form, and then enter SampleListPage. Click the InteractionClass property, expand the drop down list, and then click SampleListPageInteraction. To view the display properties of the form, expand the Designs node for the form, and then click Design. In the properties window, click the Caption property, and then enter Sample List Page. Expand the Design node and verify that the form includes an action pane, filter group, and grid control. In the AOT, right-click the SampleListPage form, and then click Save. To add the data sourceThe data source for the list is defined by a query. To specify the query to use with the list page, click the Data Sources node for the form. The data source properties appear in the Properties window. Click the Query property, and then set its value to CustTableListPage. The query and the data sources of that query are added to the form. In the Design node, right-click the grid, and then click Properties. In the properties window, click the DataSource property, and then click CustTable in the drop-down list. Click the Design node. In the properties window, set the DataSource and TitleDataSource properties to CustTable. To add fields to the gridExpand the Data Sources node of the form, right-click the CustTable node under the CustTableListPage query, and then click Open New Window. The CustTable data source appears in a new AOT window. In the window that displays the CustTable data source, expand Fields. Drag the AccountNum, Party, SegmentId, Currency, and PaymTermId fields from the CustTable data source window onto the Grid control of the SampleListPage form. Close the window that displays the CustTable data source. In the AOT, right-click the SampleListPage form, and then click Save. GotoMene items \\ Display andcreate new menu itemRight click and select Deployto EPShow how the Page looks on EPWe canalso show how does it look in Visual Studio 2010 whenthere is still time
• #21: Please do not delete thisslide – On Screen whenpresentationended.