Applies to: CommCell administrators
You can use workflows to automate business processes – both CommCell and external – using predefined activities defined in a specific order. You must have administrative permissions on the CommServe server to create and deploy workflows.
Note
-
Only CommCell administrators can create and edit workflows on the Developer tools page.
-
Tenant administrators and end users cannot create and edit workflows. They can execute only the workflows they can access and complete the actions the CommCell administrator assigned on the Manage > Workflows page. For more information, see Running Workflows and Completing Actions.
-
By default, newly installed clients block executables that run outside the installation folder when called from admin-based machines (CommServer, WebServer, WorkflowEngine, or AppMgrlite). The recommended approach is to provide target machine credentials so the client runs under those credentials. If credentials cannot be provided, configure one of the following additional settings on the target machine:
-
sAdminWhiteListPaths - Whitelist specific folder paths
-
sAdminWhiteListBinaries - Whitelist specific executable file names
-
nLimitedAdminAccess - Disable the security feature entirely
Important: Settings with the category Local must be manually entered directly on the target machine. As a safeguard, they cannot be added from the Command Center interface.
For detailed configuration steps and additional information, see Coordinate application tasks with pre-process and post-process scripts.
-
To configure a package installation whitelist from the command line, see Configuring a Package Installation Whitelist.
The Command Center includes predefined workflows, such as the Check Readiness workflow, which checks the connectivity of all the client computers within a client group. You can also create new workflows. Other workflows, such as business logic workflows, are available in the Commvault Store. The workflows in the Commvault Store include a readme that explains the workflow.
Caution
By design, there are no restrictions on the types of queries that administrators can create. However, workflow creators and workflow executors must exercise caution and ensure that no sensitive or confidential information is included in workflow forms.
Additionally, in workflow forms and scripts (such as Onstart and Oncomplete), administrator users have the ability to add custom JavaScript and CSS. It is critical to ensure that any custom JavaScript code does not introduce security vulnerabilities or compromise the integrity of the system.
Capabilities
-
Quickly define business processes using predefined activities, instead of spending hours writing scripts, integrating programs with "glue-code," and building state machines.
-
Use the debug mode to see runtime information and activity inputs and outputs.
-
Design a workflow using a library that contains basic tasks.
-
Create workflows for common tasks and let end users run self-service workflows from the Web Console.
-
Automatically send emails or action items when something needs to be approved or reviewed.
-
Set workflow permissions to control the user actions, such as the ability to run a specific workflow but not modify it.
-
View workflow job history.
-
Manage and troubleshoot workflow jobs from the Job history page.
-
Run workflows as APIs. API Workflows run completely in memory (no job ID is assigned).