 |
Command:
SCREEN LAYOUT ASSIGNMENTS
 |
Node: screen_layout_assignments |
|
Mandatory: |
no |
|
max. Occurrence: |
unbounded |
|
Description: This tag is used as container for commands regarding the button-assignment of Touch-Scales used in the Self-Service mode.
|
|
Notes: In the NSM form the UC3 application the content of this command is handled with NSM item 4+13.
For tactile UC3 devices the Self-Service Pictogramm-Buttons are defined with command
selfservice_keyboard_layout_configurations
For Touch UC3 devices PLU-keys for the Sales-, Prepack, Cash-Register- and Inventory-Mode are defined with command
keyboard_layout_configurations.
|
|
 |
|
|
 |
Node: screen_layout_assignment |
|
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 manipulating screen layout assignments.
|
|
Notes: For the mode ''readall'' the values of the elements <application_type> and <layout_type> will be evaluated. For the mode ''deleteall'' the values of the elements <application_type> and <layout_type> will be evaluated.
|
|
 |
|
|
|
 |
Tag: application_type |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
short |
|
Range: |
0 - 4
|
|
Nillable: |
no |
|
Description: The application type for what the information is desired.
Value |
Description |
0 |
Sales application (only theoretical - see the Notes) |
1 |
Cashregister application (only theoretical - see the Notes) |
2 |
Selfservice application |
3 |
Prepack 1 application (only theoretical - see the Notes) |
4 (only theoretical - see the Notes) |
Inventory application |
|
|
Notes: The command 'screen_layout_assignments' defines the assignment of PLU keys (pictogram keys) and
page keys for touch devices used in the self-service mode.
How to define PLU keys for the sales-, prepack-, cash register- and inventory mode(s) see command
keyboard_layout_configurations.
|
|
 |
|
|
|
 |
Tag: layout_type |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
string |
|
Range: |
max. 30 characters
|
|
Nillable: |
no |
|
Notes: The name of the layout type used in the touch layout XML file (created with the ScreenDesigner) for the button-assignment-setup.
Touch-Layout files created with the current ScreenDesigner Version 4.1.7 have fix coded the string "default" for the layout
type.
To use another string for the layout type is possible by changing the string "default" direct in the touch layout XML file
manually
with an editor. In this command screen_layout_assignment then must be used the same string for the tag layout_type.
|
|
 |
|
|
|
 |
Tag: item_name |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
string |
|
Range: |
max. 60 characters
|
|
Nillable: |
no |
|
Description: The name of the item.
|
|
Notes: The item name defines the button within the touch layout XML file. For the self service mode layout each button is
identified with the combination of page ID and button ID. For example means the item name "Category1.Preset1" from page
"Category1" the button element with the ID "Preset1". If there are more pages for one category marked with
#n at the end ( Category1#1, Category1#2, Category1#3, ...) the page identifier #n is ignored in the item name but finally
the combination of page ID and button ID must be unique to identify a PLU key (pictogram key) or page key.
Remark that page and button IDs are used key-sensitive!.
|
|
 |
|
|
|
 |
Node: properties |
|
Mandatory: |
no |
|
max. Occurrence: |
1 |
|
Description: Range of values: 2000 characters including the tag name of this and the subordinate tags.
|
|
 |
|
|
|
|
 |
Node: property |
|
Mandatory: |
yes |
|
max. Occurrence: |
unbounded |
|
Description: Each property is defined by a "name" an a "value" for a fixed text or a "reference" if the content of a database field has
to be used - for exapmle 'article.name' for the TLU of the PLU number.
|
|
 |
|
|
|
|
|
 |
Tag: name |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
string |
|
Range: |
- |
|
Nillable: |
no |
|
Description: In the following table are some of the possible names for the property tag.
Property name |
value
|
reference
|
disable |
1 - button is disabled 0 - button is enabled
|
--- |
event |
PLU_KEY
|
--- |
department |
DEPARTMENT number of the assigned article
|
--- |
plu_no |
PLU number of the assigned article
|
--- |
label |
Text for the preset button |
article.name or article.name_short |
image |
FILENAME of the bitmap file |
article.image
|
Property name |
value
|
reference
|
disable |
1 - button is disabled 0 - button is enabled
|
--- |
event |
PAGE_KEY
|
--- |
label |
Text for the page button |
--- |
image |
FILENAME of the bitmap file |
article.image
|
nextpage |
Touch layout page ID to jump to
|
--- |
|
|
 |
|
|
|
|
|
 |
Choice: |
|
|
|
|
|
|
 |
Tag: value |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
string |
|
Range: |
- |
|
Nillable: |
no |
|
Description: The value of the property.
|
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
Tag: reference |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
string |
|
Range: |
- |
|
Nillable: |
no |
|
Description: Reference to an existing property stored in the device e.g. article.image .
|
|
 |
|
|
|
|
|
|
|
|
|
 |
Tag: last_change |
|
Mandatory: |
no |
|
max. Occurrence: |
1 |
|
Datatype: |
dateTime |
|
Range: |
- |
|
Nillable: |
yes |
|
Description: 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
|
|
 |
|
|