Skip to main content

After analysis and working on specific requirement we have come to an issue where we are unable to check specific outcome condition which is semicolon separated in K2 4.7 designer while designing workflow.

 

We have a list of data Type A, Type B, Type C, Type D

When user selects Type A it should go to Approver A

When user selects Type B it should go to Approver B

When user selects Type C it should go to Approver C

 

There is flexibility user can select Type A and Type B, Type A and Type C, Type B and Type C and all 3 types. Based on selection it should move to respective approvers if user selects Type A; Type B once approve action is done request should go to Approver A and Approver B.

 

We tried to achieve this in current version of workflow using K2 designer and K2 for Visual studio. We see there is no CONTAINS comparison operator and we have Equal to and Not Equal to and blocking us to achieve this scenario.

 

We may have multiple types and based on type of selection task need to move to respective approvers.

 

Type A1 Type A2 Type A3 to Approver A

Type B1 Type B2 Type B3 to Approver B

Type C1 Type C2 Type C3 to Approver C

 

We can pass user selection to a data field in workflow semicolon separated like

Type A1; Type B3

 

User may select Type A2 Type B3 and click on submit then based on type of selection of type task need to move to Approver A and Approver B respectively.

 

Could you please suggest us how we can achieve this scenario as we will have many combinations of types and cannot be accommodated in all outcome rules in K2 workflow and doesn’t have option Contains to at least check If data field type contains Type A move to Approver A.

To get the most functionality of features designing workflows in 4.7, I would highly recommend using K2 Studio. 

 

Here is a link to opening K2 Studio as well as referencing to other articles on using the advanced features. 

https://help.k2.com/onlinehelp/k2five/userguide/5.1/default.htm#legacydesigntools/k2_studio/create_with_k2_studio.htm

 

If you will be working with more advanced rules and are at a point where an upgrade is possible, I would recommend reviewing K2 Five as the advanced features are merged into desginer. When upgrading, the legacy workflows need to be recreated and this could cause more rework for your team. 

I am not sure I follow your business requirements logic, but that should be possible.  If you have a requirement to put them in a semicolon delemited string then you might investigate the Split function to create a collection where you could evaluate each item.  You can even use the results of a Split in a workflow loop and evaluate each item one at a time.

 

You could also use the output of that split as input to a SmartObject that looks up the destination for that particular item.

 

One thought would be to move complex logic elsewhere than K2 - like a stored procedure or web service that you can call from the workflow via SmartObject. That way, the results of this call can tell the workflow exactly where to go instead of doing a bunch of conditionals within the workflow itself.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings