Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with debugging
Search options not deleted
user 27607
Debugging is Force.com's way of printing the specified message, in string format, to the execution debug log with the specified log level. Called using System.debug which takes either single parameter of message or two parameters of message and log level.
0
votes
Viewing Debug Log for a class
Call the runApexClass function with the instance variable of your class.
Eg:-
HelloSandboxWorld s = new HelloSandboxWorld();
SandboxContext context = new SandboxContext();
s.runApexClass(context);
- 296