Text synchronization
In Adonix softwares, the specific/custom developers can create texts (screen titles normally). These texts, stored in the ATEXTE table are automatically numbered up to 100,000. In absolute terms the number is not particularly important : if the elements are transferred by patch or by the copy of one folder to another, the message will be transferred with the number, but the number will not be protected during the integration if another message exists in the target folder.
This fashion of functioning works perfectly when not operating in a 3 level architecture (X3 folder, development folder, live folder) and that no different custom/specific developments are carried out in both the development folder and the live folder. If this is the case, there will be number conflicts (a single number having different texts in the two folders).
Because the validation of the folder transfers the specific/custom texts from the reference folder to the final revalidation folder, deleting those in the final folder. This way of operating signifies that there is the risk of losing the specific/custom texts in the live folder.
To avoid this problem, the first folder validation phase creates a copy of the live folder texts in the development folder, including renumbering those texts where a conflict exists. This phase, called Copy of the texts, is described in the corresponding technical annex (it is the fourth phase of the revalidation).
This phase can also be launched in a manual fashion using this function. It will therefore both :
- create if necessary, the texts in the APLSTD table located in the reference folder for the current folder.
- re-number the messages that are relocated in the dictionary elements that use them (potentially all the database tables that use data of the type ATX). These tables are listed below. It should be noted that no revalidation is necessary, the texts having been written in the generated source.
This function is therefore not normally very useful because the validation of the folder takes control of it all. It has however been conserved as a precaution and may be used on the recommendation of the support teams.