Default Workflow Studio

The Default Workflow Studio contains the Schneider Electric-provided workflows. It is akin to a library of provided workflows for you to use as they are, or you can create copies of them in order to manipulate them to suit your company’s needs.

The Default Workflow Studio also comes with default test cases Schneider Electric has used to validate the provided workflows.
Each subtab contains OOTB workflows including Session Manager and Designer Workflows on the Hosted tab, and Autoupdaters on the ArcGIS Server tab.

If you are ready to modify this default workflow, press the Override in Tenant button at the bottom of the interface. This toggles you to the Studio tab, and it creates a draft copy of the workflow from Default Workflow Studio.

IMPORTANT: The functions, tools, and subtabs are the same between the Studio and Default Workflow Studio tabs. For explanations of the tools, see the Studio topic.

Working with Autoupdaters

Autoupdaters are one kind of workflow that an administrator may configure. On the ArcGIS Server subtab, there is a drop-down list of our out of the box autoupdaters (OOTB AUs). Select one of the autoupdaters from the list and note the name field, minimum client version, and status of the AU are displayed along with a button to expand or hide the workflow properties.

The example in the above image uses the Auto Angle Setter autoupdater workflow. The Minimum Client Version field for this autoupdater displays 2025 C1. This means that for this AU to fire, the client must have the Editor XI 2025 C1 version, or newer, installed. If an Editor XI client has an older version, this AU would not fire when GIS edits are made. By contrast, if you select the Update Length AU, the minimum client version is set to 2024 C1 SP1. The minimum client versions for OOTB AUs match the release version in which they were contained.

If you would prefer to set a different minimum client version for any of the autoupdaters that are called in your orchestration, you can select the Override in Tenant button. This transports you to the Studio tab where it makes a copy of the AU workflow, and you can change the minimum client version (or any other property of the AU) and save or publish there. The Minimum Client Version field is not required, and if it is not populated, then the AU attempts to fire no matter the Editor XI client version used.

NOTE: The Minimum Client Version field only applies to autoupdater workflows. Any other type of workflows (for example, orchestrations in the Studio tab) do not use this field.

Once on the Studio tab, While working on your copy of the AU workflow, the title reads Update Length – Draft, for example, and if you hover over the Minimum Client Version field, you’ll see a blue information icon displaying a message warning that your draft AU overwrites the OOTB AU upon publishing.

Once published, the informational icon remains to alert administrators to the fact that this workflow overrides the OOTB workflow.

To the right of the Minimum Client Version field is the status of the AU, and it can show as Draft, Published, or Retired.

Autoupdater Workflow Properties

Within an autoupdater orchestration, AUs can be called by either the Workflow Metadata Id property or the Workflow Ancestral Id property. If you have modified an OOTB autoupdater and do not want any future changes that a new release of Editor XI may make to that OOTB autoupdater, then you can identify your AU inside its orchestration by its Metadata Id. We refer to this as pinning a particular version, or code, of an AU to its orchestration. Administrators should use MetadataId to pin a particular version of an OOTB AU provided in the Default Studio tab, or if a custom version of an OOTB AU has been created in the Studio tab.

If you choose to use the OOTB AUs, then you would identify them inside the autoupdater orchestration by their Ancestral Id. This means that any future modifications made to OOTB AUs would be included in the OOTB AUs called by your orchestration. We refer to this as always using latest of the OOTB AU code.

There is a version field within the properties for workflows. Give your orchestrations a version number if that is helpful to track changes as you modify and evolve the workflows for your organization. Note that Updated By and Updated On fields are populated when changes are made to an orchestration or other type of workflow. This helps provide a history of who worked on each workflow and when. Note that on the Default Workflow Studio tab, OOTB AUs show that they were last updated by the Schneider Electric Team.

These three buttons are available on all subtabs of the Default Workflow Studio.

	Add New button creates a new workflow.
	Refresh button refreshes the list of workflows in the drop-down.
	Show Revision History shows the revision history of the workflow.

Clicking the Show Revision History button displays the history of a particular workflow. An AU workflow that has passed through a number of iterations as an administrator made changes may look similar to this example below.

The latest version of this AU uses a Workflow Metadata ID GUID that starts with 115. You see it is the published version by nature of it being at the top of the workflow history on the left, and the diagram at the bottom of the page showing its status as published. If you click on the second iteration of this AU, identified by its Workflow Metadata ID GUID that starts with 6ea, you can see its status reads as retired.