...
The 2FA and CAMIS databases will be in sync.
TWOFA_USERID_LBL in CAMIS table AA008_APPLICATION_USER and the GLOBAL_USERID_LBLwill be in sync for CAMIS User accounts (Internal), as well as for CAME Admin and CAME Associate Admin accounts.
We won’t have to prepare a script to update those codes.
On acceptance, this would eliminate the need to have the dba temporarily disable the trigger, run the script and then re-enable the trigger.
The 2FA database will have the records, in AC040_STAKEHOLDER and AC044_EXTERNAL_STAKEHOLDER
This week, I manually recreated those as a developer (Dean W) was working on replicating a production issue on prod for a CAME. See devops 266417 Unable to add new eMER phone to CAME profile
Because members of the development teams do not have full eMER accounts on production, those accounts still need to be re-established per the notes I provided in the “Developer account section” of this document.
...