Some profiles after migration lose their Actions (relevant for re-used Actions in different Profiles). Investigate the causes, look for possible solutions.

Cornell will provide examples of their profiles. Create Orchid env (actually we only need the mod-di-converter-storage schema and the module) with provided data, migrate data - see what happens. Before migration see what logs could be added, turn the most detailed level of logging.

Critical service patch details

1. Describe issue impact on business - Issue will cause Job profiles to unlink from Match profiles and Action profiles during system migration process (e.g. Orchid to Poppy)

2. What institutions are affected? (field “Affected Institutions” in Jira to be populated) - Reported by Cornell, 5 Colleges, potential to affect any institution.

3. What is the workaround if exists? No workaround.

4. What areas will be impacted by fix (i.e. what areas need to be retested) - Existing job profiles prior to the migration and creation of new profiles and linking them.

5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high). - Previously the migration was part Java and part SQL, there was some context missing on the SQL side that caused wrong links to be selected. The migration is now all SQL to retain the context. This involved 9 workdays of effort with a technical risk of low.

6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO.  -
   - Creation of new profiles, linking them and performing data import jobs with those profiles.
   - Checking existing job profiles ensuring that there are no missing links.
   
   

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