1. General information


1.1. What is "object"

1.1.1. Object is a logical unit of the RK7.

1.2. Object properties

1.2.1. Object types

1.2.1.1. There are many of object types as the references are grouped in manager station menu.

1.2.2. Object statuses

1.2.2.1. Draft
1.2.2.2. Active
1.2.2.3. Inactive
1.2.2.4. Deleted

1.2.3. Object names

1.2.3.1. Name

1.2.3.1.1. This is the main object name that is shown in Applications GUI and printed.

1.2.3.1.2. The string should be inputed in currently set Main system (RK7) language.

1.2.3.1.3. Name length is limited to 40 symbols.

1.2.3.2. Alternative name

1.2.3.2.1. This is the object name in currently set Alternative language.

1.2.3.2.2. This string is inputed and saved using corresponding character set.

1.2.3.3. Short name

1.2.3.3.1. This is 10 symbol shortened object name.

1.2.3.3.2. It is usually used in printed documents (to fit memo width in 1 line) or in external applications.

1.2.3.4. Extended name

1.2.4. Object codes

1.2.4.1. Code
1.2.4.2. Ident

1.3. Rights on objects

1.3.1. For manager station

1.3.1.1. Manager station rights you set in employee role properties [Manager restrictions] section (available only for "Head office" roles).

1.3.1.2. With those privileges you protect corresonding objects and operations from being used by some role users (do not enable = set this possibility to false).

1.3.1.3. There are user-made and preset privileges. You may create new privileges in "Object privileges" reference.

1.3.1.4. Hence all settings are in 'inspector' area, you may restrict editability or/and viewability of them by Object type or/and Employee group (or for all objets - by default) in "inspector settings" reference. There are by parameter and by group of parameters options "Editable" and "Viewable" (disable = false = restirct edit or view).

1.3.2. For cash station

1.3.2.1. Cash station rights you set in employee role properties [Cashier restrictions] section.


2. Restaurant organizational structure


2.1. Corporation
2.2. Restaurants
2.3. Halls
2.4. Tables
2.5. Covers


3. Device organizational structure


3.1. By device type

3.1.1. Readers

3.1.1.1. Magnetic stripe (MCR)

3.1.1.2. Contactless (RFID)

3.1.1.3. Infrared (barcode, QR-code)

3.1.1.4. Dallas

3.1.2. Displays

3.1.2.1. Two line (customer display)

3.1.2.3. Second screen

3.1.3. Keyboard

3.1.4. Touch screen

3.1.5. Wireless receiver (guest call button)

3.1.6. Fiscal device (printer, module)

3.1.7. Printers

3.1.8. Raters

3.1.9. Dosers

3.1.10. Cash drawers

3.1.11. Wireless transmitter (pager)

3.1.12. Scales (http://support.ucs.ru/en/node/6773).

3.1.13. Bank card authorization terminal

3.1.14. Other

3.2. By driver for phisycal device

3.2.1. Port-connected

3.2.2. Plug and play (self install)

3.3. By logical device

3.4. Driver settings could be saved on reference server (defparams.ini file in \base\ folder).

3.4.1. You may save driver settings using RK7 manager station "save settings" option in popup menu: enter template name and press "enter".

Next time you add this driver, call "load settings" from popup menu in order to apply saved settings in current driver instance.

3.4.2. You might edit defparams.ini file manually: section name in driver name, keys are properties names and values are their default settings.


4. Network organizational structure


4.1. Interfaces

4.1.1. Interface drivers

4.1.1.1. First thing for the system to work is driver (associated library) with program code, that gives RK7 operational instructions.

4.1.1.2. On the "Drivers" tab select and add necessary interface driver.

4.1.1.3. Set driver properties.

4.1.2. Logical interface

4.1.2.1. Logical interface is a system organizational unit that have its corresponding driver links for device organizational structure units.

4.1.2.2. Go to "Service" -> "Interfaces". Create your own interface and set its properties or copy preset one. Mind selecting necessary drivers from list.
4.1.2.3. Please, do not assign one and the same interface driver to several logical interfaces.

4.1.3. High level server interfaces

4.1.3.1. For report servers there are no options for logical interface. You have to enable the interface by setting its port different from zero.
4.1.3.2. Go to "Options" -> "OLAP reports" -> "Reporting servers". Set properties of necessary server in "XML interface" section.

4.1.4. Interface monitoring

4.1.4.1. Cash server interface status you are able to check in its GUI corresponding tab (when started as "desktop").

4.1.4.2. Cash station interface status you are able to check in cash station "about" form "driver list".
4.1.4.3. Any network interface that utilizes TCP or UDP protocol you may check using TCPview (see in 6. http://support.ucs.ru/en/node/5532).

4.2. Ports

4.2.1. Unique

4.2.1.1. Never set the same port for different applications or even one application different interfaces that run on the one PC.
4.2.1.2. If you are not sure if the port is free or not, check that by some means (for example, TCPview utility by Microsoft Sysinternals).

5. User interface organizational structure


5.1. Forms

5.1.1. Form is a station full screen user interface "layout". Form determines what to draw on screen and where.

5.1.2. Read more about forms in manual http://support.ucs.ru/en/node/6317 .

5.2. Selectors

5.2.1. Selector is a changeable area on form which consists of pages. All selectors are inside some selector type (hierarchy group).

5.2.2. There could be one or more pages. In many selector types you may set page by default (that will be shown on start).

5.2.3. You are able to put objects of different types into 1 page, another pages of current selector among them.

5.2.4. Set corresponding 'Summon operation' to apply default behaviour for selected object type(s).

5.2.5. Selectors must be assigned to Usage with setting conditions like other usable object types.

5.3. Function keys

5.3.1. There elements are designed to be triggers for functions.

5.3.2. They are located in rk7man.exe Options -> User interface -> Function keys reference.

5.3.2.1. They are grouped in preset hieracy. Parent named as target selector type or design.

5.3.3. You can use these buttons in selector pages.


6. Application organizational structure


6.1. By application name (file)

6.1.1. Reference servers
6.1.2. Report servers
6.1.3. Cash servers
6.1.4. Cash stations
6.1.5. Print stations
6.1.6. Manager stations

6.2. By role

6.2.1. Servers

6.2.2. Clients


7. Document organizational structure


7.1. By purpose

7.1.1. Service

7.1.2. Regular

7.1.3. Report

7.2. By destination

7.2.1. For staff

7.2.2. For customer

7.2.3. For interface\machine\device

7.3. By place of issue

7.3.1. Front office

7.3.2. Back office

7.4. By type of data processing (report)

7.4.1. OLAP cube + FR2 layout (http://support.ucs.ru/en/node/5720)

7.4.2. SQL-cube + FR4 layout

7.4.3. Interactive dataset \ agregates (http://support.ucs.ru/en/node/7182)

7.5. By layout

7.5.1. Simple

7.5.2. Graphic