Dynamic Workflows for Feeder Services

Feeder Services makes use of a variety of Out of the Box workflows that are available on each tenant, though some are only used with certain functionality, like ADMS Patch Integration. These workflows represent the automation logic that ties the numerous pieces of functionality within Feeder Services into a coherent solution that solves real business needs for customers.

Export and Upload Subnetworks

This workflow can be found in the Default workflow studio and serves as the primary dynamic workflow for Feeder Services’ core functionality of running Export Subnetwork to grab data from the GIS and upload it into a GRR. If the tenant has been configured to use the Zip and Upload to SFTP functionality, then that will also happen at the end of this workflow.

WMS Sample

This example workflow can be found in the Studio tab under the View Examples option. The idea behind this example workflow is to provide you with an idea of how you can set up an integration between the Warehouse/Work Management System and the ArcFM solution to enable the whole end-to-end WMS-ArcFM-ADMS integration.

Patch Validation Workflow

This workflow can also be found in the Default workflow studio and acts as the high-level orchestration of the first part of the ADMS Patch Integration functionality. This orchestration begins when a custom Assignment with AssignmentType of “PatchValidation” is created by theEditor XI Service.

IMPORTANT: Since ADMS Patch Validation requires Designer XI or some other Graphic Work Design tool to handle the design work, it is expected that a project implementation or customization will interface with the Editor XI and Session Manager XI services to create the custom assignment.

Once the editor completes the Patch Validation assignment, the workflow handles validating, updating, and exporting the subnetwork changes to ADMS. There is error handling in this portion of the workflow which reopens the assignment if a failure in creating the patches occurs. If the patches are successfully created and shipped to the target SFTP server, ADMS may respond immediately (Rejected) or after a large amount of time (Synced). Once the patches have been synced, the session manager workflow continues by creating an Edit assignment for you to continue to progress the changes in their version to default (this includes any changes due to markups recorded by the field crew).

Finalize Patch Packet

This internal process is called by the Patch Validation Workflow. It is still available for review in the Default workflow studio. Finalize Patch Packet is responsible for preparing the last of the information that is needed to send the patch packet to ADMS.

ADMS Status Update Listener

This simple workflow coordinates messaging from ADMS and updates the status of the patch process. It can be found in the default workflow studio, but we recommend not to customize this without discussing with Schneider Electric first.

Patch Posted

Patch Posted is another of the Default workflow studio workflows. It is responsible for high-level orchestration of the last half of the ADMS Patch Integration functionality. Orchestration begins once an “Approval” assignment is completed. This indicates that a Session/Version associated with a design has been approved by a GIS Approval Officer and can expect to be posted to DEFAULT through GDBM. Once the Session Manager and GDBM processes complete, a confirmation GRR will be requested for each affected subnetwork associated with the patch.

Export and Upload Confirmation Patch

This final workflow is another internal workflow that is available for review in the Default workflow studio. It is only intended to be called by the Patch Posted workflow, and it is responsible for triggering an update of GRRs for all subnetworks affected by a patch.