Modifying ACLs so mentors can see the entire Journey (including LE activities)Modifying ACLs so mentors can see the entire Journey (including LE activities) Relevant for: Journey designer V1+ customers Overview With Journey designer, there are mentors available on the Journeys. Mentors (which can be renamed using the header configurations) when added, will be able to view the Journey page. OOB, they will also be able to view (and edit, if permissions are set accordingly) tasks coming from Journey Accelerator. They will not be able to view tasks, and other activities, coming from Lifecycle Event due to existing security ACLs. Use this document to enable mentors on a Journey (JNY table) to be able to read the underlying Lifecycle event generated tasks and cases. All tables that extend HR Case will need to have a new ACL to allow read access for mentors. All HR Case child task tables for HR Cases that you would like mentors to have read access to will also need a new read ACL like HR Task, Request etc. Note: These changes will provide just read, not edit, access. Other Considerations This document only details the steps to modifying ACLs on the HR case, task, and lifecycle event tables. If you are generating LE cases in other tables, you will need to add ACLs for those as well. First step: Add new ACLs to 'read' on HR Task and HR Case tables Create these ACLs in the appropriate application scope Decision type for these ACLs should be Allow If Open the scripting section by checking the advanced box Read ACL for HR case table Create read ACL for sn_hr_core_case table with script var grCase = new GlideRecord("sn_hr_core_case"); grCase.addQuery('jny_context.mentors', 'CONTAINS', gs.getUserID()).addOrCondition('parent.ref_sn_hr_core_case.jny_context.mentors', 'CONTAINS', gs.getUserID().addOrCondition('parent.parent.ref_sn_hr_core_case.jny_context.mentors', 'CONTAINS', gs.getUserID())); grCase.addQuery('sys_id', current.getUniqueValue()); grCase.setLimit(1); grCase.query(); ansewr = grCase.hasNext(); Read ACL for HR Lifecycle Event case table Create read ACL for sn_hr_le_case table with script var grCase = new GlideRecord("sn_hr_le_case"); grCase.addQuery('jny_context.mentors', 'CONTAINS', gs.getUserID()).addOrCondition('parent.ref_sn_hr_core_case.jny_context.mentors', 'CONTAINS', gs.getUserID().addOrCondition('parent.parent.ref_sn_hr_core_case.jny_context.mentors', 'CONTAINS', gs.getUserID())); grCase.addQuery('sys_id', current.getUniqueValue()); grCase.setLimit(1); grCase.query(); ansewr = grCase.hasNext(); Read ACL for HR Task table Create read ACL for sn_hr_core_task table with script var task = new GlideRecord("sn_hr_core_task"); task.addQuery('parent.ref_sn_hr_core_case.jny_context.mentors', 'CONTAINS', gs.getUserID()).addOrCondition('parent.parent.ref_sn_hr_core_case.jny_context.mentors', 'CONTAINS', gs.getUserID()); task.addQuery('sys_id', current.getUniqueValue()); task.setLimit(1); task.query(); answer = task.hasNext(); Second Step: Modify the 'Restrict query' business rule on the HR case and HR task table according to the screenshots to include mentors Modify Business rule for HR case table sys_id: f65330019f22120047a2d126c42e70fc Add two new lines appended to end of newQuery or conditions newQuery.addOrCondition('jny_context.mentors', 'CONTAINS', userId); newQuery.addOrCondition('parent.ref_sn_hr_core_case.jny_context.mentors', 'CONTAINS', userId); Modify Business rule for HR task table sys_id: d382e6a1c3502200b599b4ad81d3aeff Add two new or conditions to the query, remove semi colon from previous line .addOrCondition("parent.ref_sn_hr_core_case.jny_context.mentors", "CONTAINS", userId) .addOrCondition("parent.parent.ref_sn_hr_core_case.jny_context.mentors", "CONTAINS", userId);