You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use **Look up Data Record** to search for existing data records, or **Add Proposed Data Record** to include new records.
33
+
Use **Look up Data Record** to search for existing data records in Salesforce that are related to this Change Request.
34
34
35
35

36
36
37
+
Select the appropriate data records from the search results:
38
+
37
39

38
40
41
+
# Step 5 – Add Proposed Data Records
42
+
43
+
Click **Add Proposed Data Record** to include new data records that will be created or modified as part of this Change Request.
44
+
39
45

40
46
41
-
# Step 5 – Request Approval
47
+
# Step 6 – Request Approval
42
48
43
49
Once all required information is added, the operator can click **Request Approval** to move the CR into Pending Approval status.
44
50
45
51

46
52
47
-
# Step 6 – Approve or Reject
53
+
# Step 7 – Approve or Reject
48
54
49
55
Admins can then Approve or Reject the Change Request directly in Zendesk if the process is configured for in-Zendesk approvals.
50
56
51
57

52
58
53
-
# Step 7 – Complete or Push
59
+
# Step 8 – Complete or Push
54
60
55
61
When a Change Request has been approved, the admin can click **Complete** to close it. If no approval is needed, the admin can use **Push** to send the CR directly to Salesforce.
56
62
57
63

58
64
59
65

60
66
61
-
# Step 8 – Open DRD (Document Requirements)
67
+
# Step 9 – Open DRD (Document Requirements)
62
68
63
69
From the ticket sidebar, click the DRD link to open the Document Requirements view in Salesforce.
Click the Impact Analysis link to view the detailed analysis of the Change Request in Salesforce.
75
+
Click the Impact Analysis link to view the detailed analysis of the Change Request in Salesforce. This shows how the proposed changes might affect other components in your Salesforce org.
0 commit comments