# Pull Objective Data Configuration (RIM) Regulatory objectives sometimes require multiple submissions to get approved, often with similar or identical details. To reduce data entry, Vault allows users to enter all required details on a _Regulatory Objective_ record, and then copy the related records from the _Regulatory Objective_ record to a _Submission_ record.
## Configuring the Pull Objective Data Action To enable Vault to pull any _Regulatory Objective_ join records to a _Submission_ record asynchronously, add the _Pull Objective Data_ [user action](/en/lr/59885/#define-actions) to any _Submission_ object lifecycle state. ## Configuring Object Access To ensure users can create _Regulatory Objective_ join records and access the _Submission_ join records that Vault creates, update the _Regulatory Objective_ and _Submission_ [object page layouts](/en/lr/26387/) to add related object sections for each supported join object. ## About Record Naming If you configure [system-managed naming](/en/lr/30986/) on the _Submission_ join objects, Vault names newly-created records based on your defined patterns. When setting up system-managed naming, ensure that your naming pattern doesn't exceed 128 characters or record creation could fail. If you don't configure system-managed naming, Vault will name records based on key fields. ## About Object Type Mapping Vault uses object type mapping to determine which object types to use, depending on the _Registration_ object types selected in the wizard. This is especially important for registrations with a combination of drug product, medical device product, and packaging details. To do this, Vault checks for active _Object Type Mapping_ records you've created and, based on that mapping data, selects the object types. If there are no active records, the wizard automatically selects the target object type by comparing the Names of the source and target object types (for example, `device_intended_use__v`). If the _Name_ values do not match, Vault prompts the user to select the target object type. ### About the Object Type Mapping Object The _Object Type Mapping_ object supports customers who want to manually create submissions or regulatory objectives for both drug products and medical device products. See [Configuring Object Type Mapping for Registrations](/en/lr/62601/) for more information and a sample set of mappings. ## Configuring Matching Custom Fields Vault can copy custom field values from _Regulatory Objective_ join records to the corresponding _Submission_ join records for the following field types: _Picklist_, _Object_, _Date_, _DateTime_, _Yes/No_, _Text_, and _Number_. In order for Vault to copy matching custom fields, you must configure custom fields with matching names and field types on both objects. You should not configure entry criteria on any matching custom fields on the _Submission_ join objects, or Vault may not be able to create new records. If you have object types enabled on any of these objects, configure matching custom fields for all object types. ## Configuring User Permissions In order for users to access and use the _Pull Objective Data_ action, you must ensure that their security profiles are configured correctly. Users need: * _Create_ permission on the objects the action creates, for example, _Submission Product_ * _Read_ permission on the source _Submission_ record from which they start the action, as well as the records from which the wizard pulls data, for example, _Regulatory Objective Product_ * If the objects use Dynamic Access Control, users need at least the _Viewer_ role on the specific records * If your Vault uses field-level security, users must have _Read_ permission on the fields from which Vault pulls data