Dynamics AX 7 Workflow
Target Audience & Assumptions:
Experienced Dynamics AX Developers, who already have experience of workflow development at previous versions of AX. Because Article below is highlighting those points which are needed to take care of while developing workflows in AX7. It is not intended to explain the basics of workflow or workflow development. If you need basics, you may start from TechNet or wiki articles. Again, article is highlighting only those changes that you might experience while developing AX7 workflow.
So, let’s start.
-
Start by creating your own model whether selecting an existing package or creating a totally independent isolated package. Best could be creating a new package with ‘selecting an existing package’ such as Application Suite. It’s because of fact that Application Suite is very core for majority of Business Logic of AX7. If you don’t want to create a new package it’s your choice. Ideal choice can be keeping your objects separate of already existing packages.
-
Typically we do add a new field to maintain status of workflow. Here at AX7, no need to add new field directly at table. Instead, create Extension of table and add your custom field in extension of table.
-
At moment when you want to add Workflow Type, by running Wizard, Don’t look at AOT Explorer. This is no more AX 2012. Instead here at AX7, Right click your project and select “Add new Item”; Navigate under “Business Process and workflows” This is the point from where Workflow wizard will start.
-
While adding “Workflow Type” or “Workflow Approval”, don’t expect EP choices. It will not generate menu items for EP. Because EP is no more there.
-
No need to Build Incremental CIL after wizard has finished its work. Instead Rebuild Solution.
-
There is no more Yellow Bar, for workflow submit or other actions. Its new user interface now.
Submit will be a dialog on Right Hand side as shown below.
Got any question or comments, feel free to share.
Comments
-
Hi Zain,
Have you got any solution for the issue. I am facing the same , there is no workflow in the drop down in Workflow Type selection property on the form.
Thanks
Mallika
-
-
Hi Sohaib,
I've created a custom workflow but I am unable to select it on the form I want it activated on. I mean I don't see any workflow in Workflow Type selection property on the form.
Any idea what might be the reason behind it?
-
Hi All
I am getting this error while creating Workflow.
community.dynamics.com/.../231672
Anyone know the solution.
Thanks a lot!
-
Hi Sohib,
We are not receiving notifications(Alert) for the workflow.
Suggestions would be appreciated.
Thanks!
-
-
Sohaib, in AX 7 is it possible to pull up the workflow processor? In AX 2012 and later, this was done in the AOT--> Forms--> Tutorial_WorkflowProcessor. As a consultant, I use this frequently to test workflows right away as opposed to waiting for the workflow batch job to complete.
-
Hi Sohaib,
I'm about to create a new one for sales order approvals but have some challenges to make the "Submit" menu be available on my target form "SalesTableListPage".
Can you share your experience oh hot wo enable the menu?
Thanks a lot!
Georg
-
Hi Sohaib, thanks for this indeed helpful post!
I'm about to create my Sales Order Workflow in AX7 which works fine until I build my VS-Project.
I receive the following error massage (see below)
Are you able to share your VS-Project to check whether I did some mistakes during my Setup?
Thanks a lot!
Georg
//ERROR Massage//
Severity Code Description Project File Line
Error BP Rule: [BPExtensionFailure]:Path: [SalesTableListPage]:The Best Practice extension 'Microsoft.Dynamics.AX.Metadata.Upgrade.Extensibility.Detectors.CustomizedFormPropertiesDetector' did not complete processing due to an internal error. Exception key: 3c517194-363f-4ef0-ab34-c30597f0190b. Details: System.InvalidOperationException: Sequence contains no elements
at System.Linq.Enumerable.Last[TSource](IEnumerable`1 source)
at Microsoft.Dynamics.AX.Metadata.Upgrade.Extensibility.Detectors.CustomizedFormPropertiesDetector.FormControlsChangedDeltaVisitor.GetTop()
at Microsoft.Dynamics.AX.Metadata.Upgrade.Extensibility.Detectors.CustomizedFormPropertiesDetector.FormControlsChangedDeltaVisitor.ReportEnabledChanged(IPropertyChangedDelta propertyChangedDelta)
at Microsoft.Dynamics.AX.Metadata.Upgrade.Extensibility.Detectors.CustomizedFormPropertiesDetector.FormControlsChangedDeltaVisitor.VisitPropertyChangedDelta(IPropertyChangedDelta propertyChangedDelta, IPath path)
at Microsoft.Dynamics.AX.Metadata.Management.Delta.DeltaVisitor.VisitDelta(IDelta delta)
at Microsoft.Dynamics.AX.Metadata.Management.Delta.DeltaVisitor.VisitCompositDelta(ICompositDelta compositeDelta)
at Microsoft.Dynamics.AX.Metadata.Management.Delta.DeltaVisitor.VisitDelta(IDelta delta)
at Microsoft.Dynamics.AX.Metadata.Management.Delta.DeltaVisitor.Visit()
at Microsoft.Dynamics.AX.Metadata.Upgrade.Extensibility.Detectors.CustomizedFormPropertiesDetector.RunChecksOn(AxForm modelElement, AxFormDelta modelElementDelta)
at Microsoft.Dynamics.AX.Metadata.Upgrade.Extensibility.Detectors.AdditiveElementChildDetector`4.RunChecksOn(TModelElement metaObject)
at Microsoft.Dynamics.AX.Framework.BestPractices.BestPracticeFramework.<>c__DisplayClass1f.b__19() PreSalesWorkflows (ISV) [PreSalesWorkflowsGB] J:\AosService\PackagesLocalDirectory\ApplicationSuite\PreSalesWorkflowsGB\AxForm\Delta\SalesTableListPage.xml 0
*This post is locked for comments