Upgrade Notes

When upgrading the database, review the following usage notes.

V2022.02

• Script Calls Previous Version. The v2022.02.002 script calls the localization files from the v2022.01.001 folder. This affects the following situation: if a new user purchases V2022.02, and if they want to develop their system based on schema database, and if they are using European language, they will see the non-translated English strings of 2022.02. The fix is to correct the paths in \dt\v2022.02.002\translation\update-translation-template-singlebyte.duw by replacing “v2022.01.001“ with “v2022.02.002“, and then execute the duw script. (AD-9931)

• Closing a Work Requests Generated from a Checklist. If you have to generate a new work request as an action for completing a checklist, you will encounter problems when trying to close this work request. The /webapp/projects/users/public/dt/v2022.02.003 folder contains a correction for OnSite pertaining to closing work requests that were generated as a follow-up action to a checklist question. Database administrators can apply the scripts as desired. (AD-9381, ON-971)

• Configure Application Parameters for CAD and BIM. From Smart Client, the "Configure Application Parameters for CAD and BIM" task is not set to load as Web Central view. You can correct this by using the Database Update Wizard to run a script in the /webapp/projects/users/public/dt/v2022.02.003, which sets the Task Type to "WEB URL." (AD-9381, ON-971)

• Database Update Wizard. Version-to-Version Database Update Scripts in SQL Format. When you generate sql for csv files, you may experience that the scripts do not properly separate statements. (AD-6177)

V.2022.01

• BMS Equipment Diagnostics Reports. V.2022.01 includes four Reports Central reports that analyze BMS equipment diagnostics and associated work requests. However, they are not automatically imported in the HQ sample database. If you desire to use these reports, import them manually by running the update-sample-data.duw script in this folder: %archibus%/projects/users/public/dt/v2022.01.001/sample-data/reports/update-sample-data.duw. (AD-7453)

• v2022.01.001 scripts. If you attempt to run the V.2022.01.001 DUW update scripts twice, the import will fail. The issue is that the connector with connector ID “connect_dp_em” was updated and then deleted in the v2022.01.001 script folder. The workaround is to create a connector with this ID before rerunning the script. You can run the below statement in the Database Update Wizard’s preview text box, or you can create the connector through the Configure Connectors view. As long as the record exists before the script is run, the script will not fail when it is run more than one time. (AD-8621)

  insert into afm.afm_connector (connector_id) values ('connect_dp_em');

V.26.3

• Oracle. Upgrade. The following error is expected in when running 26.3.001 duw scripts in Oracle: ORA-01440: column to be modified must be empty to decrease precision or scale. There are six fields that had a larger size and smaller number of decimals in the database than in the data dictionary in Oracle. The duw scripts will appropriately fail to reduce the size to avoid data loss. There is a script in \projects\users\public\dt\26.3.001\schema-template\update-schema-template.duw that you can run manually to reduce the size at the risk of data loss. The size of these fields will be corrected in released databases going forward. The fields are: (AD-6906)
  

  TABLE_NAME	FIELD_NAME	DATA_PRECISION	DATA_SCALE	AFM_SIZE	DECIMALS
  activity_log	hours_actual		0	10	2
  activity_log	hours_est_baseline		0	10	2
  activity_log	hours_est_design		0	10	2
  hactivity_log	hours_actual		0	10	2
  hactivity_log	hours_est_baseline		0	10	2
  hactivity_log	hours_est_design		0	10	2

V.26.2

• Room Amenities table. The DUW changes the structure of the Room Amenities table (rm_amenity), keeping the data records. In order to do so, it creates resource standards (resource_std records) from the amenity types (rm_amenity.amenity_type). Administrators may want to review the newly created resource standard. (AD-6092)

V.26.1

• Database Update Wizard. Workflow Rules. The DUW may fail if certain scheduled workflow rules are running at the same time as the update process. To prevent these failures, use this process:
  1. Set core.runScheduledRules=false in WEB-INF\config\core.properties.
  2. Start the application server.
  3. Run the Database Update Wizard.
  4. Set core.runScheduledRules=true.
  5. Restart the application server. (AD-3908)

V.24.1

• GDPR. Workflow rules. Workflow rules for GDPR need to be activated by running the script \dt\24.1.004\schema\sysadmin\gdpr\update-schema.duw (DB-361) (DB-362) (DB-366)