Dynamic Workflows

Feeder Services provides a variety of out-of-the-box workflows that are available for 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 to a coherent solution that solves real business needs for your organization.

All of the example workflows below are available in Default Workflow Studio.

Export and Upload Subnetworks

This workflow serves as the primary dynamic workflow for Feeder Services’s core functionality of running Export Subnetwork to grab data from the GIS and upload it into a GRR. If your tenant has been configured to use zip and upload to SFTP functionality, that happens at the completion of this workflow.

WMS Sample

This example workflow can be found in the Studio tab under View Examples. The purpose of this workflow is to set up an integration between a Work Management System (WMS) and ArcFM to enable an end-to-end WMS-ArcFM-ADMS integration.

Patch Validation Workflow

This workflow acts as the high-level orchestration of the first part of ADMS Patch Integration functionality. This orchestration begins when a custom Assignment with AssignmentType of “PatchValidation” is created by the Editor 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 is available to interface with theEditor service and the Session Manager service to create the custom assignment.

Once an 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 occurs while creating the patches. If the patches are successfully created and uploaded 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. This assignment handles the progression of changes in their versions to DEFAULT, including any changes in markups recorded by field crews.

Finalize Patch Packet

This internal process, which is called by the Patch Validation workflow, is responsible for preparing the last of the information required to send the patch packet to ADMS.

ADMS Status Update Listener

This workflow coordinates messaging from ADMS and updates the status of the patch process. We strongly recommend an early discussion with Schneider Electric prior to implementing customizations of this workflow.

Patch Posted

This workflow 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 that it can expect to be posted to DEFAULT through Geodatabase Manager (GDBM). Once the Session Manager and the GDBM processes complete, a confirmation GRR is requested for each affected subnetwork associated with the patch.

Export and Upload Confirmation Patch

This internal workflow, which is specifically intended to be called by the Patch Posted workflow, is responsible for triggering an update of GRRs for all subnetworks affected by a patch.