Workflow Wizard's for Dynamics AX 2012
I wanted to write today about Workflows in Microsoft Dynamics AX. Specifically around the Wizard's that now exists for Microsoft Dynamics AX 2012 Feature Pack and beyond. There are several wizard's that help you create the needed artifacts and elements that make up a workflow.
Before getting into the Wizard's, I think it's very important that we look into some very good resources on this topic. So the following is my hot list of resources, I make use of when looking to work with workflow's and create custom workflow's for Microsoft Dynamics AX 2012.
- What's New: Workflow [AX 2012]
- Workflow concepts [AX 2012]
- About Workflow Development [AX 2012]
- Creating Custom Workflows (By Murray Fife)
- My own past post about Workflows & AX 2012
Now with those resource's one should have plenty of information to focus in and get started with the wonderful concept and power workflows bring's to a Dynamics AX 2012 instance.
One area that is new with the release of the Feature Pack for Microsoft Dynamics AX 2012 and beyond is the amount of Wizard's that Microsoft has delivered. We have several actually, and each has their own value point. The idea is around to help decrease your time to value for enabling workflows.
The focus for the wizard's that are delivered is around.: Approvals, Task & Workflow Types. These are each accessed by highlighting the specific type of artifact desired, right clicking, highlighting add-in's, and then selecting the Wizard option from there.
Each will ask a series of question's that will then be used to generate workflow artifacts that relate to specific workflow document classes, and types. This means having the workflow types & categories in place is a must. After understanding this, one can then jump start creating artifacts that fully help model and instance of Microsoft Dynamics AX 2012 for their specific needs.
I will end with this fact, don't under estimate the amount of work that might be required to fully enable a workflow. Depending on the nature of the workflow, and what is required. What should always be the first thing that is done to help with this fact? Solid Functional Design Documents that clearly give finalize & finite scope to the deliverable's that are being targeted.
Well that's all for this post. Check back soon as more to come! Till Next Time!