Apply resolution notes
When data stewards accept or reject add or change requests (DCRs), they can select a predefined resolution note Comments that can be used by data stewards to explain the rejection or approval of a data change request. or create a custom resolution note.
Mandatory resolution notes
Only rejected DCRs require a resolution note by default.
Administrators can set an option so it is mandatory that all DCRs have a resolution note. When this feature is enabled, an error message reminds data stewards or data managers to add a note if they try to resolve a DCR that does not include a resolution note.
To enable this feature in their Network instance, administrators must select the Require Resolution Notes option on the General Settings page.
Predefined resolution notes
Data stewards can select a predefined resolution note by choosing a reason code from the Code drop-down list. You can scroll through the list or begin typing a description to refine it further.
If multiple languages exist for this code, data stewards can select the appropriate language from the Language drop-down list. The corresponding resolution note will update with the description supplied for the specified language.
Data stewards can add or update the provided resolution note based on the specific situation. This does not affect the original resolution note template.
Note: Line breaks can be used in resolution notes so users can easily read the comments. These line breaks are supported by the Network-CRM bridge, so Veeva CRM users will see the properly formatted comments.
Customize resolution notes
You can import and export predefined resolution notes Comments that can be used by data stewards to explain the rejection or approval of a data change request. that data stewards can select when accepting or rejecting a task. Sort the notes to specify the order that is displayed to the data steward.
This functionality must be configured by an administrator before predefined resolution notes are available to data stewards.
Note: The messages for system resolution notes cannot be configured.
Create resolution notes
- In the Admin console, select System Interfaces.
- In the left navigation, select Resolution Notes. Any notes that have been defined appear on the Resolution Notes page.
- Select or clear the checkbox for a note in the Enabled? column to make the note available or unavailable to data stewards during task resolution.
- Click Add Resolution Notes to create a resolution note.
- In the Type drop-down list, select the type of task response (rejection or approval) for the note.
- In the Countries field, type the countries applicable for the note. The drop-down list refines as you type the names.
- Provide a meaningful description for the resolution note.
- Select Enabled to make the note available to data stewards.
In the Resolution Notes section, select the Language for the note. In the Template field, provide the text of the note for that language.
Line breaks can be used in resolution notes so users can easily read the comments. These line breaks are supported by the Network-CRM bridge, so Veeva CRM users will see the properly formatted comments.
For API and DCR exports, the JSON response might contain "/n" whenever there are line breaks in resolution notes.
- Click the Add Language link to provide translations for each applicable country.
- Click Save.
Export resolution notes
To export defined resolution notes (or a blank template) to a spreadsheet for further updates, clicking Export. All of the defined resolution notes are exported in a .csv file.
Import resolution notes
You can define resolution notes in a spreadsheet and import them on the Resolution Notes page.
- From the Admin console, in the top navigation, select System Interfaces.
- In the left navigation, select Resolution Notes.
- At the top right of the page, click Import.
- In the Resolution Note Importer, click Download Workbook to download a file containing existing resolution notes.
- Update the file using the format and instructions provided in the sheet.
- Click Upload New File to import your changes. Statistics for the pending changes, including errors, are displayed before you apply the changes.
- To apply changes, click Apply Changes.
Sorting resolution notes
Administrators can change the order in which resolution notes appear to data stewards.
- From the Resolution Notes page, select a country for which you want to change the resolution notes order. Select the handles next to each note and drag the note to its new position.
- Click Save.
Data Stewards will see the resolution notes in the order set by the administrator.
System generated resolution notes
Auto rejection by system
The following are possible change request results and their corresponding descriptions for rejected change requests.
|R-00010||System rejected - The change request cannot be processed, possibly due to an error in the record. Please contact your administrator to log a support ticket.|
|R-00013||System rejected - The record you are trying to change is no longer managed by Veeva OpenData.|
|R-00014||System rejected - You are trying to update an Under Review record that is currently locked. Please resubmit your change request when the record is open for changes.|
|R-00015||System rejected - You are trying to update an invalid, merged or deleted record. Change cannot be processed.|
|R-00016||System rejected - You are trying to add a duplicate record. Please search before adding a new record.|
|R-00017||System rejected - Your change request has been rejected because the HCO/HCP record has been rejected by a data steward.|
|R-00018||System rejected - Missing mandatory fields. Please provide values for all mandatory fields.|
|R-00019||System Rejected - You are trying to update an invalid, deleted or merged_into sub-object. Change cannot be processed.|
|R-00100||System rejected - You are trying to update a field that cannot be mapped to Veeva Network. Please contact your administrator.|
System rejected - Your change request consists of at least one read only field.
|R-00102||System rejected - You are trying to update a field that is not available in your region. Please contact your administrator to remove the field.|
|R-00103||System rejected - You are trying to update a field that is not available. Please contact your administrator to remove the field.|
|R-00104||System rejected - The reference value selected cannot be define for this field. Please resubmit with another value.|
|R-00105||System rejected - Alternate key is a read only field and cannot be updated through change request process.|
|R-00107||System rejected - Custom key is a read only field and cannot be updated through change request process.|
|R-00108||System Rejected - You have submitted an invalid or inactivated reference code/value.|
|R-01000||System rejected - HCP has opted out and cannot be updated, your changes have been rejected|
|R-01001||System rejected - An Invalid HCO cannot be set as a parent HCO. Please resubmit your change request with another Valid HCO.|
|R-01002||System rejected - An HCO/HCP cannot be its own parent. Your change request have been rejected.|
|R-01003||System rejected - Veeva OpenData has set a primary affiliation and it cannot be updated for this relationship. To create your own primary affiliation, please contact your administrator to enable the custom primary affiliation field in Veeva Network.|
|R-01004||System rejected - An inactive affiliation cannot be set as primary. Please update the affiliation status before setting it as primary.|
|R-01005||System rejected - An inactive address cannot be set as primary. Please update the address status before setting it as primary.|
|R-01006||System rejected - Only one affiliation can be set as primary. Please resubmit you change request with only one primary affiliation.|
|R-01007||System rejected - Only one address can be set as primary. Please resubmit you change request with only one primary address.|
Auto approval by system
The following are possible change request results and their corresponding descriptions for approved change requests.
System approved - In Sandbox mode.
All change requests are auto approved.
|A-00011||System approved - Created by data steward.|
|A-00012||System approved - Workflow settings, auto approval is enabled.|
|A-00013||System approved - At least one field is set to always accept changes.|