Deploy a workflow

1. Create the workflow.
   
2. Click the File tab and select the Deploy option.
   
3. The deployment process starts. You can click HIDE to hide the Deployment Started message.
   
4. Your workflow deploys successfully. Click the HIDE link to hide the Deploy Success message.
   
5. To configure the workflow permissions, click the manage permissions... link. This opens Management in a new page where you can set the workflow permissions.
   
6. To return to your workflow, click the File tab.
7. To close the workflow, click the File tab and select Close.

1. When creating your workflow, when you try to deploy it you may see that the option is not available. Take the following workflow as an example. Notice the red exclamation mark on the Claim Rejected Email step.
   
2. Click the File tab and notice the Deploy option is grayed out and you can't click it.
   
3. You are prevented from deploying your workflow if one or more of the step dependencies are missing or are not configured correctly. Click File to return to your workflow. Notice the error on the Claim Rejected Email step. You can use the Error Console to locate existing errors. In this example, the recipient was not configured.
   
4. Add the missing recipient details to the step and then click File. The Deploy option is now available.
   

1. When you create your workflow and you are ready to deploy, you notice a warning message about infinite loops.
   
2. This message indicates that your workflow contains events that loop back on each other and could cause the workflow to get stuck in a loop at runtime, potentially causing performance degradation on your server. Click File to return to your workflow. Use the Error Console to locate the infinite loop. In this example the loop is on the Send Email step.
   
3. You can either fix the infinite loop by redesigning your workflow or you can deploy the workflow with the loop. It is recommended that you resolve the infinite loop. For more information see Infinite Loop.

1. When you create your workflow and you are ready to deploy, you may see a message about missing automatic start events. This message just informs you that you have not integrated your workflow's Start step to something that starts the workflow, such as a form's submit event. You may safely ignore this message if you deliberately did not associate the start step with anything. For example, if you will only ever start the workflow from the Management site manually, nothing is associated with the Start step, and therefore you can safely ignore this message. Click File to return to your workflow, or click the Show Me button to go to the Start step of the workflow.
   
2. On the Start tab on the Configuration Panel, the How will your workflow start? tip shows. To close the tip, click X or GOT IT to close it permanently. In this example, click Got It and configure the start integration.
   
3. If you select Got It, the warning message will not show on the deploy page again. The How will your workflow start? message will also not show on the Start step. To enable this again, go to File > Options and enable Show Start Workflow Tips.

When you deploy workflows from K2 for SharePoint or the Designer, only the person deploying the workflow is granted Admin rights. Any additional Start / Admin / View rights need to be manually configured in Management. All deployment actions use the server Service account. However, all calls to the server are validated using the users credentials.

After deploying a workflow, use the manage permissions... link on the Deploy Success toast message to navigate to Management. From here you need to manually configure the workflow rights.

You need process rights to start workflows, and view workflow reports.

Process rights are permissions assigned to individuals. As the administrator you can control workflow access with these rights.

Process rights consist of the following:

For more information on managing workflow rights and roles see the Manage Workflow Rights and Manage Roles sections within the Workflows topic.