How to auto-close and submit a form (without an User action)

Hi Cedric

One different way of thinking about approaching this might be as follows:

• your current form is in the middle of a process instance
• that process instance was triggered from, say, a Record Summary page
• when a Process instance synchronous thread comes to an end you are returned to where it was triggered i.e. the Record Summary page
• so, in your Record Summary page you could have it auto-refreshing, and displaying a box layout with "Save in progress..." message
• the auto-refresh is fetching data from the database where the status of the save is stored. Depending in what you're saving and how many you could be fetching the status (or statuses) every 30 seconds (that's the fastest auto-refresh rate) and once the status (or statuses) tell you that the save is complete you can then change the message to "Save Complete" or hide the box entirely

As you've discovered the issue with User Input Tasks in process models is that they're expecting input from a User, rather than vehicles for telling you what's going on in the background.

Hope this helps

Stewart

Hello Stewart,

Thank you for these ideas.

The Input task main form is a "start form" that the user has to submit at the beggining of the process, but my second form in a middle of the process is, as you said, just a "box" to display a message.

You idea is great to display saving status to the user (and I will keep it), but does not help me (sorry if I'm wrong), to cut the whole process, into 2 sub process (each less of 50-nodes).

Our process contains too much nodes, so the start form is never closed... but when we cut the process into 2 sub process, it works (if submitted by the user).

But as said Mike... maybe my form (start form) is never closed, because of another issue independant of the 50-nodes limit...

Hello Stewart,

Thank you for these ideas.

The Input task main form is a "start form" that the user has to submit at the beggining of the process, but my second form in a middle of the process is, as you said, just a "box" to display a message.

You idea is great to display saving status to the user (and I will keep it), but does not help me (sorry if I'm wrong), to cut the whole process, into 2 sub process (each less of 50-nodes).

Our process contains too much nodes, so the start form is never closed... but when we cut the process into 2 sub process, it works (if submitted by the user).

But as said Mike... maybe my form (start form) is never closed, because of another issue independant of the 50-nodes limit...