You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Monarc FO instance administrator left his company.
He had to be replaced using the BO. The new e-mail address has been configured.
The issue was that this new e-mail address is the one of a person already defined as user of the FO.
So whereas no change has been done on FO side, the BO has not displayed any error message.
It would be important that an error message would be displayed.
The text was updated successfully, but these errors were encountered:
Any company's or the 1st superadmin user's changes on the BO side are applied by the ansible script that is executed in background mode. Ansible performs a connection to the client's DB and executes the records' modifications, inserts new ones or deletes in case of cleints' models changes.
Therefore an error message can't be displayed instantly and ansible has no mechanism to push a notification to the BO side.
Also when ansible executes a list of of SQL queries generated by the BO and it doesn't know if the result was successful, as it is a batch of them.
Actual situation
When there is an attempt to update an existing 1st superadmin user data to an existing on FO user, the SQL query fails due to the email address duplication on update.
Solutions
Semi-automatic way.
If the user's account is already presented on the FO side, then contact him/her to delete his account first. It is possible to do it via My account -> Danger zone -> Delete my account. And replace the 1st superadmin to the removed one.
Currently working solution.
Develop and API to obtain a list of users from a particular FO instance and call before opening the client's change dialog. If the existing user is selected as a new 1st superadmin account, then the only ID can be replaced by ansible. However also some other linked information. This endpoint can only be accessed by the BO instance. After the change is done the new 1st superadmin has to drop the old superadmin account (if the person left the company).
There are no external APIs available on the FO side and it requires a new complex dev.
A Monarc FO instance administrator left his company.
He had to be replaced using the BO. The new e-mail address has been configured.
The issue was that this new e-mail address is the one of a person already defined as user of the FO.
So whereas no change has been done on FO side, the BO has not displayed any error message.
It would be important that an error message would be displayed.
The text was updated successfully, but these errors were encountered: