Skip to main content
C
cedricj425261
August 19, 2022
Question

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

  • August 19, 2022
  • 19 replies
  • 1 view

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

19 replies

harshitb6843
harshitb6843
August 19, 2022

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"

    C
    cedricj425261Author
    August 19, 2022

    for a next time (and for my information), could you explain me why 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?

    is it normal ?

    D
    deepakg681722
    August 19, 2022

    To see the variables of the running instance, you have to go to process details and there will a variable tab. From there you can see the variables.

    D
    deepakg681722
    August 19, 2022

    you can add a new script task just before the writetoDS smart service and i the script task update the required field with the value and start this script task from monitor view. Make sure you close the edit process view before start the script task.

    C
    cedricj425261Author
    August 19, 2022

    Thanks a lot Harshit and Deepakg for your replies.

    mikes0011
    mikes0011
    Brainy
    August 19, 2022

    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.

    The Expression Guru
    C
    cedricj425261Author
    August 19, 2022

    Thank you Mike, that is a very good idea to have a way to control the data, before to resume the process.

    - However, I'm not sure to understand where you would place your new Script Task. You mean adding it "anywhere", but not connected to the others existing nodes ?

    - what do you mean by "non-terminating end node" ? you mean an "End event" node with no trigger ?

    csteward
    csteward
    August 19, 2022

    I use the same theory as Mike.  I run my data-fixing script tasks off of the Start Event most often, you can have the incoming flow from any node that will never be started automatically again (to prevent it from overwriting data later).

    Terms & ConditionsAccessibility statement