Manage ERP Model Versioning and Origin Tracking

Versão de lançamento: Australia

Atualizado 12 de mar. de 2026

1 min. de leitura

THIS IS AN EXPRIMENTAL TEST TOPIC CREATED BY AI AND NOT EDITED OR REVIEWED - IT SHOULD NEVER BE MADE PUBLIC! Learn how to manage ERP model versioning and origin tracking to ensure effective model management and traceability.

Antes de Iniciar

Role required: erp_admin

Por Que e Quando Desempenhar Esta Tarefa

ERP Model Versioning and Origin Tracking is a feature that helps administrators manage and trace different versions of models. This task outlines the steps to ensure that models are versioned and their origins are accurately tracked.

Procedimento

Update the model with fields to capture its origin and version.

The origin field can have values such as new, cloned, or imported.

The model will now include the origin and version fields.
Create a new table to control the current working version in the development environment.

The table should include a boolean column to indicate if a version is locked.

The new table will manage the current working version and its lock status.
During export, update the model version and set the is_imported flag to true.

Lock the last version in the version table and create a new version entry.

The model version will be updated, the is_imported flag will be set to true, and the last version will be locked.
When cloning a model, set the origin to cloned.

Register the source model and add a version 1 entry for the new clone in the version table.

The new clone will have its origin set to cloned and a version 1 entry will be added to the version table.
Validate the sys_created_by field to ensure it accurately reflects the user performing the cloning action.

This validation is crucial even for background processes to maintain accurate traceability.

The sys_created_by field will be validated and updated to reflect the correct user.