Improve Entity Restoration with Dependency Handling in Admin Panel

[siarhei-fedziukovich]

Name and Version

0.7.0-rc

What is the problem this feature will solve?

Currently, in the admin panel's audit functionality, when a user attempts to restore an entity that has invalid references (e.g., the referenced entity is deleted), the system throws an error and displays a message to the user. This message outlines the dependency issue and asks the user to manually restore the dependent entities before proceeding with the restoration of the current entity. (https://github.com/epam/ai-dial-admin-backend/issues/208)

While this approach ensures data integrity, it creates a poor user experience. Users are forced to manually navigate through the dependencies, restore them one by one, and then return to restore the original entity. This process is cumbersome, time-consuming, and error-prone, especially when dealing with complex dependency chains.

There is a need for a more user-friendly and efficient way to handle entity restoration when dependencies are involved.

What is the feature you are proposing to solve the problem?

We propose enhancing the entity restoration functionality by providing users with two options when invalid references are detected during restoration. This will streamline the process and improve usability while maintaining data integrity.

1. Restore with Dependencies

• Automatically identify and include all dependent entities that need to be restored for the current entity to function correctly.
• Display a preview of the dependencies to the user, listing all entities that will be restored as part of the operation.
• Allow the user to either confirm the restoration (proceed with restoring the current entity and its dependencies) or cancel the operation.

2. Restore without Dependencies

• Allow the user to proceed with restoring the current entity without restoring its dependencies, if it's possible (entity is valid w/o this references)
• Display a warning message to the user, clearly outlining the risks of restoring the entity without its dependencies
• Require the user to explicitly confirm their decision before proceeding.

By implementing these two options, users will have greater flexibility and control over the restoration process, while also being informed of the implications of their choices.

What alternatives have you considered?

No response