Hello community,
I have an interface with tabs as a task.When the task first loads its default is tab 1, witch is fine.The third tab has a link to start another process with a task, once that task finishes the interface refreshes and returns to original interface with default tab 1 (set in the pv as initial value).I would like the tab to be 3 (use save in the interface to save the value to the ruleinput), and have a rule input to set the tab number. But the resume task smartservice (I cant find any documentation regarding this service) has no task input to set the tabnr via the rule-input.Can I update the pv with the tabnumber value via the other process by process id? Or can the the pv with the tabnumber be updated when another tab is pressed but before the form is submitted?
Kind regards,
Erik
Discussion posts and replies are publicly visible
Erik, we had a conversation in another post. I have the feeling that your design could be improved. Is there a specific reason why you do not just submit the task to go to that extra process? Then you can persist your tabs in a process variable and easily return without the need to suspend and resume a task etc.
Hi Stefan,
The main process is unfished and not designed by me, later the check can be sub process and merged into the main process. Several checks can than be linked via chaining. For now I have to demo and kind of reproducing future behavior It works for now, only it would be better if navigated back to the task via resume it would be on the third tab.
Kind Regards,
Got it working without the resume task, could completely remove it, after I chained the task node to the end node it worked, all other nodes were chained, except the last one. That turned out to be the issue.