Documentation Index

Fetch the complete documentation index at: https://docs.staedean.com/llms.txt

Use this file to discover all available pages before exploring further.

Check for errors

Prev Next

You can automatically check RapidValue elements for errors.

Which checks are done?

Generally, the checks are done that are also done when you manually enter a record and save it to the database. So, the checks are done that control the data consistency in the database. For example, does a used reference still exist in the database?

What is checked?

If you check for errors, these RapidValue elements are checked:

  • The selected element.

  • Its references. If a reference is defined, only the reference record itself is checked and not its references and children. For example, almost each RapidValue element has a reference to the solution. In this case, only the solution record itself is checked and not its children and references.

  • Its children. If a child is defined, the child itself is checked. But also, its references and its children.

Example:

  • Flow: if you check a flow for errors, these RapidValue elements are checked:

    • The flow itself.

    • The flow references: solution and process.

    • The flow children: lanes, objects, connectors. If one of the objects is, for example, an activity, the activity itself is checked. But also, its references: solution, role, area, and application and its children: activity steps.

Fix errors

The found errors must be solved manually. You can do so immediately. But you can also create a task to have it solved at another time.

Flow diagram