Qmsknowncomplaintprofileconfiguration
Class: metadata
This component type is only available in Quality Vaults with Veeva QMS enabled.
Known Complaint Profiles lets users define and leverage a set of Known Complaints to automatically populate field data and CAPAs, codes, investigations, risks, and root causes to Complaint records in order to reduce processing time for recurring complaints. QMS Known Complaint Profile Configurations define the related records and field data to sync between Complaints and Known Complaints, as well as the lifecycle state a Complaint moves into upon association with a Known Complaint.
Learn more about Known Complaint Profiles 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. |
complaint_object | Type: Component Required | Must be either Object.quality_event__qdm or Object.complaint__v. |
complaint_object_lifecycle | Type: Component Required | The lifecycle of the complaint_object. |
complaint_object_type | Type: Component Required | The object type of the specified complaint_object. For the complaint__v object, this value must be Objecttype.medtech_complaint__v or Objecttype.pharma_complaint__v. For the quality_event__qdm object, this value must be Objecttype.complaint__qdm or Objecttype.mt_complaint__v. |
copy_capas | Type: Boolean | If true, Vault copies related CAPA Actions or Medtech CAPAs between Known Complaints and Complaints. |
copy_codes | Type: Boolean | If true, Vault copies related Codes between Known Complaints and Complaints. |
copy_investigations | Type: Boolean | If true, Vault copies related Investigations between Known Complaints and Complaints. |
copy_risks | Type: Boolean | If true, Vault copies related Assessment Risks between Known Complaints and Complaints. |
copy_root_causes | Type: Boolean | If true, Vault copies related Root Causes between Known Complaints and Complaints. |
description | Type: String Max length: 1500 | A general description of the known complaint profile configuration. |
fields_to_copy_ap_and_uar | Type: String Max length: 1500 | Specifies which fields are copied from Known Complaints to the processing Complaints. For example, investigation_summary_and_conclusion__v. |
fields_to_copy_pp_and_up | Type: String Required Max length: 1500 | Specifies which fields are copied from source Complaints to Known Complaints. For example, investigation_summary_and_conclusion__v. |
lifecycle_states_of_known_complaint | Type: String Required Max length: 1500 | When users associate a processing Complaint with a Known Complaint in one of the specified states, the processing Complaint moves into a state associated with the Known Complaint Closed state type. Otherwise, the Complaint moves into a state associated with the Known Complaint Open state type. For example, known_complaint_approved_state__c. |
Supported Operations
Section link for Supported Operations| Operation | Support |
|---|---|
| Create | |
| Recreate | |
| Alter | |
| Drop | |
| Rename | |
| Describe | |
| Generate Recreate | |
| Queryable |