Solution Center Configuration

This section covers how to configure autoupdaters for ArcFM Autoupdater XI in Solution Center.

Autoupdaters are configured within the Workflows plugin > Studio tab > ArcGIS Server.

Autoupdaters can be enabled to execute whenever an edit is made. A special type of workflow, called an orchestration workflow, is needed to orchestrate the execution of autoupdaters.

An orchestration workflow controls the autoupdaters to execute and the order in which they are to be run. This orchestration workflow is useful to pass the required parameters to each individual autoupdater, effectively acting as a central repository for all autoupdater configuration.

Once the desired autoupdaters are configured inside the orchestration workflow, they can be associated to one or multiple feature services that have the ArcFM Autoupdater XI SOI enabled. If different feature services require different parameters or various autoupdaters to be executed, then multiple orchestration workflows can be created.

If you prefer to run the provided out-of-the-box autoupdaters, you can grab the example code for an orchestration workflow by clicking View Examples toward the top of the screen. A dialogue appears that provides samples and workflow information.

If you don’t want to run certain portions of the example code above, you can either delete it or comment it out. Numerous comments within the example code provide a great deal of guidance on when to use a certain autoupdater.

Follow these steps to configure additional autoupdaters:

1. Click the Add New button.

2. On the Graph tab, type a name for your orchestration workflow in the Name field.

3. Type the autoupdater code within the entry[ ]; block, and ensure that you set the operational map ID.

   

4. Click the Build button.

5. Click Publish.

Configure an Orchestration Workflow to Execute an Autoupdater

1. Insert a new TriggerAutoupdater node type, using the following code as an example:

     AutoStructureAssociate[ # This is the name of the node
       se_type = TriggerAutoupdater, # This is the node type
       se_workflowMetadataId = "6b0e487b-de06-4b11-96be-3b7945a3e67b", # Autoupdater workflow metadata Id to execute
       se_structureSearchDistance = 50, # Autoupdater specific parameter
       […]
     ];
   

2. Change the se_workflowMetadataId attribute to the Workflow Metadata Id you want to execute.

3. Change your node action execution order to now include your newly created node: entry > AutoStructureAssociate > exit

4. Review the final workflow, as seen in this example:

   digraph finite_state_machine {
     # The "entry" node should be of se_type ApplyEditsTrigger and an se_operationalMapIds attribute should also be present
     entry[
       se_type = ApplyEditsTrigger,
       se_operationalMapIds = "6b140ef6-1ca5-42f8-9151-485c13fe94g1"
     ];
     
     AutoStructureAssociate[ # This is the name of the node
       se_type = TriggerAutoupdater, # This is the node type
       se_workflowMetadataId = "6b0e487b-de06-4b11-96be-3b7945a3e67b", # Autoupdater workflow metadata Id to execute
       se_structureSearchDistance = 50, # Autoupdater specific parameter
       […]
     ]; 
     entry -> AutoStructureAssociate -> exit;
   }
   

   
   

   More parameters can be inserted where you see […] in the code above.

   

5. Click the Build button.

6. Click Publish.