Answers:
clarification.
- in the window settings, you need to make it possible to display an additional field for filling (take into account the type of the additional field (if the field is a drop-down list, then display it as a drop-down list). The layout in this case looks like this
- if the names of the buttons are not spelled out or add. the field is not selected, then do not show the specified elements on the form
16.09.2021, 11:52
Original comment available on version: ru
Is a block in the process interface suitable for you with a pop-up setting that will be displayed when the process is opened? Do you need to show this window always or only the first time you opened the process, or is there some kind of condition for displaying this window?
29.09.2021, 11:32
Original comment available on version: ru
1. I hang an action on the stage / procedure for opening a window
2. the transition to the stage / procedure is triggered
3. The actions of the stage/procedure are sequentially performed, we reach the action to open the window, open the window and pause. waiting for the user to enter what is configured in the action for this window
4. the user enters data, the user closes the window, save the entered data in the database, so that they become available in the following steps, proceed to the following steps
29.09.2021, 15:03
Original comment available on version: ru
Unfortunately, this option cannot be implemented.
This option is possible: an action is added to show a window at the stage, as well as a block with window settings is added to the interface settings. When a process is opened on a status that has this action and a configured window, a popup is displayed, if a button is pressed in the window, the data has been written and the interactive window will no longer appear on this status, otherwise it will be displayed every time the process is opened, until this process passes to another stage
Is this implementation right for you?
29.09.2021, 15:50
Original comment available on version: ru
unfortunately this is not at all what was required. for the procedure, as I understand it, this window can no longer be hung. and as I understand it, you are proposing to modify the process interface block, which is not good, since this is no different from the individual settings of the process interfaces. I ask you to look for a solution that can implement exactly the output of the input window through the triggering of an action at a process step or procedure. I am sure that the introduction to the functionality of this tool will seriously expand the functionality of boxing.
30.09.2021, 17:24
Original comment available on version: ru
I can offer an option that can work in boxing
there is a stage XXXX you hang up all the actions you need and an action that shows the window and, based on how you filled the window, switch to another stage in which you already add the actions that you wanted after filling the window.
+ we can make an option that will block the process and give nothing to do with it until the window is filled
in fact, this is all the same as what you want, only divided into 2 stages
30.09.2021, 17:48
Original comment available on version: ru
Added action to step
When this action is on a stage and the process moves to this stage, a popup will be displayed to the user when opening the process without the possibility of closing it. The window will disappear only after pressing one of the buttons specified in the settings
06.10.2021, 18:19
Original comment available on version: ru
in fact, it turns out that in the part "and based on how the window was filled, switch to another stage" does not work. actions are triggered before the window is displayed and after filling in the values in the window and / or pressing the desired button, the actions to switch the stage are no longer triggered. those. you have to manually switch the stage and / or through the procedures when saving, start switching the stages, but for this you still need to force the process to be saved again.
fix it please
03.11.2021, 16:23
Original comment available on version: ru
here it seems like the problem is that the fields must first be filled in, and then work out the actions at the stage so that everything works correctly. But like as discussed above that this is not possible.
I think that a suitable option is to make a status for each button to switch to when pressed, Alexander, think about it)
03.11.2021, 17:22
Original comment available on version: ru
let's make it more versatile. I think it will be even easier to implement.
in this action, please add the field "Run procedure after clicking the button"
I will set up a procedure that
- parse the value of the field
- or just switch to the stage
- or do something else
It is important that the procedure is saved before the procedure is triggered (so that at the time the procedure is triggered in the process, the data entered through the window has already been saved to the database and the flocks are available for processing in it)
can it be like that? Andrey, Maria, how do you like the idea? ))
03.11.2021, 18:28
Original comment available on version: ru
After clicking on one of the buttons of the interactive window, not only saving values will be performed, but also the execution of procedures when editing a process and actions that are triggered when editing a process on the current status (similar to what happens when you click the Save in process button)
22.11.2021, 13:31
Original comment available on version: ru
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment