Rimobjectconfiguration
Class: metadata
Rimobjectconfigurations define properties for RIM objects that are leveraged across multiple Veeva Submissions and Veeva Registrations features such as the Registrations and Submission wizards, Global Content Planning, and copying Content Plans.
Learn more about RIM Object Configurations in Vault Help.
| Attribute | Metadata | Description |
|---|---|---|
label | Type: String Max length: 60 | UI-friendly string in the Vault’s base language. |
active | Type: Boolean | Indicates whether the component is active. |
object | Type: Component Required | The object for the configuration. |
Rimfieldconfig
Section link for Rimfieldconfig| Attribute | Metadata | Description |
|---|---|---|
label | Type: String Max length: 60 | UI-friendly string in the Vault’s base language. |
active | Type: Boolean | Indicates whether the component is active. |
create_display_order | Type: Number | Determines the display order when creating new registered details using Create Registrations or Manage Registered Details wizards. This property also applies when creating Change Items in Create & Manage Event Details. |
editable_application_detail | Type: Boolean | Determines whether an Application relationship field can be edited if it is used in a Regulatory Objective or Submission in an excluded lifecycle state when Enable Application Relationships, Enable Relationship Triggers, and Exclude Regulatory Objective Lifecycle States settings are configured. |
editable_registered_detail | Type: Boolean | Determines whether a field is editable in the Manage Registered Details wizard. If set to true, the field is editable when updating existing details using the Manage Registered Details wizard. |
field | Type: Subcomponent Required | The field for the configuration. |
object | Type: Component Required | The object for the configuration. |
unique_across_applications | Type: Boolean | Determines whether the field is used by the Copy Content Plan/Copy Into Content Plan and Compare and Merge Content Plans actions while looking for matching and unique relationships when source Submission and target Submission are under different Applications. |
unique_within_application | Type: Boolean | Determines whether the field is used by the Submission Wizard and the Copy Content Plan/Copy Into Content Plan and Compare and Merge Content Plans actions while looking for matching and unique relationships when the source Submission and target Submission are under the same Application. It is also used to prevent duplicate Application relationships when managing these relationships via the Enable Application Relationships and Enable Relationship Triggers RIM settings. |
update_display_order | Type: Number | Determines the display order when updating existing details using the Manage Registered Details wizard. |
use_in_comparison | Type: Boolean | Determines whether the field is included when comparing Content Plans of the same Content Plan Template during Global Content Plan dispatch and when comparing and merging Submission Content Plans. |
Supported Operations
Section link for Supported Operations| Operation | Support |
|---|---|
| Create | |
| Recreate | |
| Alter | |
| Drop | |
| Rename | |
| Describe | |
| Generate Recreate | |
| Queryable |