Hosted Workflows

The Hosted subtab, or workflow family, is the home of hosted workflows which may include the Session Manager workflow, Designer workflow, Feeder Services workflows, and Markup workflow for Mobile.

Hosted workflows can orchestrate business processes. They deal with movement of work across systems (think sending information from Mobile to Designer XI) or Editor XI. These are hosted on shared architecture in Azure. They are capable of things like publishing service bus messages and working with service bus infrastructure. They can be triggered by a scheduled event, or when a specific action happens. The concept of hosted workflows is different from client-side workflows in that client-side workflows take place on a client machine and affect an individual user’s experience within a specific application. An example of a hosted workflow might be the entire Session Manager workflow whereas an example of a client-side workflow might be Open Session from within Editor.

Available Tools

The following buttons are available on all subtabs in Default Workflow Studio. The Studio tab provides a few additional tools. Refer to the Studio topic to learn more.

	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.

Revision history of a workflow is recorded and can be helpful to track changes made to different versions of workflows over time. Refer to the Default Workflow Studio topic to read more about revision history records.

Below is an example of a hosted workflow, the Session Manager workflow.

Workflow Properties

Property	Definition
Name	The title of your workflow.
Minimum Client Version	The minimum version of Editor required to execute this autoupdater workflow. This field only applies to autoupdater workflows on the ArcGIS Server subtab. We recommend leaving this field blank on all other types of workflows.
Workflow Status	Published — the workflow is published and represents the latest version of the workflow. Draft — the workflow is in draft form and not published. Retired — the workflow has been replaced by a newer version and this version is retired and no longer published. Example — this is a workflow example that is useful for copying and pasting into a new workflow as a template or starting point.
Workflow Metadata Id	The unique identifier on each version of a workflow that allows you to call a particular version.
Workflow Ancestral Id	This identifier designates the starting point of a workflow’s history, after which all versions maintain that Ancestral Id.
Version	The version number of the workflow. Useful in tracking the evolution of workflows as administrators make changes.
Updated By	The user name of the last person to modify the workflow. The OOTB workflows provided by Schneider Electric say Updated By Schneider Electric Team, or sometimes say none.
Updated On	The date the last workflow modifications were made.
Expression Language	The coding language that is used within the workflow.