placeholder Command:  PROFILE ASSIGNMENTS 


Short version Long version Changes Example

Mandatory: no
max. Occurrence:  unbounded
Description:
This tag is used as container for commands regarding the assignment of profiles to devices.
Notes:
This command can be used for UC3 application versions 1.12.0 and higher. See more details in the note for the next Tag.

In the NSM of the UC3 application the content of this command is handled with NSM item 831.
 
Mandatory: yes
max. Occurrence:  unbounded
Supported modes: delete Delete the named item.
deleteall Delete all items.
read Read the named item.
readall Read all items from the desired device(s). This doesn't mean comparable reading as in the L2 protocol.
write Write the named item.
Description:
This command is used for managing device configurations.
Notes:
For the modes ''read'' and ''delete'' it’s possible to provide a valid configuration_device_no as filter and then only the configuration profiles matching this filter criteria are taken in consideration for the indicated action.
For the modes ''readall'' and ''deleteall'' it’s NOT possible to provide a valid filter. So always all profile assignments are taken for the indicated action.

This command can be used for UC3 application versions 1.12.0.0 and higher in combination with the commands configuration_profiles and independent_configuration_profiles.
With older version than V1.12.0.0 the functionality of this command was handled by other commands. See more details about this in the document Handling-of-TransUC3-configuration-data.

   
Mandatory: yes
max. Occurrence: 1
Datatype: short
Range: 1 - 999
Nillable: no
Description:
The device number that configuration is for.
   
Mandatory: no
max. Occurrence: 1
Datatype: string
Range: max. 50 characters
Nillable: no
Description:
A name that can be assigned for easier identification.
   
Mandatory: no
max. Occurrence: 1
Datatype: string
Range: max. 50 characters
Nillable: no
Description:
The name of the configuration profile from the file customer.ini assigned to this profile assignment.
A configuration profile in the file customer.ini is identified by the name used as prefix for section names following the pattern: [<profile_name>.<section name>].
For further information see the document Customer-ini-profiles
   
Mandatory: no
max. Occurrence:  1
Description:
The node contains the list of mode profile assignments referred by the profile assignment.
Each mode profile assignment is indicated by the combination (mode profile number, application mode, and mode number inside the sequence of modes with same type).
     
Mandatory: yes
max. Occurrence:  unbounded
Description:
Node corresponding to a mode profile used within profile assignment.
       
Mandatory: yes
max. Occurrence: 1
Datatype: string
Range: max. 20 characters
Nillable: no
Description:
The application mode corresponds to the specific area of application’s behavior that can be configured by a mode profile.

The following values are supported:
Value Description
sales Mode group configuration for application mode 'Sales'.
prepack1 Mode group configuration for application mode 'Prepack1'.
inventory Mode group configuration for all inventory application modes.
selfservice Mode group configuration for application mode 'Selfservice'.
cashregister Mode group configuration for application mode 'Cash Register'.

       
Mandatory: yes
max. Occurrence: 1
Datatype: int
Range: 1 - 999 999
Nillable: no
Description:
Mode profile number that together with application mode identifies uniquely this mode profile.
See in command mode_profiles the Tag mode_profile_no.
       
Mandatory: no
max. Occurrence: 1
Datatype: short
Range: 0 - 9
Nillable: no
Description:
The sequence index of the mode group if it’s type is inventory. Default value is 0.
The following modes are supported at the moment:
Value Comment
0 inventory
1 Mode1
The name for the mode can be set in the file customer.ini.
For that assign a name to sNameMode1.
2 Mode2
The name for the mode can be set in the file customer.ini.
For that assign a name to sNameMode2.
3 Mode3
The name for the mode can be set in the file customer.ini.
For that assign a name to sNameMode3.
4 Mode4
The name for the mode can be set in the file customer.ini.
For that assign a name to sNameMode4.
5 Mode5
The name for the mode can be set in the file customer.ini.
For that assign a name to sNameMode5.
6 Mode6
The name for the mode can be set in the file customer.ini.
For that assign a name to sNameMode6.
7 Mode7
The name for the mode can be set in the file customer.ini.
For that assign a name to sNameMode7.
8 Mode8
The name for the mode can be set in the file customer.ini.
For that assign a name to sNameMode8.
9 Mode9
The name for the mode can be set in the file customer.ini.
For that assign a name to sNameMode9.

   
Mandatory: no
max. Occurrence:  1
Description:
The node contains the list of 'mode independent configuration profile assignments' referred by the profile assignment.
Each profile is indicated by the combination (configuration profile number and configuration profile type) because the 'application mode' assumes an implicit value.
     
Mandatory: yes
max. Occurrence:  unbounded
Description:
Node that corresponds to a independent configuration profile used within profile assignment.
Notes:
For the <application_mode> value COMMON is assumed implicit, therefore it is not necessary as tag.
       
Mandatory: yes
max. Occurrence: 1
Datatype: int
Range: 1 - 999 999
Nillable: no
Description:
Configuration profile number that together with configuration profile type identifies uniquely this configuration profile.
See in command independent_configuration_profiles the Tag configuration_profile_no.
       
Mandatory: yes
max. Occurrence: 1
Datatype: string
Range: max. 20 characters
Nillable: no
Description:
The configuration profile type that corresponds to the specific area of application’s behavior that can be configured through a configuration profile.

The following values are supported:
Value Description
display Configuration for advertisement on ¼ VGA display.
report Configuration for reports.
printhead Configuration for detection and signaling worn out printer's heads.
rubberroll Configuration for detection and signaling worn out printer’s rubber roll.
verification Configuration for detection and signaling due date for scale’s verification / calibration.
repository Configuration for access to repository of updating archives.
printoutinfo Definition of printout template for ingredient information.
powermanagement Configuration of power management options like switch off of display.
Supported with version V1.14.0 and higher
printoutinfolabel Configuration of printing info label options like template definition, company text.
Supported with version V1.20.0 and higher
hinttext Configuration to set the frequency of showing hint messages separated for each operator.
Supported with version V1.26.0 and higher

       
Mandatory: no
max. Occurrence: 1
Datatype: short
Range: 0 - 2
Nillable: no
Description:
The sequence index of the independent item group if it’s type repository. Default value is 0.
The following values are supported at the moment:
Value Comment
0 Assignment for the first repository.
1 Assignment for the second repository.
2 Assignment for the third repository.
This element is supported with version 1.16.0.0 and higher.
If this element is missing repository 0 is the default.
   
Mandatory: no
max. Occurrence: 1
Datatype: dateTime
Range: -
Nillable: yes
Description:
The last time when the record was changed.
CCYY-MM-DDThh:mm:ss
The format is as following:
C = Century
Y = Year
M = Month
D = Day
T = Separator between date and time
h = hour
m = minute
s = second