May I know how to enable the second option in the assignment tab telling this node will run as an unattended activity.thanks
Discussion posts and replies are publicly visible
hi bisheswart9459 advanced options can you go through this link . This would be helpful
A user input task cannot run automatic.
Stefan Helzle there is an requirement that is the add another form value is true then the process should start again from start node , I tried using connection the false part of the last XOR gate to the start node but it is saying we can not add a input flow to the start node and after that I added a user input task but that is not the correct approach . Can you please help me with this scenario .
Start event happens only Once for a process instance.
bisheswart9459 said:should start again from start node
You want a new process instance or You want to start from first interface? If you want to start a new process instance use (email or message) triggers for starting new process Instance.
Or If you just want to start from first interface remove start form and place it as User input task and after XOR you connect it to that user input task.
Why not modify the interface to allow adding multiple items?
Simple and easier One
did not get you ,can you explain it in details please !
In your interface, the user should be able to add as many elements as needed.
In that way, the process will be started once, and the user will stay in the interface until all the elements have been added
Is the simplest solution
But that is not my requirement . See the picture above in that picture in that process model at last there is a xor gate that will check one value if the value is false then the process will end but if the value is yes then I need to start the process from first means it will be like a loop if yes then start from first which is my start node .
I guess you can use the suggestion what Stefan and others have mentioned. Having the ability to add multiple values in the interface would be the correct way to do this. You should also rethink about how you design this process model.
If it is just the interface that you are thinking that the user should not see multiple data items at the same time you can use buttons such as "Submit" or "Save and Add another" and have these buttons do the magic on screen, making the user think that the previous form was submitted. Also if you follow this you need to have a null check in the "Cancel" button so that no data that is collected in the previous form is missed from saving but the current screen data should be eliminated.