SharePoint Workflows Appear in Different Categories After Deployment

  • 16 February 2021
  • 0 replies
  • 5 views

Userlevel 5
Badge +20
 

SharePoint Workflows Appear in Different Categories After Deployment

kbt187362

PRODUCT
K2 Cloud
K2 Five
K2 blackpearl
TAGS
Deployment
Integration
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.

Issue

After deploying a SharePoint solution with workflows created from the K2 Application page in SharePoint, workflows may appear in different categories under the Workflow Server node in Management.

Symptoms

Depending on how the workflow has been created and integrated with SharePoint, the workflow could end up under two possible folder names in Management after being deployed.

1. Workflows created using the 'When a SmartForm is submitted' option

2. Workflows created using the 'When the following events occur' option 

After deploying the solution to a new environment, you may see something similar under the Workflow Server node in Management. 

Source: 

Target: 

Resolution

The folders seen within Management under the Workflow Server node are not actually folder names but rather process folder names. During deployment, the Package and Deployment tool refactors the process folder name for SharePoint workflows. Workflows that are fully integrated with SmartForms have a particular list/workflow setting present that gets used in the refactoring while as other SharePoint integrated workflows do not, so the SmartObject name is used for the refactoring instead. You will need to click the 'Edit...' button for the form in the start event to complete the start wizard which will generate the list/workflow setting.

Considerations

Below are two features related to the category structure seen for workflows within Management. Voting on them will allow you to track when they are released or addressed as well as alert the developers that there is a greater need for these enhancements.


0 replies

Be the first to reply!

Reply