Ruleworks: test a follow-up rule
Make follow-up rules your admins can maintain.
Before you start
Section titled “Before you start”Read the getting-started checklist. Confirm module access, the target records and the change owner before proceeding.
Test a follow-up rule
Section titled “Test a follow-up rule”- Choose a primary table and the event that should start the rule. Keep the first scenario limited to one task.
- Build the conditions and configure a follow-up action using fictional records. Check mappings and recipients before enabling any send behavior.
- Validate the configuration and preview matching records. Use the test trace to understand which conditions and actions are selected.
- 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.
What to check
Section titled “What to check”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.
Go further
Section titled “Go further”Developer reference and extension boundaries · Module overview