Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Testing an activity in context

Updated on January 14, 2022

If the activity requires extensive setup and is more appropriately tested in context rather than through unit testing, you can trigger the Tracer to start only when the activity is reached.

To test an activity in the context of other activities and rules that produce the needed initial conditions, complete the following actions:

  1. Open the activity.
  2. Select Actions > Trace. The Tracer tool starts.
  3. To avoid using more memory than needed while tracing, click Settings in the Tracer window and ensure that only the ruleset containing the activity is selected in the Rulesets To Trace section.
  4. Begin the other processing that eventually calls the activity in your own requestor session. Tracer output begins when the activity starts.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us