Prolem with Processnode without ingoing signal

RE: Prolem with Processnode without ingoing signal

Alok Patro — Thu, 17 May 2018 14:45:16 GMT

This is how appian works , all the nodes without any incoming flow starts, so all of the other nodes executes twice. Can you explain why you kept the script task out of the start node flow. Would suggest to keep the script task after the start node so that only a single evaluation occurs.

RE: Prolem with Processnode without ingoing signal

chandu — Thu, 17 May 2018 13:31:15 GMT

Wow,. good catch Bryan, I was thinking that the user has a requirement to do that. when I see ur comment now I realized that the design is not for specific requirement.

RE: Prolem with Processnode without ingoing signal

bryant.st39 — Thu, 17 May 2018 13:10:02 GMT

When you dropped the node, it didnt actually insert it between the two nodes...i think the latest version of Appian addresses this behaviour. To insert the node, you have to delete the connector and reconnect the nodes.

RE: Prolem with Processnode without ingoing signal

tobiasp0001 — Thu, 17 May 2018 13:06:07 GMT

Hi Chandu,
it was an unexpected issue, because I dropped the Script-Task on the flow between Start Node and the "Write to multiple"-Node.
I just realised that I had two entries in my database and then I was confused while pulling the Script node from the flow and there was only an outgoing flow.

And it is new for me, that in BPMN a node without a start node can be triggered automatically.

Thank you

RE: Prolem with Processnode without ingoing signal

chandu — Thu, 17 May 2018 12:56:16 GMT

Hi Tobiasp,
This is working as expected. The script task will require a exit connector. Could you please let us know your requirement?

RE: Prolem with Processnode without ingoing signal

bryant.st39 — Thu, 17 May 2018 12:52:49 GMT

When the process starts, the nodes with no incoming flow initiate as well, meaning the node with 2 input arrows gets exectuted twice (once from the start node and once from the script task) resulting in all remaining nodes being executed twice. To correct this, put an "And" gateway in between the start node and the "Store Application Request Status" node and route the start node and "Script Task" into the "And" gateway or you could just insert the "Script Task" between the start node and "Store Application Request Status" node.