Issue Scenario

User needs to know how to use SMS Magic Error Logs.

Solution

•In order to understand an issue you have encountered, check the Error Logs to confirm if a Log was generated.

•In case of Permission issue, you can see the Object name and the field which requires permission.

•In case of validation issues, the error logs will provide you with details for the same.

•It also informs you of system exceptions on which you can find out more details on Google.

•In case of code issues, it provides the line number and the trigger name.

•Check with the CS team, to know if they have encountered a similar issue.

•Reach out to the dev team If no logs are available or you are unable to understand them.

Issue Scenario

The user receives system Error Messages

Solution

When you receive a system error message, you can look it up on Google to understand its significance and resolve it with a work around. However, If you are unable to resolve it you can reach out to the Dev team.

Definition

Debug Logs help you identify the possible causes behind a particular issue occurring in the customer’s org.

Prerequisites

You will need a subscriber access to setup Debug logs. As, our objects and functionalities are part of a managed package, detail logs for the same will not be available directly from the customer’s org. Therefore, we will need to set up the logs from the subscriber’s access.

When you view the debug logs page through subscribers access, Salesforce displays the following message
“Debug logs you request will also include debug information for your packages. These logs are not accessible by the customer.”

To setup Debug Logs

1.Under Setup, type “Debug Logs” in the Quick Find search box.

2.Click Debug Logs and then click New.

3.If you want to debug the issue for a user select User in the Traced Entity type field.

4.Select name of the user facing the issue in the Traced Entity Name field.

5.Select the start time and end time , i.e. the time during which you will be reproducing the issue. (Try to be very specific. If you select a long time period, then, it will generate 1000s of logs and will be difficult to trace)

6.Now add a debug log.
For the debug log, make sure that you are selecting appropriate debug levels for debugging. (for example, if you want to check an issue regarding a custom apex class or trigger, then, you can select finer/finest for it.
If you are trying to trace an issue with the workflow, then, select the Workflow as Fine/Finer)

7.Click Save.

8.Reproduce the issue for which you want to generate the log.

9.Once generated, open the logs and search for “Exception” or “Error” to narrow down your area of investigation.

10.If you are unable to understand the logs, create a case for the Dev team and share the logs with them for further investigation.

Issue Scenario

User needs to know how to send Automated SMS.

Solution

1. Create a process builder to send an automated SMS when a new task is created or edited to meet certain criteria. The XML configuration needs to be created on the Object on which you are creating the task. You can refer to the following link for steps to create the XML configuration: http://www.screen-magic.com/configure-sms-automation-using-workflow-rules/

2.Select “Task” as the object.

3.Under Start the process select Start only when the record is created option.

4.Enter the criteria as per your requirement. In the screenshot shown below, the criteria is defined as “task subject should not be SMS Notification” and the task should be related to Leads object.

5.Save the criteria.

6.Enter the immediate action as Create a record.

7.Under Record Type select Task .

8.Enter the following field values for creating the task record.

9.On completion, you can send an Automated SMS on task creation.