...
See also: Creating a CAME profile
See also: Creating a CAME Associate Admin Profile
When CAMIS development or acceptance is refreshed from production, without refreshing the corresponding 2FA database:
...
if the developer /test business accounts are left as is:
account does not appear in CAME Admin/CAME Associate Admin drop-down
account won’t be connected to existing GC-Key.
these accounts can be “upgraded” to full eMER accounts that are connected to the original GC-Key by inserting the appropriated data into the following tables:
Reconstructing the accounts is time consuming (RPA might be a possibility to help with this ? have not investigated yet, since this is a new process).
Re-importing a backup of the existing account data could potentially break referential integrity in some parts of the application.
In short-term future, it may be more efficient to set the accounts that need to be “brought back” to deleted, and then re-create from scratch. Will do a test to see if such an account could be linked to existing GC-Key.
Main tables:
Table | Description |
|---|---|
AC040_STAKEHOLDER | Contains the main record for Internal admin accounts having 2FA Admin access and eMER accounts external stakeholder (eMER) accounts have |
AC043_INTERNAL_STAKEHOLDER | Holds a record related to the one in AC040_STAKEHOLDER for users with 2FA Admin access. |
AC044_INTERNAL_STAKEHOLDER | Holds a record related to the one in AC040_STAKEHOLDER for users with 2FA Admin access. |
AC002_XREF_APPLICATION_USER | -Application access - |
AC003_LOGIN_ATTEMPT |
Recommendation:
based on the experience with the recent refresh of the CAMIS db (only) from production to acceptance, my recommendation would be to refresh both databases from prod to the target environment being refreshed (acceptance / development) at the same time in the future, as it will be less work for all involved.
...