Update (GESAUPD)

Open: Development > Utilities > Patches

Presentation

Use the Update function (GESAUPD) to view all the dictionary updates that have been performed by a:

  • Standard patch installation
  • Hotfix
  • Folder validation

You can't use this function to create update records. You need to use the easy patching and folder validation functions to create update records in these system tables.

Records

The update lines are numbered in reverse chronological order. A record contains the following elements:

  • The sequence number in reverse chronological order
  • The impacted folder
  • The internal version number
  • The update type (local menu 54):
    • Standard update: update from a current version to a different version.
    • Hotfix: fix that does not update the version number.
  • The process type (local menu 61):
    • Integration: corresponds to a patch update.
    • Validation: corresponds to a folder validation.
  • The integration status (local menu 64): indicates the current status of the update. The last record corresponds to the last update installed.
    • The status can be:
      • Control OK
      • In progress
      • Ended
      • Error
      • Ended with warnings
    • If the status is Error, you need to review the log files before launching the update again.
    • If the status is In progress, it can either mean that:
      • You are connected to a folder where the update is running.
      • The update has been suspended because the server has stopped.
        You can click Status update to restart the update: this sets the update status to Error and you are then able to launch the installation again.
        You can only click the Status update button if the integration status is In progress.
  • The generation status, it can be:
    • Ended
    • Not applicable
    • Error
    • Ended with warnings
  • Date and UTC time at the end of the patch installation
  • Global log files. Two files can be displayed:
    • The log file of preliminary checks.
      For example, the checks that prevented the update from being completed.
    • The log file displayed once the validation is complete. For example, the generation of windows.

    These files can be opened using the Actions icon, Log reading option.

Tables

This function contains two tables:

  • Catalog
  • Detail

Catalog table

This table displays the catalogs that have been installed with the update. These catalogs are archives containing all the elements to be patched.

From this table, you can access two log files using the Actions icon:

  • The log file of preliminary checks
  • The log file of the update (integration)

The table columns are:

  • The log file name
  • The status
  • The language
  • The legislation
  • The product code
  • The log in check phase
  • The log in integration phase

Detail table

This table contains the details of all the elements included in the update. This includes:

  • The catalog
  • The object type
  • The related identifiers
  • The file name
  • The Creation action, if a new element is added, or the Modification action
  • The access path to the file during the integration
  • The line number of the entry in the catalog
  • The date + UTC time of the update
Click the Detail filter button to reduce the number of results in this table. This button allows you to filter results by any detail field from the Detail table. You can also:
  • Use an expression to filter results
  • Filter by different operations (equal, not equal, greater than, like, etc.)
When a filter is applied to the Detail table, the Data filter enabled message is visible.

Technical appendix

The tables that contain the update information (AUPDATE, AUPDATELINE, AUPDATEPATH) work as the ADOSSIER table: they are system tables that can only be stored in their root folder. If a given folder contains no records, Sage X3 isn't able to determine the current version of the folder and rejects any connection attempt.

You need to check that these tables are up-to-date. The update is performed in the following cases:
  • During the folder import using the console. The AUPDATEPARAM.ini file located at the folder root contains all the required values.
  • During a folder validation.
If a direct folder transfer is performed (by other means), you need to revalidate the folder to update the tables.