Versions Compared

Version Old Version 5 New Version Current
Changes made by

rommel.ngo

rommel.ngo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties

Target release

Q42024

Epic

Jira Legacy
serverSystem Jira
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyTAPSS-2039

Document status

Status
titleDRAFT

Document owner

rommel.ngo

Designer

rommel.ngo

Tech lead

rommel.ngo

Technical writers

rommel.ngo

QA

Sushma Ramachandrappa

...

  • Wellbeing is already out of the Jarvis by Go Live / User Acceptance Testing

  • TAP Members are defined by

    image-20241001-042724.pngImage Added

\uD83C\uDFA8 User interaction and design

...

  • As we do not know who in the future will be joining Jarvis, it should be noted that they need to actively exclude Non TAP users from ever having access to any TAP Activities. Using Restriction rule have its consideration, one of which is :
    Before creating restriction rules, we recommend that you Turn Off Salesforce Classic for Your Org. Salesforce can't guarantee that restriction rules work as intended for end users who are in the Salesforce Classic experience.

🪶Impact Analysis

Excerpt
nameActivities OWD Impact Analysis

TAP Activities - Private (AS IS)

Only the activity owner (labeled as Assigned To) and users above the activity owner in the role hierarchy can edit and delete the activity.

TAP Activities - Controlled by Parent (TO BE)

A user can perform an action (such as view, edit, transfer, and delete) on an activity based on whether he or she can perform that same action on the records associated with the activity.

The "parent" of the activity record is:

  • Who Id (Name): Contact and Lead

  • What Id (Related To): Account, Opportunity, Case, Campaign, Asset, and custom objects with Allow Activities enabled.

TAP Users

  • This limits cross team collaboration.

  • Risk of reduced operational efficiency if data is not visible to teams that need it.

  • When Activities are parented to private objects such as Case, this also still limits cross team collaboration.

  • Potential security concerns since there is no data segregation within TAP

  • As most of our objects are public (Account, Contact, Opportunity), Activities parented to these records are also going to be public which could potetnt

Non Tap Users (current or future)

  • No Impact, unless the user is put above TAP users in Role Hierarchy

  • As most of our objects are public such as Accounts, Contacts, and Opportunities, all activities related to these objects inherently becomes public as well where a Non-TAP user could potentially get access to more sensitive information on Activities (i.e. emails, events, tasks, call conversations)

Proof of Concept : Making Task OWD Sharing to Controlled by Parent,

...