Skip to content

Start with one useful change

You do not need to configure the whole collection at once. Choose one process, one form or one set of records that your team wants to improve.

  • Use a development or test environment approved by your organization.
  • Confirm that Core and the module you want to use are installed. Package delivery and final installation instructions will accompany the release; these pages do not provide a download yet.
  • Ask your platform administrator for the module role and access to the records involved. An app being visible does not mean every action is permitted.
  • Use fictional sample records. Note any flows, rules or plugins that may run when those records change.
  1. Open the installed module’s model-driven app. Check Setup Check where available and resolve items relevant to your task.
  2. Choose the module guide below. Write down the expected result before configuring anything.
  3. Start with a draft and a small sample. Validation checks the configuration; a preview helps you inspect results. Neither proves the whole business process is ready.
  4. Review the result with someone who has the intended user role. Administrator access can hide permission problems.
  5. Activate or publish only when the guide and your organization’s change process call for it. Record how to pause the configuration and who owns it.

Capture the module name, installed version, time, operation and the visible error. Include a correlation or run identifier if shown. Avoid sending record contents or personal data. Check permissions, configuration status and required components before retrying a write.

Contact Empath Design with a reproducible description.