Users and User Profiles

The following users are set up as DOKA-NG users. The names of the users correspond their banking-related function.

“SAS_… users” will be able to log into a SaaS MyModelbank environment only.

The user profiles reflect the scope of the activities and functions a user is permitted to perform. A user therefore will not have access to functions that do not form part of the user's field of activity.

For the purposes of the MyModelbank, the range of functions was split into several groups:

A clerk carries out transactions and has permission to generate reportings.

• Access to all business sectors including the appropriate transactions for the Information System
• Access to incoming processing
• Access to open or pending transactions
• Access to all statistics
• Access to such general standards as displaying files, changing password, changing the entity, staff replacement, sending messages

In addition to the functions accessible to a clerk, the officer also has access to typical verifier functions:

• Access to all business sectors including the appropriate transactions for the Information System
• Access to verification and release of transactions
• Access to incoming processing
• Access to open or pending transactions
• Access to all statistics
• Access to all transactions related to Static Data Maintenance
• Access to such general standards as displaying files, changing password, changing the entity, staff replacement, sending messages

The administrator has access to the typical range of functions of a system administrator:

• Access to incoming processing
• Access to the Workflow Manager
• Access to all system transactions
• Access to the assignment of user rights and profile maintenance
• Access to transactions handling patches
• Access to all transactions related to Static Data Maintenance
• Access to such general standards as displaying files, changing password, changing the entity, staff replacement, sending messages

The master has access to all DOKA-NG functions. This is particularly suitable for testing and/or demonstration purposes: as well as being able to access transactions specific to business sectors, the master can also access all the functions of the administrator.

The default profile contains only the basic functions available to every user.
The default profile is used by the system when a user has not been assigned to any specific profile.

Additionally the profiles “boot” and “sample” exist. “boot” is needed for the bootstrap package are used there. “sample” is used by transaction GENSML.

Using the application profile field, it is determined what queue entries (e.g. incoming, open, to be corrected, release, deadline) can be assigned to the user when deploying the manager for interactive queue entries (QUETSK). A list of possible entries is contained in a *.tda file in the ini folder of the application.

5 application profiles have been set up in the MyModelbank with these features:

• Clerk.tda - may be assigned to all queue entries apart from releases
• Officer.tda - can be assigned to all entries
• Release.tda - may be assigned only to releases (for the 'team heads' of the MyModelbank)
• Manager.tda - no queue entries are assigned (for the 'Branch Managers' of the MyModelbank)
• Admin.tda - no queue entries are assigned
  

Regardless of the range of functions, the application can be launched using a number of different starting transactions.

• 'OFFICE' has graphic elements representing a complete office scenario.
• Under 'OFFTEA' and 'OFFMIS', certain statistical data is presented in the form of graphics, providing a direct overview.
• In addition, the permitted functions can be made accessible in different ways using an Office menu.
• All Office menus and sub-menus can be adjusted to own needs via the relevant administrative transactions; even own menus can be defined here.

The following Office menus are available as user profiles in DOKA: