Hi ​@MatteoSangiorgi,

It might be possible to work with two process flows (or two subflows within the same process flow).

The first flow would end with the "Open document" process action. The user would then read the information from the opened document. Closing this document could then serve as the start process action of the second process/subflow.

However, this is only possible when using a 3-tier environment, since closing a document is not a valid start action for a process flow in the Windows GUI.

If it is important to pass information through process variables, I would recommend using subflows within the same process flow.

Hi  ​@Jeroen van den Belt 

actually , my process flow starts with a Task, that requires user input (barcode reader - requires user ouptut) and  ends with Open Notes → Change filters. 

When document is closed, should start a new barcode reader task. If I drag a process step from change filters (the notes must be filtered for item name) to “barcode reader” task, it’s not possible to read the notes, because task is started .

I tried a subflow, but doesn’t work on Universal Gui.

If i drop Change filters and i add a process step from Open document and subflow, nothing happens.

This is subflow (it requires user input)

​@MatteoSangiorgi I think what Jeroen meant, was using the flow to get to the point it opens the Notes to read and that is the end of Process Flow 1. For Process Flow 2 it will have the remaining steps which should start when closing the document.

I myself have not gotten a process flow to work when the Close Document is a starting point, so I have a question open for this.

If you struggle the same, you could opt for a Task button on that document to start the second flow and close the document in there with the following steps.

It turns out that Close document is incorrectly listed as a valid starting point. I’ve asked our Documentation team to update this information in our Docs. Apologies for any inconvenience this may have caused.

I think that the alternative Mark describes might be a good one — using a task (with or without logic) as the starting point, and then initiating the Close document from there.

Thank you for your feedback ​@Jeroen van den Belt and ​@Mark_Plaggenborg 

I’ve implemented the alternative you suggested.

Now, is it possible to hide the close button? The user must be forced to execute task instead click on close button. The close button should me hidden only for this subject/variant.

I’m implementing a MES , so i need to prevent incorrect user inputs.

Hiding the close button is not something that’s currently supported in the platform in a formal way.

From what I understand, it may be possible to hide the close button using custom CSS. If you give it a try and it doesn’t work out, please let us know.

You can also vote for and share your thoughts on the idea raised by ​@Mark_Plaggenborg, as it aligns with the behavior you originally requested.