Validation

The process now needs to be validated to ensure that there are no errors.

The MDM validation plug-in runs in the background as the user modifies or edits the process; it checks that changes are made in accordance with the Validation rules.

Validations are triggered when the destination of the Process is set as MDM.

All errors will show up in the Problems tab of the Properties Window.

The following validations are performed to ensure conformity to MDM standards:

• All Activity Tasks to Web Service: All Activity types should be set to Web Service. Usage of any other activity type will result in an error.
• All Service Tasks to CIM Service: CIM Service should be chosen for all Service Tasks. No other services are supported.
• Single starting point for processThe process should have only a single starting point. Activities which do not have an incoming transitions are considered a starting point.
• Unique Activity Names: Each activity should have a unique name, which is mapped to the MDM activity name.
• Only XOR and Parallel Gateways: Gateway Type should be XOR (Exclusive Decision/Merge Data or Event based) or AND (Parallel Fork/Join). No other Gateway Types are supported.
• Properly defined parameters: Each global Process parameter and data field must have the attributes Direction, Eval, and Type properly and sufficiently defined.
• No Multiple Uncontrolled Transitions: Multiple uncontrolled transitions should not be present since they are not supported by the MDM workflow engine. If there is more than one outgoing transition from an activity, a gateway has to be used.
• Intermediate Event Restrictions: Intermediate events are restricted to exception, timeout, cancel, and Link Event. Use of any other type will result in an error.