Solved

Close document starting point process flow

  • 28 January 2021
  • 4 replies
  • 114 views

Badge

Hello, if i look at our docs page, the following is stated: 

"The ID of the document that has to be closed. If this process action is not a start action, then the value of this parameter will be used to determine which document must be closed. "
https://docs.thinkwisesoftware.com/docs/sf/process_flows.html#close-document

From this you can deduce that a close document step can be modelled as a start action of a process flow. But I cannot get this to work. Is this possible or not?

icon

Best answer by Mark Jongeling 28 January 2021, 13:54

View original

4 replies

Userlevel 7
Badge +23

Hi Bram,

The Close document process action is not a valid starting point for a process flow. I do see that the documentation is misleading and can make you thing it could be a starting point.

We will put a list of valid starting actions onto our documentation page in the near future and change the explanation text of this process action. 

Kind regards,
Mark Jongeling

Userlevel 3
Badge +5

Is there a way to either prevent manually closing a document or triggering an action (alongside with the record_id of the selected record) when a document is closed?

Userlevel 7
Badge +23

Is there a way to either prevent manually closing a document or triggering an action (alongside with the record_id of the selected record) when a document is closed?

Hi Roy,

It is currently not possible to prevent the user from closing documents/screens nor to trigger an action when a document/screen is closed. 

To add, there is an Extended property called 'ShutdownProcedure’ you can use when the GUI gets closed by the user. This is execute the named procedure.

Feel free to create an Idea for this. Do add some examples for when this is handy :wink:

Userlevel 2
Badge +7

Hi Mark

The Extended property probably applies to closing the GUI completely, so the entire application?
Is it somehow possible to link something like that to a specific screen?
We are looking for some kind of "on close-event" so that we can execute a follow-up in a flow after the user closes the (previously opened) input screen. We have now created an extra task for this that the user can start. But if the user does not use this task to close the screen, but simply "clicks away" the screen, the (subsequent) process flow started with this task will of course not be executed.

Reply