Hello community,
Can you help me with configuring start process link so that it refreshes the original interface instead of "ending" in the news tab of tempo?
Once the link is clicked the process that is configured with chaining runs and shows the task, the task just shows information, the task is assigned to initiator.If the task is submitted, the process does end, but I cant see the original interface refresh when I test it.
If I run the test again, the interface shows the information that was previously shown on screen in the task and saved to DB.
Behavior is fine except the reload original interface part.
Kind Regards,
Erik
Discussion posts and replies are publicly visible
Do you test that from the interface designer?
Yes, from the designer
This is the expected behaviour of the interface designer.
Is there a way to test it in a different way? Maybe start the interface via a process?
Yes. Use it in a user input task in a process and start that.
Hello Stefan, tried that but behavior did not change.
I made a process model with a user input task, in the interface of the task, a check/action can be initiated via the start process link, then the result of the check is presented as a task (in the main task) then when accepting the task of the process that was started with the process link, the browser navigates to tempo and the screen of the initial task is "gone", it can be opened via task in tempo and then the interface is indeed updated. But I would like the interface to refresh. Tried to fix this by defining the "check" task as a quick task but that didnt help. Can you help me configure it right?
Please describe what you mean with "then the result of the check is presented as a task (in the main task)".
Maybe text is not a great medium to transport this behaviour. Can you post a video or at least some screenshots of the involved models and how it behaves?
Sure Stefan, can I somehow sent it to you in private because of regulations of the company I work for?
That will not make it any better without an NDA ;-) Try to remove any personal data and references to the client.
Okay will try, first I will try something else. Will check the behavior if I remove the user input task from the process model of the check, because it adds no value other then showing the result, but maybe if I remove the user input task, the result will be shown in the interface the process initiated from via the link. (no user input is needed anyway)
Good idea. And also try to implement a simple test to fully understand the behaviour before making things more complex.
just checked, I got message action completed in Tempo, and again task screen is closed, will check something else, I made a box with the link saved that as an interface and call that interface in a parent interface, maybe must get an output of the process that is being called and show that on refresh of the interface where the link is in. And will search if there is a an example of the start process link, or indeed make a less complicated test process.
Hi Stefan checked the behavior think the reason is because the task of the process that is being called is no part of the process model its being called from. I dont want a forced chained node to complete the check as its optional, so once the link its clicked it starts an instance of a different process-model with a task. If I add a node at the end of the check process model to resume the parent task I think I can achieve what I have in mind. I then need the tp!id of the parent. So try to configure that, can you please inform me how to configure the Definition field of report metric?
found it, just also use the tp!id
This is confusing. Please share screenshots of the models involved.
Got it working, thanks for your help. For now I use the resume task smartservice. When the parent process is more refined the solution will be different I will add the the check process as a sub process to the parent and chain it.
Got it working with the resume task smartservice, but as you mentioned, not the best way. Got it working now without the resume task, turned out the issue was because there was no chain between the task and the end node in the main process.