POPPY RELEASE ON MODDICONV-327

NOTE MODDICONV-302, MODDICONV-323, and https://folio-org.atlassian.net/browse/UIDATIMP-1465#icft=UIDATIMP-1465 must all be released and deployed together as Orchid CSPs for all to work properly

Purpose:
Profile validation errors can be represented as either a simple message or in error code format (e.g. "jobProfile.duplication.invalid").
It is complicated on the UI side to determine whether the validation error should be shown as-is or translated into a more user-friendly message.

Steps:
Change the following error codes to their corresponding more verbose messages:

• jobProfile.duplication.invalid

• matchProfile.duplication.invalid

• actionProfile.duplication.invalid

• mappingProfile.duplication.invalid

ORCHID Critical service patch details

1. Describe issue impact on business - Change error messages to be more understandable to users

2. What institutions are affected? (field “Affected Institutions” in Jira to be populated) - All with 3+ actions for the same record type in the same job profile

3. What is the workaround if exists? Consolidate actions for 1 record type into single action profile, but that is not desirable for some libraries

4. What areas will be impacted by fix (i.e. what areas need to be retested) Data Import Smoke and CP automated tests; this manual test

5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high).

   • Purpose: Some libraries prefer to have more discrete/granular mapping profiles linked to shared action profiles for updates, because they can use these action profiles in scope of one job profile instead of creating unique mapping profiles and individual action profiles that might be used only once. Currently, when there are multiple action profiles for updating holding within one job profile, the 3rd action always fails.

   • Technical explanation:

     • Remove OL retry counter from the event payload after a successful attempt to update holdings to avoid its influence on subsequent actions processing

     • Add test

   • Level of effort: Work is complete and level effort is low.

   • Technical risk: Very minimal risk.

6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO. Test cases already exist and level of effort is .5 day

7. What is the roll back plan in case the fix does not work? Revert to previous version