Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
Configuration Required for Adopting Activity
Summary |
---|
This page will detail the configuration required to use Salesforce Activity in Jarvis. Analysis of the current state is still in progress and this page will be updated periodically to reflect new updates and business decisions. |
AQ Activity Report Object
Preventing Users from Adding New Activity Reports
There are two ways to prevent Jarvis Users from Creating new Activity Report records after Salesforce Activities have been rolled out:
Adjusting Permission Sets - TAP currently controls Create, Read, Update, and Delete access to different objects with permissions sets. Removing the Create access from permissions used by standard users which will prevent them from creating Activity Reports on any page layout or when using the Data Import Wizard. This is the best practice approach for managing what users can update in Salesforce.
Removing the New Button from All Page Layouts - The New Button can be removed from all page layouts and related lists for the Activity Report. This is not recommended as there may be exceptional circumstances that require a System Admin to create Activity Reports in the future, removing the New Button would prevent them from doing so. There will be some page layouts that should have the Activity Report buttons removed regardless of what permissions are used but removing them from all page layouts and list views isn’t viable.
Updating existing permission sets that give users access to Activity Reports is the recommended approach for allowing users to read existing Activity Reports and prevent them from creating new records.
Removing AQ Activity Report Buttons from Page Layouts
There are multiple Buttons and Components referring to Activity Reports that should be removed from core page layouts. These need to be identified and recorded here.
Decommissioning AQ Activity Report Flows
There are 5 Flows referencing the AQ Activity Report object. These Flows will need to be decommissioned so its obvious for System Admins that they are no longer in use.
Flow | Purpose |
---|---|
Activity report contact participant | Populates the USYD_contacts_c field on the Activity Report with the contacts listed in the AR Contact Participant |
Creation or updating of activity report user participant | Adds the Owner of the Activity Report to the User Participant related list on the AR if they aren’t already there |
Usyd Copy Email Activity Files to New Activity Report | Copies any Files added when a user syncs an email using the Outlook Integration to the associated Activity Report |
USYD Latest activity report on account | Adds the date of the latest Activity Report to the USYD_Last_Activity_Report_c field on the Account |
USYD Latest activity report on account (delete trigger) | When the latest Activity Report is deleted this updates the USYD_Last_Activity_Report_c field on the Account |
Salesforce Activity
Configuration for Events and Tasks will be dependent on in progress business decisions about what fields add value when logging interactions with Alumni and Donors. This section will be updated as business decisions are finalised.