Field help (APATYPE)

The patch type can take the following values:

• Standard
  This patch can be installed on a folder list which will be given in the integration, in theory, this list contains the supervisor folder. In most cases (including for specific and vertical developments), this is the patch to use. Indeed, the delivery of specific or vertical developments does not rely on the patch type, but on the list of activity codes which are given in the corresponding table.
• Supervisor
  This patch will only be integrated in the supervisor folder. This type is used when the user wants to insert pre-setup elements such as import/export models, automatic journals and Workflow rules that could have been modified in the different folders. In order to avoid erasing the modifications carried out, the supervisor folder only is updated. It is used to have updated setup values in case of the creation of a new folder, and also to update manually by making copies in each folder after having used the existing comparison utilities.
• Specific
  This patch is identical to the standard patch but it is used when a screen is patched to delete the specific actions (SPE) not included in the patch. You must use this value if you need to modify the name of the specific process for a dictionary action on screens. This also applies to screens, objects, reports, formulae and inquiries.
  Please refer to the detailed technical appendix for further information.
• Vertical
  This patch is identical to the standard patch but it is used when a screen is patched to delete the vertical actions (SPV) not included in the patch. You must use this value if you need to modify the name of the vertical script for a dictionary action on screens. This also applies to screens, objects, reports, formulae and inquiries.
  Please refer to the detailed technical appendix for further information.
• Add-on
  This patch is dedicated to the add-ons. It is used to keep the actions on vertical fields (SPV) and the specific actions (SPE).

The patches containing documentation elements are specifically processed: this is described in the corresponding appendix.