Sponsor Tracking Rules for Relationships

• A Relationship Type is already configured. This tutorial uses “PaaS” (Platform as a Service) as an example.

To create a rule for sponsor tracking that triggers a CTA whenever there is a change in sponsor attributes:

1. Under Edit Rule, enter or select the following details:
   • Rule Type: Select Custom.
   • Rule For: Select Relationship.
   • Rule Name: Enter the rule name. For example. Standard Sponsor Tracking Rule for PaaS.
   • Relationship Type: Select the Relationship Type. For example, PaaS.
   • Description: Enter description, if any.

2. Click NEXT.
3. Under Setup Rule, drag-and-drop the following fields from the

RelationshipSponsorTrackingHistory object in the Show section:

• RelationshipSponsorTrackingHistory::Relationship (This field will be available by default)
• RelationshipSponsorTrackingHistory::Relationship Name
• RelationshipSponsorTrackingHistory::ChangedAttribute
• RelationshipSponsorTrackingHistory::NewValue
• RelationshipSponsorTrackingHistory::PreviousValue
• RelationshipSponsorTrackingHistory::Contact Name

4. Drag-and-drop the following fields in the Filters section.
   • GS Relationship::Relationship Type (This field and its value are available by default after you select the relationship type in step 1.)
   • RelationshipSponsorTrackingHistory::ChangedAttribute - equals - company.
   • RelationshipSponsorTrackingHistory::ChangedAttribute | equals | location.
   • RelationshipSponsorTrackingHistory::ChangedAttribute | equals | title.
   • RelationshipSponsorTrackingHistory::Created Date | greater or equal | Add N Days to Rule Date | -1.
   • RelationshipSponsorTrackingHistory::Created Date | less than | Rule Date.

5. Modify the Advanced Logic to A AND (B OR C OR D) AND E AND F.

6. Click NEXT.
7. Under Setup Action, enter or select the following details:
   • Action Type: select Call To Action.
   • Priority: select High.
   • Type: select Risk.
   • Status: select New.
   • Playbook: select a playbook if you already have one for sponsor tracking related changes.
   • Reason: select Sponsor Change.
   • Owner Field: select the owner for the CTA being created.
   • Due Date: Run Date + 5 Days.
   • Default Owner: enter a default owner.

• Post update to chatter: select Always.
• Post update to comments: select Once.
• Comments: enter <${RelationshipSponsorTrackingHistory::Contact Name}> has changed <${RelationshipSponsorTrackingHistory::ChangedAttribute}> from <${RelationshipSponsorTrackingHistory::PreviousValue}> to <${RelationshipSponsorTrackingHistory::NewValue}>.

Note: Type @ to see the token values for Comments.

8. Click SAVE.

Similar to Rule for Tracking Sponsor Attribute Changes, you can configure a rule for tracking sponsors that are to be deleted.

1. Under Setup Rule, drag-and-drop the following fields in the Show section.
   • SponsorTracking::GSRelationship (This field is available by default as you select the relationship type while creating the rule)
   • SponsorTracking::SponsorFullName
   • SponsorTracking::Account
   • SponsorTracking::GSRelationshipName
   • Account::Created By ID Name
   • SponsorTracking::Account Name

2. Drag-and-drop the following fields in the Filters section:
   • GS Relationship::Relationship Type. (This field is available by default after you select the relationship type while configuring the rule.)
   • SponsorTracking::Contact | equals | NULL.
   • SponsorTracking::Last Modified Date | greater or equal | Add N Days to Rule Date | -1.
   • SponsorTracking::RelationshipContact | equals | NULL.

3. Modify the Advanced Logic to A AND C AND (B OR D).

4. Click NEXT.
5. Under Setup Action, enter or select the following details:
   • Action Type: select Call To Action.
   • Priority: select High.
   • Type: select Risk.
   • Status: select New.
   • Playbook: select a playbook if you already have one for sponsor tracking related changes.
   • Reason: select Sponsor Change.
   • Owner Field: select the owner for the CTA being created.
   • Due Date: Run Date + 1 Days.
   • Default Owner: enter a default owner.

• Post update to chatter: select Always.
• Post update to comments: select Once.
• Comments: enter The contact <${SponsorTracking::SponsorFullName}> of Relationship <${SponsorTracking::GSRelationship Name}> has been deleted.

Note: Type @ to see the token values for Comments.

6. Click SAVE.