For each workflow you can set the availability settings (whether the workflow is enabled and displayed on the Self-Service or Helpdesk site) and the language settings.
The language settings allow you to specify a custom name and description of a workflow for the Self-Service or Helpdesk site in the default and additional languages (only the languages to which the Self-Service and Helpdesk sites are localized are available).
To specify language settings
To specify availability settings
You can extend the built-in workflow functionality by creating custom workflows. You can design such workflows that fit your organization’s needs. There are two types of custom workflows: self-service and helpdesk.
To create a custom workflow
When you add a new workflow, it does not have any activities. Fill the workflow with required activities in the workflow designer.
For each workflow, you should specify the name and description in the default language that will be displayed on the Self-Service or Helpdesk site. You can also specify the workflow name and description in other languages (only the languages to which the Self-Service and Helpdesk sites are localized are available). For more information, seeWorkflow Settings.
Import/export workflow functionality allows you to share your configured workflows effortlessly. For example, if you want to use a configured workflow from Management Policy 1 in Management Policy 2, you do not need to manually configure all workflow activities and settings in Management Policy 2. Simply export the workflow from the first Management Policy and import the workflow to the second Management Policy.
Note, that this functionality is available only after you turn on the extensibility features.
To turn extensibility features on
To export workflow
When you import workflows, note that existing workflows with the same name will be replaced. You can back up existing workflows by exporting them when prompted.
|IMPORTANT: When you import workflows, it is strongly recommended to audit scripts of custom activities included in workflows before using workflows in a production environment. This is required because security-sensitive information can be accessed via PowerShell scripts included in a custom activity. Import workflows from a trusted source only.|
|IMPORTANT: If the workflow you are importing contains activities that are missing from the current configuration, import the missing activities first (from the same workflow archive file), and import the workflow itself.|
To import workflow
There are two options to create a custom activity: you can create a custom activity from scratch or convert a built-in activity to custom.
For any custom activity, you can specify a display name, a short name (used to address the activity in scripts), a description (used on the Administration site), and add PowerShell script to the activity. When you create the custom activity from scratch, you can also select user interface elements and enter the main instruction for the page of the Self-Service or Helpdesk site that will be displayed when the activity is executed.
Note, that you cannot specify any user interface elements for custom activities converted from built-in ones. If you want set user interface elements for your custom activity, create it from scratch.
For more information on writing PowerShell scripts for custom activities, refer to the Password Manager SDK.
|IMPORTANT: Note, you can create custom activities only after you turn on the extensibility features. You can turn on the extensibility features on the General Settings tab of the Administration site.|