Friday, November 11, 2011

Differences between different versions of AX (AX 4.0 , AX 2009 and AX 2012) - Part -3

I have already posted 6 sections on the differences between various versions of AX in my previous two posts. In this post, I am going to discuss on the last 3 sections of differences.


Workflow

S.No.
AXAPTA 4.0
AXAPTA 5.0
AXAPTA 2012
1
•Forward only, sequential workflows
•Only interactive elements (tasks and approvals)
•Support for sub-workflows
Expand workflow capabilities by providing broader applicability•Introduce branching
•Introduce automated tasks
•Introduce line-item workflow support
•Introduce parallelism
2
Business user configures workflows using a Microsoft Dynamics AX client form

Improve the workflow editing experience and usability
•Introduce a graphical workflow editor
•Support for “drag-and-drop” of workflow elements
•Familiar property editing experience
3
•Separate workflow component have to be installed
•Requires IIS and .NET Business Connector
•Requires additional security setup
Simplify workflow deployment and installation
•Host the .NET Workflow runtime in AOS
•Separate installation no longer required
4
Workflow server components need to be installed on a web server running Internet Information Services (IIS).
Workflow server components are now automatically installed when installing the Microsoft Dynamics AX AOS. This new deployment significantly simplifies the administrative effort required to set up the workflow infrastructure.
5
Workflow history and the status of an active or completed workflow and its elements that includes data about new workflow features, such as advanced flow-controls, automated tasks, line item workflow, and work item queues can be viewed. This data either in the Microsoft Dynamics AX client or the Enterprise Portal for Microsoft Dynamics AX can also be viewed
6
Includes a new workflow online analytical processing (OLAP) cube, and performance analysis reports built on this cube. These tools can help determine whether a workflow is adding efficiency to your business processes, and provide a means of comparing an automated workflow to the manual processes it replaced. The new performance analysis reports focus on showing how much work was done by using the workflow and how much time that it took to perform the business tasks that comprise the workflow. Using these reports can help you modify your workflows and optimize their performance.
7
The Workflow Editor is a graphical interface that is used to model Microsoft Dynamics AX 2012 workflows by arranging workflow elements similarly to how a business process is graphically modeled using Microsoft Visio. Add, delete, and reposition workflow elements that represent the tasks and approvals that comprise the workflow can be done. Also add flow-control elements, such as manual and automated decisions, automated tasks, parallel activities, and sub-workflows. These improvements can be used to create complex workflows that closely model the business processes that an organization wants to automate.
8
No Flow-Control Elements
Several new elements were added to help you design workflows. These elements will help create workflows that have alternate branches or branches that run at the same time. These elements include the following:
Conditional decision: A point at which a workflow divides into two branches. The system will decide which branch to use by evaluating the submitted document to determine whether it meets a specified condition.
Manual decision: A point at which a workflow divides into two branches. A user must take an action, and the action taken will determine which branch is used to process the submitted document.
Parallel activity: A workflow element that includes two or more branches that run at the same time.
9
No advanced workflow controls
Workflow for Microsoft Dynamics AX 2012 supports advanced workflow flow controls. They include starting and ending elements, manual and conditional decisions, parallel activity and parallel branches, automated tasks, and sequence flows. Business users can now author workflows that correspond more closely to real life business processes using graphical elements that help them to better visualize the process flow.
10
No Automated Task
An automated task is a type of workflow element that does not involve human interaction. For example, an automated task can perform a credit check, run a report, or update a record. The purpose of an automated task is to execute business logic as part of a workflow that is implemented to automate a business process.
11
Assigning a workflow task to a user, role, or organizational hierarchy can be done
Assigning a workflow task to a work item queue. A work item queue is a list of workflow tasks that must be completed. Users can be determined to assign to a queue. Any user assigned to a queue can complete any of the tasks in the queue.
12
No Line-Item Workflows
Workflows for line items on a document can be implemented. By providing support for line-item workflows, workflow now supports more business process scenarios. For example, you might define a workflow for timesheets where each line item on the timesheet is approved by a specific project manager.
A line-item workflow is configured and instantiated for different types of line item records that are related to a header. A header-line workflow can be configured to pause until other workflows are run on any number of line records.
13
No Line-Item Workflow in the AOT
Line-Item Workflow in the AOT: line-item workflows can be enabled for a workflow type inside the AOT so that business users can author a workflow in the Workflow Editor that includes line-item workflows
Analytics
S.No.
AXAPTA 4.0
AXAPTA 5.0
AXAPTA 2012
Implementation Process
1
Two New Cubes:
•The Environmental Sustainability cube provides data that can help you track your organization's energy consumption and greenhouse gas emissions, which your organization can use to be more proactive in its approach to environmental issues.
•The Workflow cube provides data that can help you track the history and current status of business processes in your organization, which you can use to identify processes that have become inefficient and help your business run more smoothly.
2
Financial cubes have been updated for compatibility with Microsoft Dynamics AX 2012 features. This includes support for new budget and ledger transaction tables, unlimited financial dimensions, changes to fiscal calendars, and Microsoft Dynamics AX perspectives.
3
When you disable license or configuration keys, associated columns were removed from tables in the online transaction processing (OLTP) database. As a result:
•Cubes could not be processed because they could not access the columns they were designed to retrieve data from.
•Errors were displayed in reports and Role Center Web parts that used cubes as a data source.
The OLTP database has a fixed schema. This means that when you disable license or configuration keys, associated columns are not removed from tables in the OLTP database. Instead, data is removed from those columns. As a result:
•Cubes can be processed successfully.
•Errors might be displayed in reports and Role Center Web parts that use cubes as a data source. You will need to modify these reports and Web parts so that they no longer try to retrieve data from a column or field that contains no data.
4
Date Dimension and the Gregorian Calendar:
the properties of the Gregorian calendar can be defined by using the Calendar builder form in your Microsoft Dynamics AX client.
To access the Calendar Builder click Organization administration > Common > Calendars > Gregorian calendars.
5
View Support in Perspectives:
custom query definitions were required to perform the following tasks:
•Join tables with complex join conditions.
•Reduce the scope of tables.
•Create measures or dimension attributes using calculated fields.
The Microsoft Dynamics AX 2012 online analytical processing (OLAP) framework supports Microsoft Dynamics AX views in perspectives. The user is able to drag-and-drop Microsoft Dynamics AX views into perspective nodes in the Application Object Tree (AOT) and set the Analysis properties. You can generate an Analysis Services project from a perspective that contains Microsoft Dynamics AX views in addition to tables.
Reporting
S.No.
AXAPTA 4.0
AXAPTA 5.0
AXAPTA 2012
1
The SQL Server Reporting Services architecture in Microsoft Dynamics AX 2012 has been modified to follow a Model-View-Controller (MVC) design pattern variation. This architecture allows many different client types to call Microsoft Dynamics AX 2012 Reporting Services reports including: Microsoft Dynamics AX clients, Enterprise Portal, and Batch Job. This also means that Reporting Services can be replaced by a different application for rendering reports.
2
Microsoft Dynamics AX 2012 reports require SQL Server 2008.
3
Installation and Deployment:
Install the reporting extensions when running the Setup wizard.
Installation and Deployment:
the Setup wizard is changed. It no longer includes an option for installing the reporting extensions.
4
Auto-report wizard to create customized, ad hoc reports. These reports were based on the X++ reporting framework.
Auto-report wizard to create customized, ad hoc reports that are based on the SQL Server Reporting Services framework. To start the Auto-report wizard, click the Print icon on a form.
5
Deploy a report in each specific language.
Deploy the report, and that version will automatically reflect all supported languages.
6
All X++ reports are now migrated to SQL Server Reporting Services. This platform provides users better looking reports, more export formats, and a more capable report designer.
7
X++ framework is used to modify the queries used to retrieve data for reports.
The Reporting Services framework is updated and uses the same functionality. This means filtering and sorting the data on Reporting Services reports can be done.
8
Batch Support:
SQL Server Reporting Services reports in Microsoft Dynamics AX 2012 can now be integrated with the Microsoft Dynamics AX batch framework. This allows to:
•Schedule a long-running report to be printed during off-peak hours.
•Schedule a report to be printed on a recurring-basis.
9
Report Web Parts:
The Web Part used to display reports in Role Centers and other Enterprise Portal pages is updated. This Web Part is renamed from Microsoft Dynamics Report Server Report to Microsoft Dynamics AX Report. The Web Part has also been updated to improve usability. It is now easier to:
•Add the Web Part to a page.
•elect a report to display in the Web Part.
•Select parameters to filter the data displayed on the report.
10
Cross-reference system to view the relationships between objects.
The Cross-reference tool is now updated to work for reports. Like any other object in the AOT, you can right-click Report > Add-ins > Cross-reference tool > Using, and the data source will be displayed. You can also select a data source, such as a query in the AOT, and select Used By, and it will list the report or the reports that use it.

To check my previous two posts. Click the following links....


2 comments:

paragchapre said...

Can you please post the difference between SSRS report in AX 2009 and AX 2012. I know little bit differe nce but in details I dont know.

paragchapre said...

Can you please post what is the difference between SSRS report in AX 2009 and AX 2012.