Default Workflow Studio
Default Workflow Studio contains 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.
-
Default Workflow Studio also comes with default test cases Schneider Electric has used to validate the provided workflows.
-
Each subtab represents a type of workflow family that corresponds to a client application, and contains OOTB workflows including, for example, Session Manager and Designer XI workflows on the Hosted tab, and autoupdaters on the ArcGIS Server tab. The node actions available in each workflow family are different.
If you are ready to modify a default workflow, click the Override in Tenant button at the bottom. This toggles you to the Studio tab and creates a draft copy of the workflow from Default Workflow Studio.
Available Tools
The functions, tools, and subtabs are largely the same between the Studio and Default Workflow Studio tabs. However, the Studio tab provides a few additional tools on its subtabs. Refer to the Studio topic to learn about the additional tools.
The following buttons are available on all subtabs in Default Workflow Studio:
 |
The Add New button creates a new workflow. We recommend not using this on the Default Workflow Studio tab as new workflows created here cannot be saved or published. This tab is only for Schneider Electric-provided workflows. |
 |
The Refresh button updates the list of workflows in the drop-down. |
 |
The Show Revision History button provides the revision history of the workflow. |
You can click the Show Revision History button to view the history of a particular workflow.
A workflow that has passed through a number of iterations as an administrator made changes may look similar to the example below, in which the Auto Angle Setter AU workflow (on the ArcGIS Server subtab) is used.
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.
Workflow Properties
Workflow Properties vary between hosted and client-side workflows and can be unique to a specific workflow family. For a description of the property fields, continue reading about the types of workflows you’re interested in.