Copy parameter values
This function is used to copy the values of parameters defined at a given level (company, site, user, legislation) for a given code, to a group of destination codes (company, site, user, legislation, depending on the selected copy) defined by value range, using a template, or given in the form of a list.
This copy can be performed in simulation mode first (with or without details on the copied parameters).
Screen management
Entry screen
Presentation
A single entry screen makes it possible, when starting the function, to enter all the necessary parameters. When validating the entry, a confirmation is requested, then the function is launched, and a trace file reports on the result.
Close
Fields
The following fields are present on this tab :
Block number 1
| This field is used to define the folder from which the parameters are going be copied. The possible syntaxes are described in the dedicated appendix. |
| This field is used to define the folder in which the parameters are going be copied. The possible syntaxes are described in the dedicated appendix. |
| It defines the level of definition for the parameters to be copied The following values are possible:
|
|
|
| When this box is checked, the detail of the copied parameters along with their value can be obtained in the list. If it is not checked, only the list of the destination codes is displayed. |
| If this box is checked, the parameters copy is not carried out, and the log file provides the detail of the copies that would be performed if the operation were launched in a non-simulated mode (with or without the detail of the parameter values). |
| When this box is checked, a preliminary deletion of the parameters at the destination level is carried out before the copy. For instance, if parameters belonging to user A (some of whose parameters are inherited from the site) are copied to user B (some of whose parameters are defined at the level of the user themselves), then:
|
| It specifies the origin (company, site, legislation, user, depending on the case) of the parameter values to be copied. |
| Title associated to the previous code. |
Destination
| It defines how to enter the destination codes (company, site, legislation, user), according to the following possibilities:
|
| When the parameter copy is performed to a destination defined by ranges, these two fields are used to specify the start and end codes concerned. Depending on the case, company code ranges, site code ranges, legislation code ranges or user code ranges are entered here. |
|
|
| When the parameter copy is made to a destination defined by a template, the template concerned is entered here. According to the case, a company, site, legislation or user code template is entered here. |
Table List
|
|
| When the parameter copy is made to a destination defined by a code list, the codes concerned are entered here. According to the case, company codes, site codes, legislation codes or user codes are entered here. |
| Title associated to the previous code. |
Close
Messages in the trace file
The trace file provides information in the following form :
Level Origin: NAME
NN Copied parameters
Parameter NAME: VALUE ( Title )
Level Destination: NAME
NN Copied parameters
Parameter NAME: VALUE ( Title )
where:
- Level corresponds to the company, site, legislation or user
- NN provides the number of concerned parameters (copied, following the line of origin, deleted, on the destination level, remembering that this line is not present if no parameter value has been deleted).
- The detail lines with each parameter and its value are only present if the Detail box is checked.
Remarks
If parameter values existed for a given destination code, and do not exist in the start code, these values are deleted. For instance, if the CALNBRDEC parameter is set to the default value 2 for the folder, and is not defined at user level for the only user JOHN:
- a copy of the parameters for the user JOHN to the user JIM is going to copy this parameter value.
- Inversely, a copy of the parameters of the user JIM to the user JOHN is going to delete this parameter value for the user JOHN (since considering that the user has no value as such, but they have to inherit the value of the upper levels).
This rule also applies when performing copies between folders. In this way, the copy of the parameters associated with JOHN in folder 1 to the user JIM in folder 2 is only going to recopy those parameters specific to JOHN (if parameters were inherited from the site, the company or the folder, they will be inherited from the site, the company or the folder, in other words, the inherited values may not be identical). If need be, it is then possible to copy the parameters of JOHN's site to JIM's site, those of JOHN's compnay to JIM's company etc.