Studio

On this tab you can modify an existing workflow or create a new one. But first...

You need to review the Acceptable System Use Policy and agree to its terms. Each user is presented with the agreement for each tenant to which they connect. Acceptance of the agreement is required before custom workflows can be created. Users need to accept the agreement only once per tenant, unless future changes are made to the policy that require a new agreement.

After you’ve read through the terms, click Accept to proceed.

Modify a workflow

Select a Schneider Electric-provided workflow on the Default Workflow Studio tab, then click the Override in Tenant button in the lower right. This toggles you to the Studio tab and creates a draft copy of the workflow.

Create a new custom workflow

Select the applicable subtab (or workflow family such as Hosted, Designer Client, ArcGIS Server, etc.), and click the Add New button. We recommend using the examples provided as a starting point. Your initial step is reviewing the following topics:

IMPORTANT: While it is possible to create a new, unique workflow from any subtab (or workflow family), if that new workflow has significant overlap with the OOTB workflows, you could experience both workflows firing simultaneously. To avoid this, we recommend that you choose the OOTB workflow from the appropriate subtab on the Default Workflow Studio tab, and click Override in Tenant. This process tells JobServices to use the new, custom workflow and ignore the OOTB workflow.

NOTE: The Minimum Client Version drop-down can be populated with the release version that your client-side workflow requires to execute. This value is used for autoupdater workflows on the ArcGIS Server subtab, and workflows on the Editor Client subtab, and is ignored on any other type of workflow, including orchestrations.

When you want to customize a client–side dynamic workflow, select an action from the Insert Node Action list. This places the code directly into the codeblock. Then click Publish.

These buttons are available to help while building your workflows:

	The Add New button creates a new workflow.
	The Refresh button updates the list of workflows in the drop-down.
	The Show Revision History button provides the revision history of the workflow. See Default Workflow Studio to read more about revision history.
	View Examples shows Schneider Electric-provided examples of workflows. See Default Workflow Studio to read more on View Examples.
	The Export button launches a dialog that allows you to export any workflow from the subtab (or workflow family) you’re currently on: Hosted, ArcGIS Server, etc. This can be useful when exporting workflows from a test tenant to a production tenant. The workflow exports in the form of a .zip file that uses the naming convention: ArcFM-Workflows-TenantId.zip. Exported workflows from a particular subtab (or workflow family such as Hosted, ArcGIS Server, etc.) are meant to be imported into the same subtab (or workflow family).
	The Import button allows you to locate a .zip file of a workflow you’d like to import. The import tools always import as draft. This allows administrators to review, run test cases, and then publish when ready. The Import tools prevent importing a workflow from a different subtab (or workflow family such as Hosted, ArcGIS Server, etc.). For example, ArcGIS Server to ArcGIS Server is appropriate while ArcGIS Server to Editor Client is not.

If you want to customize client-side dynamic workflows using node actions and triggers, refer to the ArcFM Developer Guide for more information.

If you want to configure autoupdaters, refer to the Editor XI Implementation Guide or Fiber Manager XI Implementation Guide for more information.