Synchronizing process attached objects
When an environment is migrated from an old version of the beqom application to beqom 9.1 or later, then the objects attached to processes need to be synchronized in order to make sure that they are properly visible and useable in the beqom application. This operation is required because of a change in database architecture that was introduced in version 9.1 of the beqom application. From this version, some information that was originally stored in the tenant database was move to a new, multi-tenant database called the Catalog Database. A number of application objects are stored in this database, such as process attached objects (reports, forms and documents.
This is an note/information message.
The operations outlined below need to be performed only once, during the migration of the tenant. Once they have been performed, the synchronization of objects is done by the beqom Admin Portal. There is however one notable exception to this principle, which is the case where a process is created/edited in SQL. In this case, it needs to be synchronized as well. See section Synchronizing a Process Created/Edited in SQL.
Permissions
In order to perform the synchronization operation on the objects attached to a process, you must use a user belonging to a profile that was granted the following access rights in the beqom application:
(Undefined variable: CompoVariables_AP.Admin): full rights on the "Synchronization & Data Security" page (Read, Modify, Delete, Create)
(Undefined variable: CompoVariables_AP.Data): component access
(Undefined variable: CompoVariables_AP.Process): component access
(Undefined variable: CompoVariables_AP.Rules): component access
For more information about permissions and the procedure on how to grant them, refer to BQM12 - [[[Undefined variable FAQ_Titles.BQM12]]].
Synchronization in Version 9.1
For a migration to version 9.1 of the beqom application, the following actions need to be performed:
Clean-up the tenant (this operation is only required if the UID reference records in the tenant database have been manually changed):
UPDATE k_referential_tables_views SET uid_datasource = NULL
UPDATE k_referential_tables_views_fields SET uid_datasource_attribute = NULL
UPDATE k_m_plans SET uid_object = NULL, uid_datasource = NULL
UPDATE k_reports SET uid_object = NULL
UPDATE k_m_plans_form_report SET uid_object_relation = NULL
Execute the following API method: Gateway, POST /api/ProcessExplorer/SynchronizeProcessAttachedObjects
Execute the following API method: Gateway, POST /api/Admin/SynchronizePlan
Synchronization in Versions 9.2 and 10
For a migration to version 9.2 or 10 of the beqom application, the following actions need to be performed:
Clean-up the tenant (this operation is only required if the UID reference records in the tenant database have been manually changed):
UPDATE k_referential_tables_views SET uid_datasource = NULL
UPDATE k_referential_tables_views_fields SET uid_datasource_attribute = NULL
UPDATE k_m_plans SET uid_object = NULL, uid_datasource = NULL
UPDATE k_reports SET uid_object = NULL
UPDATE k_program SET uid_object = NULL
UPDATE k_referential_grids SET uid_object = NULL
UPDATE k_m_plans_form_report SET uid_object_relation = NULL
Execute the following API method: Gateway, POST /api/ProcessExplorer/SynchronizeProcessAttachedObjects
Execute the following API method: Gateway, POST /api/Admin/SynchronizePlan
Synchronizing a Process Created/Edited in SQL
In the specific case where one or several processes are created or edited outside of the beqom application, via SQL, the process and its attached objects need to be manually synchronized.
To do so, proceed as follows:
Synchronize process attached objects using the following API method: Gateway, POST /api/ProcessExplorer/SynchronizeProcessAttachedObjects
Synchronize the process(s) using one of the following API methods:
Gateway, POST /api/Admin/SynchronizePlanById/{idProcess}: use this method if you want to synchronize one specific process
Gateway, POST /api/Admin/SynchronizePlan: use this method to mass synchronize all processes