...
| Info |
|---|
See the following page to have a better understanding about the new setup interface : Wedia Config |
Starting version 2023.3.0, a new configuration interface has been provided to offer the ability to create and adapt libraries and metadata, define asset universes to organize their content, set up filters for quick and precise asset retrieval, establish terms and conditions, create links and menus to enhance the navigation , and fine-tune roles and permissions for seamless collaboration.
The following pages outline key areas that require attention and provide initial guidance for the migration process from an existing Wedia application.
| Page Tree | ||||
|---|---|---|---|---|
|
Migration to Version 2023.3.1 Required
The first step in the migration process is to upgrade the existing application system to the required version, 2023.3.1. This version contains essential updates and improvements that will enhance the system's performance, security, and functionality and enable the correct management of the application from the setup interface.
Roles
As part of the migration process, it is necessary to create new instances of 'pkgsecugroup' roles or retrieve the ones provided in the engine's nar (Native Archive) file. These roles play a crucial role in managing security permissions and access control within the system.
Security
To ensure the security of the migrated system, the following steps need to be taken:
a. Default and Development Domain Rules: The migration requires the inclusion of Default and Development Domain rules provided in the nar file. These rules define the initial security settings and permissions for various system components.
b. Adaptation of Legacy Rules with PKG_Security: If the decision is made to retain the legacy rules, it is important to note that the associated roles will not be administrable. Alternatively, the recommended approach is to rewrite the rules to reference 'roletemplate,' which allows for more flexible management of roles and permissions.
Structures:
During the migration process, it is necessary to add required tags to the relevant system objects. These tags, such as 'secugroup/all,' define specific security groups and access levels for various components of the system. Ensuring proper tagging is essential for maintaining security and access control in the migrated system.
Databases: A comparison between the existing '_portal' and the new 'starter-kit' databases should be conducted for portals that utilize 'portal@xxx.' This comparison will help identify any differences in the resolved JSON files, ensuring a smooth transition of data and functionality to the new system.
User Interface: Consideration needs to be given to the visual appearance of the application, including elements such as emails, colors, and overall user experience. Detailed guidance on how to address these aspects during the migration process should be provided.
This initial analysis and documentation outline the key areas that require attention during the migration of the existing application system to the new version 2023.3.1. By following the outlined steps and considering the necessary modifications and adaptations, a successful migration can be achieveduse the new setup interface. Further documentation and detailed instructions should be prepared to guide the implementation of each step in the migration process.