Sample Workflow in Action

Orchestration Trigger

The process for capturing and storing these states is automated in a number of OOTB Dynamic Workflows that are expected to run during normal business workflows. Descriptions of these can be found in the Dynamic Workflows section. It is not expected that these workflows will need to be customized, but an integration is needed to interface with Editor XI and Session Manager XI services to create a custom assignment with an AssignmentType of PatchValidation that will trigger the ADMS Patch Integration orchestration.

Sample WMS Integration workflow

One potential option for creating the custom assignment is through your Work Management System (WMS) that is integrated with a custom Dynamic Workflow. This is the recommended integration for customers using Designer XI as their design tool. These workflow step samples are also available in the Workflows plugin within Solution Center

1. After the design is approved through WMS, continue the workflow through Session Manager and Feeder Services before sending changes to ADMS.

2. Validate ADMS Patch Integration is enabled. This is optional but provides more QA/QC to prevent erroneously triggered workflows.

3. Get the Design and Work Request information from the Design Coordination Service.

4. Create the version and session in Session Manager XI and wait for a response.

Successful Session creation:

1. Persist the version information to the Work Request resource.

2. Push To GIS will make the edits in the version associated with the session

3. Finally, once the edits have been applied, create the custom assignment in the Editor XI service.

Failed Session creation:

In this path, it generates an error message to add to the Draw assignment, then reopens the assignment for a designer to view in DXI and resolve the issue(s).