Each
workflow defined in SAS Workflow Studio is stored as a
workflow template in XML format. These templates can be opened from or saved to a local file system.
In addition, SAS Workflow Studio supports persistence and versioning of the workflow
templates using SAS Content Services. Finally, users can activate the workflow templates,
which results in uploading the specified version as a formal
workflow definition via SAS Workflow Services for instantiation by end-user client applications.
Note: Template changes made in SAS Workflow Studio do not take
effect until the new version is uploaded and activated. Once activated,
any new instances started use the newly activated version while any
currently running instances continue using their respective version
of the workflow definition.
For details, see Deploying and Maintaining Workflows.
Note: Workflow templates from previous
versions are migrated when they are opened in SAS Workflow Studio,
and you are prompted to verify the migration.
Together, the SAS Workflow Studio and SAS Workflow Services provide the ability to
manage workflows. These workflows can be leveraged by solutions—including CRM, financial
services, risk management, health care, and manufacturing—as platform components for
process automation. Solutions integrate with SAS Workflow Services using technologies
like web services or published Java APIs to launch workflows, receive workflow status
updates, generate notifications and alerts, and monitor workflow progress.
Also, some solutions use the SAS Workflow Administrator web plug-in to enable system
administrators to view active workflow instances.
The following figure illustrates the lifecycle of a workflow from its creation in
SAS Workflow Studio to its instantiation in an application.
CAUTION:
It is strongly
recommended that administrators do not delete workflow templates from
the repository.
Deleting a workflow template can cause unpredictable results when
instance information is accessed and presented using SAS Workflow Administrator.