Important Debugging tools
(Tracer, Live UI & Chipboard)
TRACER
[To trace
all the rules behind
execution & active requestor]
Ø Tracer is
the main
debugging tool used to trace complete step-by-step
execution from bottom to top and also trace active requestor session connected to your server
node
Ø Better
use Tracer to trace entire
execution & use Trace Open Rule tracer to trace specific rule execution
·
Path to Tracer: Developer tool bar > Tracer tool
·
Path to Tracer Open Rule: Dev portal > specific rule opened > Actions menu > Trace
It is
available for only specific rules like Activity, Data Page, DT, RD, Service
rules
Ø Tracer
has below features:
·
Play / Pause mode: Make sure Tracer
in play mode before run the
program
Pause
mode: You can stop trace in
mid of program whenever you want
·
Clear: To erased display
events & to continue further tracing
·
Save: To save tracing results in local
system as
(an Excel, CSV or XML file) for analysis & to send it to superiors
·
Remote Tracer: To trace active remote
requestor only on current Node
F Go SMA to trace active
remote requestor on other Node
·
Watch (Property Inspector - across
program): To watch Property
at specific Page
F To watch the specific properties (one by one) by
changing its values at specific page in
program
F It stops tracing at that particular Property you set in Page
·
Breakpoints (only specific Activity step):
To watch Property
at specific Activity Step
F To set break points for specific Activity Step,
so that we can watch required Property values we set (one by one)
F It stops tracing at that particular ‘Step begin’ you are
going to set
·
Settings: Select the desired options
to limit the tracing results, it improves your Tracer performance
1. Events To
Trace: Activities &
its Steps / DT &
its Actions / When and
Access Deny, Exception
2. Break
Conditions: Exception, Fail Status & Warn Status
3.
General Options: Abbreviate Events, Expand Java Pages, & Local
Variables
4. Event
Types To Trace: Auto populate properties, Case Type, Data Page, Declare rules (9), Flow, Interaction, Locking, Log Messages, Parse Rules, SOAP Messages, Services , Stream Rules etc.
5.
Rule sets To Trace: We can filter Rule sets from
tracing
F As a
beginner or needy, better trace entire execution including OOTB also by selecting
all Rule Sets
6.
Pages To Trace: To trace additional
pages like referenced pages
F Primary & Step Pages
are always traced by default
7. Max Trace Events to Display (default: 500 most recent
trace lines)
Ø Tracer
has columns as:
Line / THREAD / INT / Rule# / Step Method
/ Step Page
/ Step / Status / Event type / Elapsed / Name / RuleSet
·
Step Method: we
can find parameters here
·
Step Page: we can find page details here
·
Again Event type
has (in order while execution): Represents internal steps of that rule
Activity
End / Step End / Step Begin / Activity Begin / When
Begin / When End / Stream Rules / Expression / Constraint / Model Begin / Model
End / Access Denied etc…
LIVE UI
[Used to quickly inspect the UI rules]
Ø Live UI tool is used to
identify & quickly inspect the rules that are underlying the Harness (such as Harness, Section, Property, Declare, Skin rules
& even FA etc.) to fix some UI
issues there itself and to also understand the structure of a work object form
Ø There itself at run-time,
we can also customize the Section using Live UI tool
Ø Developer tool bar > Turn on the UI Inspector [Turn off it
when done by toggle it]
Ø Toggle it by Ctrl + Shift without coming out from it
Ø Also
called ‘UI Inspector’ tool
Comments
Post a Comment