Edit a process instance to resume a Write To MDS Entity node

Question

Hi, 
 In Production context, a process raised an error on a Write To Multiple DS Entity node because of a mandatory field is set to null. 
 When editing the process, I can see that some process variables are editable ("Modify" button is visible) but the PV for my concern is not editable (type CDT). 
 
 From the link below, I've read that 2 solutions are possible to fix and resume the instance : 
 1/ Creating a new PV, then assigning the latter to the Write To Multiple DS Entity node... 
 (but I don't see any way to add a new PV, as the "variables" tab from process properties is not visible from the monitor process instance view) 
 2/ Using the IFM Manager plugin. 
 What would be the best way (more simple) to correct the process and then resume it please ?

https://community.appian.com/discussions/f/process/13373/how-to-add-a-process-variable-in-already-initiated-process-instance-and-map-this-new-process-variable-to-a-form-input

Mike Schmitt · Accepted Answer

Harshit's answer is correct - if you end up doing this often like me, here's one revision of the technique that I prefer: 
 instead of placing the script task right before the "write..." node, instead just add a script task and follow it with a non-terminating end node. Run the script task to push a new value into whatever CDT field(s) you need to update. Then you can check current variable values in the monitor and ensure they're correct. *Then* just right-click on the WTDS node that originally failed and click "start". The main point here is that it allows you to be sure of your fix before trying the WTDS node again and potentially having another failure and/or writing something you didn't really mean to write, if your script task didn't do what you expected it to on the first try.

Harshit Bumb (Appyzie) · Answer

Hi there, 
 Another way can be to add a script task before the write to M DSE Smart service and in the output tab of that node, construct your CDT and save it in the write PV. After saving it, close the editing window to see the changes in the monitoring window and then start from the script task by right-clicking on it and selecting "Start"

Mike Schmitt · Answer

Unknown said: You mean adding it "anywhere", but not connected to the others existing nodes ? 
 Correct. When adding it to an already-running instance, it doesn't need to follow anything. This is a handy feature. 
 Unknown said: what do you mean by " non-terminating end node" ? you mean an "End event" 
 Yes, a regular end event. When there are active (or failed) nodes in a running instance, a regular (non-terminating) end event won't cause the instance to "complete" in the sense that a parent flow would continue - so non-terminating ends can be used safely when trying to fix instances. 
 I'm emphasizing "non-terminating" here because lots of people (me included) use Terminate nodes in most situations, until a non-terminating one is needed specifically (like in a process flow where some parallel flows might need to end early while the main flow continues).

Edit a process instance to resume a Write To MDS Entity node

Top Replies