Scribd
Upload
9 views20 pages

Session 20-Debugging-Events, AgentResolution, Background Methods

Session 20-Debugging-Events,AgentResolution,Background methods

Uploaded by

Vishnu Vardhan Reddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9 views20 pages

Session 20-Debugging-Events, AgentResolution, Background Methods

Session 20-Debugging-Events,AgentResolution,Background methods

Uploaded by

Vishnu Vardhan Reddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 20

Debugging techniques.

Event Debugging
If here exist any check FM , then we can debug it by placing the debugger in the FM.
Suppose the code is wriiten in Check FM as below.
Now go to SWE2 and associate this check FM with the event and BOR.
Trigger the event in SWUE and provide the BOR , Event name , Object key and click Create Event button.

Give object key as 293


Debugger will get stopped
Execute the t-code SWEL , the event is triggered and workflow has captured the same.

Now provide 292 in the object key.

Debugger will get stopped and exception will be raised , hence workflow will not get trigerred.
Execute SWEL , the exception is thrown and workflow is not trigerred.

Agent Resolution debugging.


We can debug the method which determine the agents or rule which fetches the agent by placing the
debugger in the code. Since the task will be foreground task hence it can be debugged.
Create the Rule in PFAC tcode and assign it to one FM
Create the FM with importing and exporting parameter.

Write the below logic to fetch the agents and place the debugger.
Assign the FM created with the Rule

Create the rule container element ‘LEVEL’.


Assign the rule with workflow.
Once executed the debugger will get stopped and hence the code can be debugged.
Background methods debugging
Suppose there is one step/activity i.e background method , then we can debug it by making it as
foreground and getting it placed in inbox. Thus when executed the breakpoint will get stopped.
Here the save method is background , make it as foreground.
Assign the wf initiator in expression tab , so that once the step is executed the workitem will get placed
in initiators inbox.
Execute the workflow by providing all the container values.
Now we can see the item gets placed in inbox.

Execute it by DC on it, and the debugger will get stopped.


All the container values will also flow and hence debugging can be carried out.

You might also like