Action and Action Map Best Practices

Where Rules can become inefficient with poorly structured logic, Actions that are executed in the wrong order can give incorrect results. Make sure that Actions perform Operations only on the objects that they are required to and don't contain objects that should have been filtered out beforehand.

---

Rules and Actions should be kept to a single, clear purpose. Efficient Actions are created for Action Maps, paired with a Rule for filtering the data.

---

When Actions need to test objects, Temporary Values can be used to reduced repeated processing within the same Object, Session, or Task.

---

Set constant values at the top of an Action as Temporary Values so they can be easily managed. When a constant value is used in multiple places, all instances can be updated with a single change.

---

Action Maps are great for producing reports. They pair testing in Rules with outputs created in Actions.

Multiple report types are available "out of the box" and the Non-conformance data store can replace reporting in Actions/Action Maps, if it contains the information you require.