Keep these considerations in mind each time you apply a promotion. To accommodate a particular situation, you could need to change some of these parameters.
The Promotion system uses a different set of files to hold, as backup copies, the original definitions and data of objects that are included in a change request. The naming conventions for these backup files are contained in the @PROM_BACKUPDS table. For more information on this table, refer to
@PROM_BACKUPDS Table.
Target or remote promotions can result in new objects being created on the receiving system. You must pre-set default access permissions for these new objects to address potential security concerns. If these permissions are not pre-set, invalid default values can be inherited from the receiving system.
When submitting a change request, developers must indicate the type of change request by assigning it a category, for example, enhancement or product defect. The TIBCO Object Service Broker system provides several pre-set category values in the CHG_CATEGORIES table. You can add to and modify this list at any time to suit your environment.