Hey @████████, just chipping in to say this feature would definitely be useful and is high priority for us from an HR perspective.
One of the challenges of building end to end employee onboarding solutions using Laserfiche Forms is that action history is visible to everyone. This requires sub-processes being offloaded to secondary support processes (forms) to keep the action history and comments private.
An intuitive (but granular) way to control who can see the action history would be highly appreciated. My initial thoughts for a quick fix from the discussion above would be a "Hide/show Action History" at the task level?
Something like:
That way we could control who can see the action history at the 'task' level to start with.. This could also be ticked by default making it backwards compatible with historical processes.
I make this recommendation above because it seems like the easiest way to prevent unauthorised users from seeing potentially sensitive action history for their 'tasks' as part of a process..
During a request to recruit process there are parts of the process where non-HR users should have the action history hidden from them.. for example (at a high level):
1) Manager submits request to recruit
2) Task assigned to HR for approval
3) (if approved) Task assigned to Executive Team for financial approval (First non-HR employee who can see entire action history but shouldn't be able to)
4) (if approved) Task assigned to Recruiter to make offer to candidate
5) (if accepted by candidate) Recruiter to upload paperwork
6) Generic IT team member assigned task to set up user in Active Directory (Another non-HR employee who can see entire action history but shouldn't be able to)
7) Assigned to Manager (original initiator) to assign assets to the new user (Non-HR, but entitled to see action history as part of process as they are initiator/manager).
8) Process completed.
Hope that helps with context and I'm looking forward to a fix!
Thanks team!