Wiki Detay | wiki workcube

Upgrade, patch and pull operations are operations performed to obtain new versions, patches made in the system, innovations and the most up-to-date files. The upgrade screen essentially allows manual operations during version updates. The Release Notes page lists the current version of the server and any released versions. When you enter the versions, you can see the innovations and changes.

Lean Version Catalyst started to be developed with the philosophy of scale, performance and simplicity after the Holistic versions. Essentially, all these versions continue on the same basic structure. Therefore, it is a continuation of previous versions and full compatibility has been observed. As in previous versions, servers can be upgraded, patched or pulled.

You can access detailed information through the wiki article "What is Upgrade, Patch, Pull?".

Things to Consider Before Updating the Version

What to do before and after the upgrade of systems that will be upgraded to Lean.23.
wrk_query javascript function has been completely removed and is blocked by Plevne WAS security application. In codes written for addon or customization purposes, wrk_safe_query should be used instead of wrk_query.

To make the current version pullable and to receive updates continuously, you need to activate the upgrade feature with the Pull method.

For this, you need to go to the system parameter settings and confirm whether your Current Branch value in the Git Branche Change field is the version you want to run your system on, if not, enter the version of the version you want to run your system on in the Target Branch field.

For example; Current Branch: releases/Holistic.22, Target Branch: releases/Lean.23

After editing the Git Branch settings, git.self_pull = true, git.branch = Current branch: You need to define them as releases/Lean.23.

Git Access Code: When you click on the verification icon next to the git.password parameter value in the system parameter settings or when you click on the verification icon on the git password verification screen during the upgrade; It is automatically issued for systems with a valid subscription. If it does not come even after you click on the verification icon, you can ask it from Workcube.

You must have a valid bitbucket app password to pull, patch or upgrade Workcube. The files where Workcube is installed must be on git, and your bitbucket user code, which Workcube gives you and updates at regular intervals, must be entered correctly.

Hint: If this access code is correct, if you click on the bitbucket icon you see below, the app will automatically receive your password from the system bitbucket. Once you do this, it will be valid until the next access code you receive from Workcube.

DB Comparison and Difference Removal: 19.02.2023 DB with the main version while upgrading, patching and pulling with the merge process. and schema comparison is made with remote modeldb.

New definitions have been added for this process in the System Parameter Settings.

* modeldb.dbname = release_workcube

* modeldb.dbusername = release

* modelmodeldb.dbhost = *** System IP Address to valid subscribers

* modeldb.dbport = *** The system automatically gives the port to valid subscribers.

* modeldb.dbpassword = *** The system automatically gives the password to valid subscribers.

The comparison process after connection is automatic. will start. This process can take a long time! Additionally, your connection speed to the model database affects processing time. During this time, your system will remain in maintenance mode!

If you wish, you can do this manually later. To compare your database after the upgrade process is completed: "Control Panel > System > DEV Tools > SCHEMA COMPARE"

This development is used to automatically eliminate all schema, table, index and view differences between the version used and the current version in the distribution.

Data Services: In order to receive Workcube Data Services, "service.data_url" and "service.upgrade_url" fields have been added to the system parameter settings. In order to receive data services, these fields must be defined as "https://release.workcube.com".

Do not forget versions and data are distributed via release.

Things to Consider Before Updating the Version in Protein-Installed Systems

Your post-installation parameter settings have been previously updated. If not done, check. Enter your params settings on the protein.params page.
For the params settings to work; Create a protein.config file in the /AddOns/Yazilimsa/Protein/reactor/ folder and write main dsn in it.
*Protein.config does not come with the installation because it is in git ignore.
When systems that work without using parameters are upgraded, parameters are added. must be entered.

Warning to those who will upgrade! The Lean23 version is published as beta for testing purposes for 14 days from the beta release date.

To upgrade your system to the latest version, simply complete the following processes with Self upgrade.

Undo the improvements made to standard files.
Reset system parameter settings edit.
Switch to current version.
Run all Current WRO queries
Current Compare Database (Schema Compare)
Current Solution, Family, Module, Object, Widget, Install WEX, Output Template, Process Template and Languages
Restart your Workcube

Detailed information about System Parameter Settings can be found in the "System Parameter Settings" wiki article

You can access detailed information about the upgrade via the "Release Transition and Upgrade from Master" wiki article.

Tips

Record was not found

Feedback

Did you find this content helpful?

Please Write Your Feedback!

Name*

Last Name*

Email *

About Workcube Objects

Allows comparison of previous and next versions. Checks are made on the files by finding differences between branches.

Type: Dev Version: Cognitive v20 Licence: Standard Author: Workcube Core