Individual Customizings and Update Safety

Individual Customizings

General

For individual customizing, please consider the notes in PLANTA customizer
The name allocation must be subject to a convention to be defined, which must not intersect with the names of standard objects. The recommended procedure is to place the license number in the form “L[nr]_project_id” in front of the column or generally DB object names.
When you create real individual DIs, you also have to make sure that you select a DB position which cannot be reached by the standard (e.g. starting from 5000).

Rules for the most frequently performed changes made to standard objects

Adjustment	To be considered
Module, panel, module variants, data field, and data item name	All names must be adjusted in all licensed languages. In the standard documentation (PLANTA Online Help), the standard name will still be used.
Data item name	Integrity Some fields (e.g. project) are used directly or indirectly via Fetch exits in further data tables; sometimes also in abbreviated form (e.g. task/TA) Some fields have a corresponding data field (e.g. manager name as ID and as incarnation field) In some modules, the DF heading is displayed instead of the data item name Impact on layout For different lengths, the change has an impact on form or print layouts
DF length of a data item	Impact on form or print layouts Adjust data content before a data item is shortened.
Data area, work area, role assignment, listboxes	Before you make any changes, you have to check the frequency of use in order not to change other objects simultaneously by mistake. Recommendation for multiple usage: Copy standard object ( = individualize) and replace it with the copy in the required assignment Adjust copy

Information

Objects of the standard system (e.g. user roles, work areas, listbox values, data areas, data fields, data items) are reset to PLANTA’s standard settings in every update. These may vary between versions due to further development.
If you do not want changes to be made by the new PLANTA standard system during update, you should set up your own customizing objects such as modules and data areas, as they are not changed by the update.
- This can be done by copying standard objects, which can be adjusted subsequently.

Change Standard Objects

In some cases, the complete individualization described above is not realizable by copying - or not realizable with reasonable effort - and therefore standard objects are changed.
In order for the changed positions not to be simply overwritten during update, PLANTA makes a new conflict management procedure available with the help of which you can identify individual changes made to PLANTA standard objects and apply solutions for conflicts. This procedure replaces the previous manual writing of In Case of Update (ICOU).

Which changes are ICOU-relevant:

If parameters of the standard objects are changed, they will be reset to their default values after the update.
If an assignment in a standard object is deleted, it will be available again after the update.
If an individual object is assigned to a standard object additionally, this assignment is maintained when performing an update.
In general, the license of the record is decisive: Customizing records with a PLANTA license are changed, customizing data records with a customer license remain unchanged.

Example

Standard module 004711 has been changed:
- data field 999001 was adopted to standard data area 004712
- in standard data area 004713, the default value of data item 004714 was changed from @Y to @N.
- individual data area 999002 was assigned instead of standard data area 004714.
After the update,
- you have to check whether
  - data field 999001 in standard data area 004712 is still correct (e.g. layout parameters in forms)
  - the parameters of individual data area 999002 are still correct (e.g. pos, o-pos, satisf. rule, etc.)
- reset the default value of data item 004714 in standard data area 004713 to @N
- delete the assignments (available again now) of standard data area 004717

Information

If the module has been exchanged completely in the standard (new ID), the variants get lost.
If a module has only been changed, individual variants are retained but may have to be adjusted manually to the changes made to the base module.
This applies to both system wide and customized module variants.