Defining record definitions to store and manage data
A record definition is a collection of the data required for building the application for your business process. A record definition is made up of specific record fields. For example, a task can be stored as a record definition.
Application business analysts can customize the objects developed in their own applications and that are marked customizable by the developers, but cannot customize the objects developed in com.bmc.arsys. For example, objects in core BMC applications like Foundation, Approval, and Assignment cannot be customized.
|Where to go
|To understand the concepts related to a record definition and a record field, and types of record definitions.
|Record definition concepts
|To create a regular record definition and modify record definitions to add or update record fields, permissions, or record indexes or include record data with the bundle.
|Creating or modifying regular record definitions
|To create a join record definition.
|Creating join record definitions
|To create an external record definition.
|Creating external record definitions
|To inherit or extend an existing record definition to a new record definition.
|Inheriting an existing record definition to a new record definition
|To define a relationship between the record definitions.
|To encrypt or hide the field data.
|To create record instances.
|To enable auditing of record definitions.
|To create hierarchical groups by using security labels.
|Creating hierarchical groups by defining security labels
|To customize the record definitions, view definitions, process definitions, rule definitions, named list definitions, and association definitions created for an application.
Use shell to: