Window Types

Base Form

DUO is structured with a familiar base form and drop down menu. 

Essentials - Base Form

The database splash colour (company profile setting) is shown as a coloured line above the status bar unlike MYOB Exo which shows this as a background colour behind the company name.

Login Form

Login utilises the same staff stable entries at MYOB Exo for login name and password.

 

Essentials - Login Form

The database, login and password can be supplied on the command line so as to bypass the login screen (e.g. on a desktop shortcut).  The format is identical to that used by MYOB Exo.

Login Roles and Modules

DUO incorporates all modules within the one executable. You may have noticed the login screen above has a Role ComboBox (which MYOB Exo does not)

 

Essentials –Login – Role Selection

As all modules in DUO are in a single executable, the Role (defined in DUO Configurator) sets which module(s) the Role consumes a seat licence for. Example: warehouse personnel are likely to select the Warehouse role whereas GM and Admin staff are likely to select Default (meaning all available modules).

Menu entries in the site map are hidden for functions associated with a module that is not included in the role.

Access Rights

Access rights of any given staff member are controlled by the user’sr security profile set (Exocfg > Staff > Security Profiles). Each staff member has a Security Profile property in their staff record (Exocfg > Staff > Staff).  In most Exo databases there is only the single Default Security Profile. If you need to restrict access, then create additional levels and change the Staff > Security Profile property.

 

Essentials –Login –Security Profile

Access rights to any object or function have the following levels:

·         View Only: Cannot change anything.

·         Edit: Can change an existing object but cannot create or delete.

·         Insert: Can change and create an object but cannot delete.

·         Delete: Can change, create, and delete an object (Full Access)

·         Denied: cannot access the object even to view

Access rights also follow an inheritance path for any object or function. Where the ultimate parent is the profile setting DUO Default Access Level.  Screens in the System Designer have a Security tab where access rights to the object being designed can be specified.

 

Object Locks

DUO complies with the Exo model for Object Locks where on opening a transactional entity or similar a database entry records that the entity is in use by a particular computer to prevent simultaneous processing / updating of the same record.  When a conflict is detected a screen like the Exo one appears.

Essentials - Object Lock

The reply choices are the same as for Exo

Retry: Re-query the database to see if the lock has been relinquished by the other party.

Overwrite: Take ownership of the entity.  Before using this please ensure that this lock has been left behind by an abnormal termination of process and that the entity is not actually in use by the machine name shown.

Read Only: Proceed in read only mode (look but don’t change).  For some workflows this option may not be available.

Exit: Abort the attempt to take ownership of this entity.

Help About {summary}

As per most applications there is a Help > About screen to show Registration, Connection, Environment, Connected Users, and EULA information.

Essentials –Help About

As this screen shows a lot of information, we have provided a detailed description in a later section of this document, rather than include it here.

DyametaTechnology or your channel partner may require some of this information during a support call.

Search Windows

DUO supports searching for things like accounts and stock items.

Essentials -Search Grid {example}

Search grids can apply in two different workflows

·         As the basis for a workspace window to maintain or process the item that is being searched. These windows are typically launched from the base form menu. After a search selection is made, additional tabs are displayed. These may contain:

o   Processes applicable to the selected record e.g. picking in Scan Pick.

o   One or more dashboard tabs housing dockable widgets to show details associated with the selected record e.g. related customer and contact information.

·         As a lookup to complete a field or grid cell. This is the classic Select and Close workflow e.g. use ‘?’ in a form field to search for Debtor, Stock Item etc.

Search grids are discussed in more detail in the Classes section of this document. See class epSearchForm.

Dashboards

These are work space windows into which dockable widgets can be added.  Unlike the dashboard tabs of a search screen, there is no parent object class for the widgets to inherit. In the dashboard definition you can optionally set class=value parameters to ‘seed’ the widgets..

Widget Windows (dockable widgets)

These are windows of class epDockForm that can appear in a Dashboard tab of a Search Window or in a Dashboard work space. For more information on dockable widgets see the section Dockable Widget Classes.

DUO for EXO     DUO for EXO     © Dyameta Technology Ltd                     Previous Topic           Next Topic           Home