Skip to main content

All-


I have a client event with 4 destination users where the destination rule options are "Plan per destination" - "All at once". For simplicity there are three actions, approve, reject and forward.


What would happen if one of the destination users decides to forward/redirect the request to another person? Would this be something that I would need to handle throw the API or should there be a line rule for forward?


If there is a line rule for forrward then anyone who approved the request would have to re-approve the request.


What would be the best way to handle this type of problem?


Mike Trouard

It really depends on how "Forwarding" is supposed to work.


If it is only supposed to redirect the individual user's item to someone else, then that sounds like K2's default redirect functionality. This should not be an action or be a line rule. If the users are interacting with their worklist through the Workspace then this is already built-in functionality which the users can do. If they are interacting through some custom interface you've written, then you'll have to make use of the Client API and call the Redirect method on the WorklistItem.


If instead, forwarding is supposed to remove the item from all users worklists and move to a different activity, etc., then this is an appropriate use of an Action/Outcome/Line Rule.


 

If one of the available actions is forward, you could use a suceeding rule like "if at least 1 of Action Result = 'forward'".  Then your line rule could be used to direct to the next appropriate step.  Using this technique the event will be automatically removed from the other three destination users.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings