Skip to content

Ruleworks: test a follow-up rule

Make follow-up rules your admins can maintain.

Read the getting-started checklist. Confirm module access, the target records and the change owner before proceeding.

  1. Choose a primary table and the event that should start the rule. Keep the first scenario limited to one task.
  2. Build the conditions and configure a follow-up action using fictional records. Check mappings and recipients before enabling any send behavior.
  3. Validate the configuration and preview matching records. Use the test trace to understand which conditions and actions are selected.
  4. Review the result with the intended user role, then follow your change process to activate the rule. Watch its run history after the first real event.
One condition, clearly expressedThe trigger and grouped conditions behind one account follow-up rule.Screenshot placeholder
Reserved for an approved product capture. No demonstration is available here yet.

TestRecord is not a pure read: it stamps the last-tested time. Saving drafts also invokes lifecycle behavior. Do not use live business records as harmless test data.

Record the expected result and compare it with the actual outcome. Keep the configuration in draft or paused if the result or permissions are unclear. A screenshot slot is not evidence of release acceptance.

Developer reference and extension boundaries · Module overview