Asset reuse and relevant records

Ensure that assets are built to be reusable, and publish them for reuse in App Studio. Existing assets can be refactored into reusable assets using the refactoring tools.

Use relevant records to encourage the reuse of reusable rules in App Studio and the Case Designer.

As an organization's maturity model is implemented, more and more reusable enterprise assets are available. Manage the common assets through a center of excellence (COE).

Relevant records designate records of a case or data type as necessary or reusable in a child class. Relevant records for a case type can include references to fields (properties), views (sections), processes (flows), user actions (flow actions), correspondence rules, paragraphs, harnesses, service level agreements, and when rules that are explicitly important to your case. For a data type, relevant records designate the most important inherited fields (properties) for that data type.

The relevant records can include records that are defined directly against the class of the case or data type and fields inherited from parent classes.

Designating a record as a relevant record controls most prompting and filtering in the Case Designer and Data Designer. For example, user actions and processes defined as relevant records show up when adding a step in the Case Designer.

Fields marked as relevant for a case type define the data model of the case. Processes and user actions marked as relevant appear in Case Designer prompts to encourage reuse. Views marked as relevant appear as reusable views.

Fields, views, processes, and user actions are automatically marked as relevant records when creating them within the Case Designer and Data Designer. You can manually designate relevant records on the Relevant Records landing page. It is also possible to add a relevant record by using pxSetRelevantRecord.