We have a number of complex workflows available to users through related actions on records. These workflows have many SAIL forms for editing data in a wizard format but we do not persist the data until the users complete the wizard and click save. However, at any point in the flow, users have the ability to exit the workflow by clicking the record view tabs at the top.
How can we disable these record links? I know I could capture who is in the workflow, lock the record in that user's name, and then set visibility on most of the record view links (not related actions) so they wont see anything if they are editing it, but this also doesn't show the links again for them if they did exit and need to go back and edit the record.
Is there not an OOTB way of having the record related action removing the record view buttons for the user int he session they are working the related action?
Discussion posts and replies are publicly visible
Is there any particular reason you don't just let the users re-open tasks they exit via their task list?
Yeah, or use queryProcessAnalytics to see if there is an open task for the record and use a task link if so
The amount of persistent tasks in the system would kill the available memory. We are killing these quick tasks after a bit and closing the processes.
Ca you put a task link in a related action? Call it something like Resume Edits, and set visibility if the queryProcessAnalytics returns a task?
Jacob Edelman said:The amount of persistent tasks in the system would kill the available memory.
Unless the number of tasks you anticipate is in the tens or hundreds of thousands, I don't believe this should be a worry.
Why not just give the user separate controls in the related action task(s), to differentiate between merely saving and actually submitting the edits? The related action would then persist up until a final submit has been confirmed, and any time a user re-opens a related action they had been working on previously, you just re-query their changed data and allow them to continue.
There are that many edits of records on a weekly basis.
Perhaps if we were building this from scratch, but with how it is architected, just looking for a quick way to disable the other record view tabs.
Ah... well, i'm not sure there's any way to actually accomplish that, so it might at some point just have to boil down to being a user training issue.