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

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

cedric02 — Mon, 22 Aug 2022 13:14:55 GMT

Thanks a lot Mike for these further informations.

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

Mike Schmitt — Mon, 22 Aug 2022 13:07:39 GMT

[quote userid="50421" url="~/discussions/f/process/25568/edit-a-process-instance-to-resume-a-write-to-mds-entity-node/99846#99846"]what would be a "Terminated" end node ?[/quote]

That's what it would be. We can usually just say a "terminate node", but some users might hear "end node" and not realize they should *specifically not* use a "terminate" node (which is just an end node with a different configuration), hence my choosing the explicit language in use above.

[quote userid="50421" url="~/discussions/f/process/25568/edit-a-process-instance-to-resume-a-write-to-mds-entity-node/99846#99846"]An end event configured with Result tab set with "Terminate process" ? [/quote]

oh - yes; though i'd think most designers would be very used to using terminate nodes (at least, i hope?!?) - but yes, to be clear, i mean an end node with the "terminate" setting enabled. Hence the way I worded it repeatedly above.

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

cedric02 — Sat, 20 Aug 2022 18:43:17 GMT

Thank you Mike for these precisions.

[quote userid="50400" url="~/discussions/f/process/25568/edit-a-process-instance-to-resume-a-write-to-mds-entity-node/99798#99798"]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.[/quote]

When you say a "Non terminated" end node is a regular one, what would be a "Terminated" end node ?

An end event configured with Result tab set with "Terminate process" ? (just to be sure ;-) )

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

Mike Schmitt — Fri, 19 Aug 2022 18:49:28 GMT

[quote userid="2401" url="~/discussions/f/process/25568/edit-a-process-instance-to-resume-a-write-to-mds-entity-node/99813#99813"]I'm sure in the past I've seen an error when publishing related to some nodes not having an incoming path[/quote]

AFAIK it does do this for nodes without outgoing flows. But I agree, I feel like it used to be different - but alas, no really feasible way to check.

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

Chris — Fri, 19 Aug 2022 18:47:38 GMT

[quote userid="50400" url="~/discussions/f/process/25568/edit-a-process-instance-to-resume-a-write-to-mds-entity-node/99808#99808"]I feel like this might be the only reason that all nodes need an incoming flow in the model itself (i.e. to provide actually predictable starting conditions. i'm not sure what the behavior is, for instance, if such a process is started as a subprocess - do they all still fire, or does something else happen? i'd test and find out, but there are only so many hours in a day lol)[/quote]

Just ran a quick test, same behavior as a sub - all nodes fire..

I'm sure in the past I've seen an error when publishing related to some nodes not having an incoming path, but apparently that's old news..

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

Mike Schmitt — Fri, 19 Aug 2022 18:38:53 GMT

[quote userid="2401" url="~/discussions/f/process/25568/edit-a-process-instance-to-resume-a-write-to-mds-entity-node/99807#99807"]then when started for debugging, all nodes fire..[/quote]

I feel like this might be the only reason that all nodes need an incoming flow in the model itself (i.e. to provide actually predictable starting conditions. i'm not sure what the behavior is, for instance, if such a process is started as a subprocess - do they all still fire, or does something else happen? i'd test and find out, but there are only so many hours in a day lol)

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

Chris — Fri, 19 Aug 2022 18:37:01 GMT

[quote userid="50400" url="~/discussions/f/process/25568/edit-a-process-instance-to-resume-a-write-to-mds-entity-node/99801#99801"]...but since we don't need to connect them to an incoming flow, why even do that? Just add it and provide an end event, then start it manually? Or are you handling some other special use case in this way?[/quote]

I do this purely because I did not know that in an already-running instance, nodes do not need an incoming flow...... No other use case, news to me! 🙂

I feel like that has not always been allowed, but cannot confirm..

Interestingly enough, I was just able to publish a model in this fashion - then when started for debugging, all nodes fire..

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

Mike Schmitt — Fri, 19 Aug 2022 18:27:55 GMT

[quote userid="2401" url="~/discussions/f/process/25568/edit-a-process-instance-to-resume-a-write-to-mds-entity-node/99796#99796"] I run my data-fixing script tasks off of the Start Event[/quote]

...but since we don't need to connect them to an incoming flow, why even do that? Just add it and provide an end event, then start it manually? Or are you handling some other special use case in this way?

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

Mike Schmitt — Fri, 19 Aug 2022 18:23:02 GMT

[quote userid="50421" url="~/discussions/f/process/25568/edit-a-process-instance-to-resume-a-write-to-mds-entity-node/99794#99794"]You mean adding it "anywhere", but not connected to the others existing nodes ?[/quote]

Correct. When adding it to an already-running instance, it doesn't need to follow anything. This is a handy feature.

[quote userid="50421" url="~/discussions/f/process/25568/edit-a-process-instance-to-resume-a-write-to-mds-entity-node/99794#99794"]what do you mean by "non-terminating end node" ? you mean an "End event" [/quote]

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).

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

Chris — Fri, 19 Aug 2022 17:52:15 GMT

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).

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

cedric02 — Fri, 19 Aug 2022 17:31:23 GMT

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 ?

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

Mike Schmitt — Fri, 19 Aug 2022 15:18:41 GMT

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.

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

deepakg681722 — Fri, 19 Aug 2022 11:09:42 GMT

That's Great.

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

cedric02 — Fri, 19 Aug 2022 10:53:59 GMT

Thank you Deepakg, I understand now my problem : I was in the "Edit process View" window (and no "Monitor process View").

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

deepakg681722 — Fri, 19 Aug 2022 10:39:15 GMT

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.

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

cedric02 — Fri, 19 Aug 2022 09:52:40 GMT

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 ?

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

cedric02 — Fri, 19 Aug 2022 09:46:12 GMT

Thanks a lot Harshit and Deepakg for your replies.

RE: Edit a process instance to resume a Write To MDS Entity Smart Service

deepakg681722 — Fri, 19 Aug 2022 09:39:48 GMT

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.

RE: Edit a process instance to resume a Write To MDS Entity Smart Service

Harshit Bumb (Appyzie) — Fri, 19 Aug 2022 09:39:31 GMT

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"