User
Description
This app is used to maintain the users who are allowed to use your ClassiX® applications. In addition to a user's login information, such as ID and password, access rights can also be defined here.
As a rule, it is the "own" employees of the clients defined in the system who are users. Being a user therefore means that a person - in addition to their role as an employee - has the additional role of user. The entry of a user is therefore actually the entry of a user role.
This also makes it possible to assign user roles to contact persons of other companies. Unlike employees, contact persons of other companies do not have an employee role as an employee of a "system client", but a contact person role as an employee of another company. This means that these persons can also be given another role as a user of their system. (e.g. their tax advisors or auditors - but also temporary agency workers - who continue to be and remain the contact person of the external company).
If such "external" users also carry out activities in which, for example, documents are created with input/output of contact data, it makes sense to store this contact data (e-mail, telephone extension number) - purely in the role as user - directly at the user role. Otherwise, there is a risk that the system will take over the contact data of the "foreign" contact person role when printing a document or sending an e-mail.
Even if, for example, the employees in the sales department are only to be contacted via a collective e-mail (e.g. sales at myCompany.com), this collective e-mail can be stored for each of these users in their user role. In the employee role itself, the actual contact data for internal company traffic can then remain unchanged and unmistakable.
In addition to the user role-specific contact data, a user can also be assigned his or her own first place of work.
In addition to user roles that can be assigned to a natural person, one occasionally needs user roles that cannot be permanently assigned to a specific person. This is the case, for example, if the system is to be used by "third parties", e.g. for anonymous use via an interface (API). For such cases, user roles can also be assigned to companies (legal persons). Whether the assignment is made to one's own company (e.g. for night runs) or to a third-party company (e.g. the operator of the online shop that transmits data) is not relevant here.
In principle, it is also possible to create user roles without any assignment to a natural or legal person. However, the change history of data then also has gaps.
Functionality
Input window
- User
- Security
- Settings
- Surface
- Start script
- Interval checks
- Assignments
- My Apps
- Form printer
- Representative
This window is for user maintenance. You can select a user by entering the required abbreviation in the User ID field and confirming with RETURN. If you want to open the list window, you can select the menu item "Search".
The login name (user ID) and password must be entered.
Furthermore, the personnel number and also a time limit for the validity of the login can be added. In the lower area of the window, it is also possible to define restricted access rights.
If you have just created your login here when using the system for the first time, please log in to the system again.
Since a real person should be assigned to the login if possible, it is recommended to first create the personal data in the ClassiX® partner administration. You can also do this later. In general, however, you should keep in mind that 'user' is only the role of one person, and one person may have several roles. If you first create the person and then assign one or more roles to this person, you can avoid double entries and you will always have your data well structured.
However, system users do not have to be created as persons at the same time!
| Menu item | Description |
|---|---|
| Edit | - |
| : Person | - |
| Select | - |
| : : Employees | Assign employees to the user |
| : : Person | Assign person to user |
| : Create | - |
| : : Employees | Create a new employee |
| : Communication | If the user - as a user - has different contact details than those he has in his (internal) employee role or his (external) contact person role, then these can be entered here. |
| : : Insert | |
| : : : Telephone | Adding a new fixed telephone number for the user |
| : : : Mobile phone | Insert a new mobile phone number for the user |
| : : : Fax | Inserting a new fax number for the user |
| Inserting a new e-mail address for the user | |
| : : : WWW address | To insert a new WWW address for the user |
| : : Edit | Edit the object selected in the "Business Communication" list |
| : : Delete | Delete the object selected in the "Business Communication" list |
| : : Contact | Contact the person in the "Business Communication" list, i.e. if you have a telephone number (if TAPI is installed) call them, if you have an e-mail address (if Outlook is installed) open Outlook, if you have a WWW address open the browser with this URL |
| : User hierarchy | Calling up the user hierarchy |
| : User settings | Edit user settings of the user. |
| : Document settings | Open document settings |
| : Create activity document | - |
| : : Note | Creating an activity document for an ink note |
| : : Letter | Generate transaction document for a letter |
| : : Fax | Creating a transaction document for a fax |
| - | |
| : : : Writing | Generate transaction document for an email |
| : : : Import from Outlook | Importing a transaction document of an email from Outlook |
| : : Phone call | Creating an activity document for a telephone call |
| : : Meeting | Generate activity document for a meeting |
| Close | Close window |
| Search | Call up list window |
| Symbol | Description |
|---|---|
| Creating a new user | |
| Save changes | |
| Print user | |
| Edit person | |
| Edit employees | |
| Open the user’sdocument settings | |
| View favorites of the current user. | |
| Processes of the user | |
| Generate transaction document | |
| Recalling the user's saved lists |
| Field | Description | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| User | ||||||||||||||||
| : Identification | - | |||||||||||||||
| : : User ID | Login Name of the user (If there is already a User ID of another valid user, the entered User ID is completed with a consecutive number at the end). This field is a mandatory field. | |||||||||||||||
| : : System number | Sequence number automatically assigned by this machine (cannot be edited). | |||||||||||||||
| : : Person/Company | Person or company assigned to the user role. Without an assignment of the user (role) to a person or company, the "user" is only known in the system with the user code. The search for persons can also be carried out via the employee or contact person role. In principle, the system can only be operated with a user role, i.e. even without the user role being assigned to a person or company. All processes are also only assigned to the user role, but only employees of the registered client or contact persons of external companies are authorised to process documents. | |||||||||||||||
| : Authentication | - | |||||||||||||||
| : : Password | Enter the password or set a new password using the button of the same name. Here you can set a new password - e.g. by the system administrator - WITHOUT entering the old password. This field is a mandatory field, because even if you want to use the single sign-on functionality(SSO), a password must be set for ClassiX in order to be able to log in as a ClassiX user at another workstation (provided by another Windows user). After a password has been reset, the login failure counter is automatically initialized. | |||||||||||||||
| : : Validity | Specify the validity of the password as a time period (dd.mm.yyy - dd.mm.yyyy) | |||||||||||||||
| : : : Windows SID... | Windows SID assigned to the user for single sign-on(SSO) functionality. With the adjacent button ... you can list all Windows users and select the appropriate user. This requires Windows rights to read the AD. | |||||||||||||||
| : Representation (signature regulation purchase) | The user can adjust their substitutions for the signature rule here. | |||||||||||||||
| : Communication | - | |||||||||||||||
| : : First place of work | As a rule, a user's first place of work is that of his employee role. However, this can be overwritten specifically for each user. | |||||||||||||||
| : : Business communication | Specification of the user's contact details (telephone, mobile phone, e-mail, etc.), if different from his contact details as an employee of the client or as a contact person of an external company. Also in the case that, for example, the employees in sales are to be contacted via a collective e-mail (e.g. sales at myCompany.com), these can be stored here for these users. | |||||||||||||||
| Settings | ||||||||||||||||
| : Registration | - | |||||||||||||||
| : : Lock status | Output of the accumulated failed attempts at registration. The last two digits indicate the number of failed attempts until a temporary lockout, the first two digits indicate the number of temporary spears (until the user is completely locked out). The number of failed login attempts after which a temporary or complete block is issued by the system is defined in the client. | |||||||||||||||
| : : per date / um | Displays the date and time of the last failed login attempt. | |||||||||||||||
| : : Initialise | Press this button to reset the failed attempts counter. | |||||||||||||||
| : Logout/System auto | ||||||||||||||||
| : : Automatic logout after | Specify the number of minutes of inactivity after which the user is automatically logged out of the system. If no value is set here, the settings from the client apply. | |||||||||||||||
| : : : Last logout / um | Output the date and time of the last logout. | |||||||||||||||
| : : Close dialogues automatically after | If the value is zero or disabled, the value from ‘Automatic log-off after’ is used. If this is also zero, dialogues are displayed indefinitely. Dialogues include error messages, file selection, prompts, etc. The display of a dialogue for an unlimited period also means that the programme waits at this point for a response from the user; in other words, programme execution pauses at this point. If no value is set here, the settings from the client apply. At the very least for user accounts that perform automatic, unattended tasks (e.g. independent execution of application calendarsor autonomously acting AI agents), a value should always be entered here to at least abort those programme steps that cannot proceed without manual input, so as not to block any subsequent programme steps. | |||||||||||||||
| : Language | - | |||||||||||||||
| : : Preferred language | Set preferred language. All screen templates are preset for the user with this language | |||||||||||||||
| : : Standard language | Set the default language (of the system) | |||||||||||||||
| Telephone | - | |||||||||||||||
| : : Standard device | Set default for the standard device with TAPI interface when calling the telephone module | |||||||||||||||
| : : Ringtone | Set the default ringtone when calling the telephone module | |||||||||||||||
| : : Number of calls in call history | Specifies how many call records to display in the history of the phone module | |||||||||||||||
| Security | ||||||||||||||||
| : Access rights | To assign access rights to a user, you must first create them as access objects. Then they can be assigned to or removed from the user via the "Insert" and "Remove" buttons. Attention! The different access rights that can be assigned to a user are: Note!
Note! | |||||||||||||||
| Start script | ||||||||||||||||
| : Start script | A start script (InstantView® script) that is automatically executed once directly after this user logs in. With such a start script, one instructs the system to execute certain functions directly. The following is a small list of frequently used functions:
| |||||||||||||||
| : Testing | The start script is executed on a test basis. | |||||||||||||||
| : Changeable by user | The user settings allow the user to change the values for the interval check continuously. | |||||||||||||||
| : Inherited | If a check mark is set, the fields (except for "Can be changed by user") cannot be changed and receive their settings (which can now also be seen here on the screen) from higher-level cost centres or the client. | |||||||||||||||
| : | The question mark button takes you to the editing mask of the object from which the settings have been inherited (if appropriate permissions are available). If there are no authorisations for opening the object, you can move the mouse over the button, which displays a tooltip indicating from which object the data was inherited. | |||||||||||||||
| Interval checks | ||||||||||||||||
| : | The interval checks and start scripts are inherited from top to bottom in the hierarchy. This means: If these settings are set in the client, they are valid for all users until the user's cost centre, a higher-level cost centre or the user himself has changed these settings on the corresponding editing masks. | |||||||||||||||
| : : Check resubmissions | This enables the checking of transaction documents with the transaction type "planning", which are created with a resubmission date with or without a time. The resubmissions of the logged-in user can be queried on an interval-controlled basis. Messages that have an earlier or current date for resubmission and the status "Read" is not set are then automatically displayed on the screen. | |||||||||||||||
| : : Interval | Time interval, at which intervals it should be checked whether resubmissions exist. (e.g.: 30 min) | |||||||||||||||
| : : : Changeable by user | The user settings allow the user to change the values for the interval check continuously. | |||||||||||||||
| : : Inherited | If a check mark is set, the fields (except for "Can be changed by user") cannot be changed and receive their settings (which are also currently visible here on the screen) from higher-level cost centres or the mandate. | |||||||||||||||
| : : | The question mark button takes you to the editing mask of the object from which the settings have been inherited (if appropriate permissions are available). If there are no authorisations for opening the object, you can move the mouse over the button, which displays a tooltip indicating from which object the data was inherited. | |||||||||||||||
| : : Check system messages | The system messages of the logged-in user can be retrieved at intervals. If there are new messages that have not yet been moved to the "Read" status or with a later date for resubmission, they are automatically displayed on the screen. | |||||||||||||||
| : : Interval | Time interval at which the system checks whether system messages are available. (e.g.: 30 min) | |||||||||||||||
| : : : Changeable by user | The user settings allow the user to change the values for the interval check continuously. | |||||||||||||||
| : : Inherited | If a check mark is set, the fields (except for "Can be changed by user") cannot be changed and receive their settings (which are also currently visible here on the screen) from higher-level cost centres or the mandate. | |||||||||||||||
| : : | The question mark button takes you to the editing mask of the object from which the settings have been inherited (if appropriate permissions are available). If there are no authorisations for opening the object, you can move the mouse over the button, which displays a tooltip indicating from which object the data was inherited. | |||||||||||||||
| Assignments | ||||||||||||||||
| : responsibility purchasing department | The purchasing areas for which the user is responsible are listed in the list box. It is possible to assign further purchasing areas to the user by dragging and dropping. Only purchasing areas from PURCHASING_GROUPS can be assigned. | |||||||||||||||
| : : Insert | Assign responsibility for a purchasing area | |||||||||||||||
| : : Remove | Remove responsibility for a purchasing area | |||||||||||||||
| Domains | ||||||||||||||||
| Domain Declarations | Here, objects within the database can be divided into domains using domain declarations. | |||||||||||||||
| Form printer | Display of all forms in the database with the set printers
After selecting a form, the printers can be entered in the lower section of the window and saved for the user. By emptying the fields or entering the form printers, the user printers for the form can be reset to the standard. | |||||||||||||||
| Representative | ||||||||||||||||
| : My representatives | Define people who can represent the user.
| |||||||||||||||
| Log file | History of when, who used the substitution. | |||||||||||||||
| : My substitutions | List of persons the user can represent. To do this, the user account must have the system access right "Allow alias login". | |||||||||||||||
| : Log file | History of when, from which user the substitution was taken over. | |||||||||||||||
| button | Description |
|---|---|
| User | |
| : Set new | Enter new password in the input field of the called window |
| : Person / Employee | Select person / employee |
| Security | |
| : Access rights | - |
| : : Check | Check access to messages and classes, see |
| : : Synchronize | Adopt the same access policies of another user. |
| : : Insert | Insert access right |
| : : Remove | Remove access right |
| : : | Switch between tree and list view. |
| Settings | |
| Telephone | - |
| : : Standard device | Select default device for the TAPI interface |
| : : Ringtone | Select a ringtone |
| Status bar | |
| OK | Changes to the user are saved. If no changes are made, the button is locked. |
| new | The input window is cleared. |
| Close | The window is closed without saving changes. If you want to save the changes, you must press the "OK" button. |
List window
Used to list the users.
| Menu item | Description |
|---|---|
| Edit | - |
| : Application status | - |
| : : Log out | These menu items are for purely administrative purposes, e.g. after a system crash, i.e. when users have not been able to log off properly. |
| : : : with (current) timestamp | The users selected in the list are registered as logged off from the system - by setting the current time stamp. (Only change of status!) |
| : : : Reset only Login status | The users selected in the list are registered as logged off from the system without setting the current time stamp. (Only change of status!) |
| : : Set registration status to "active | For the users selected in the list, their login status is set to "active". |
| : Parse log files | The log files are parsed (read in) for the logged-in user and the evaluation is displayed in the Evaluation Log File app. |
| : Operations | Show processes of the last selected user. |
| : Initialise user lock | For the users selected in the list, the counter of failed login attempts is initialised to zero. A user is automatically blocked by the system (i.e. this user cannot log in again) if they have entered the password incorrectly several times. The number of possible failed attempts is defined here. |
| : Issue new temporary passwords for selected users. | E-mails (with text of the document template "NEW_PASSWORD_MAIL") with random, temporary passwords are sent to the selected users. This process corresponds to the procedure as if the user should have requested a new password for himself ("forgotten password"). The temporary password is only valid for 3 days at a time, the user must - after logging on to the system with the temporary password - assign a new password. |
| : Windows user | With the sub-items of this menu ClassiX users can be synchronised with the users defined in the Windows network. This is a prerequisite for a single sign-on |
| : : Import Windows users | From a list of all Windows users, the users can be selected to be created as Classix users with the same name. The Windows SID is also transferred in addition to the name. After the transfer all newly created ClassiX users are listed |
| : : Windows SID | - |
| : : : Set automatically | For each user selected in the list, the SID of the corresponding Windows user is automatically taken over if the user name is the same |
| : : : Remove | For the users selected in the list, their Windows SIDs stored in ClassiX are removed |
| Close | Close window |
| Options | - |
| : Validity | - |
| : : valid users | Display only valid users |
| : : all users | Show all users |
| Symbol | Description |
|---|---|
| Creating a new user | |
| Edit user | |
| Print user list | |
| Searchfor characteristics | |
| Search for objects that do not contain any of the characteristics to be specified (regardless of the value set) | |
| Empty list and delete search terms | |
| Edit person | |
| Edit employees | |
| Viewing the current user's favourites | |
| Show processes | |
| Generate transaction document | |
| Set validity | |
| Copy all users to the clipboard |
| Field | Description |
|---|---|
| User | Search by user login name |
| Employees | Search by employee name |
| button | Description |
|---|---|
| Edit | The current user is displayed in the input window. |
| New | An empty input window opens. |
| Delete | The selected user is deleted. |
| Close | The window is closed. |
Selection window
This window is used to select a user.
| Menu item | Description |
|---|---|
| Options | - |
| : Validity | - |
| : : valid users | Display only valid users |
| : : all users | Show all users |
| Field | Description |
|---|---|
| User | Search by user login name |
| Employees | Search by employee name |
| button | Description |
|---|---|
| OK | The selected user is applied. |
User settings
This window allows the user logged in to ClassiX® to set his own settings. This window differs from the editing window in which the administrator can set the user settings. In contrast to the editing window, administrative settings, such as access rights, cannot be changed via this window.
| Menu item | Description |
|---|---|
| Edit | - |
| : Change password | Reset the user's password |
| Access keys | Specifying access keys for the user |
| : Document settings | Call up the user’sdocument settings |
| Field | Description |
|---|---|
| User | |
| : User ID | Login User Name (If there is already a User ID of another valid user, the entered User ID is supplemented by a consecutive number at the end). |
| : Number | Personnel number |
| : Password | Set a new password using the button of the same name |
| : person/employee | Person/employee assigned to the user |
| Representation arrangements (authorisation procedure) | |
| : : Representation | This button can be used to define the representative and the period of representation. Before the substitution is defined, all open requisitions, orders and purchase invoices should be approved, as the substitution rule only applies to the new documents. |
| : : Deputy | In contrast to a substitute, a deputy can be run in parallel and only makes sense with the attitude "... only allowed by selected approver" in the client. The check is hierarchical, i.e. the deputy of the deputy can also approve! The documents are not displayed in the deputy's approval folder. |
| Substitution (signature regulation purchase) | |
| : : for 1st signature | Define a substitute for the 1st signature when ordering. Another user can be defined with or without a time period. This user also gets the orders to be signed displayed. |
| : : for 2nd signature | Define a substitute for the 2nd signature on the order. Another user can be defined with or without a time period. This user also gets the orders to be signed displayed. |
| System | |
| : Language | - |
| : : Preferred language | Set preferred language. All screen templates are preset for the user with this language |
| : : Standard language | Set the default language (of the system) |
| Telephone | - |
| : : Standard device | Set default for the standard device with TAPI interface when calling the telephone module |
| : : Ringtone | Set the default ringtone when calling the telephone module |
| : : Number of calls in call history | Specifies how many call records to display in the history of the phone module |
| Printer | - |
| : : Standard printer | Here you can select a default printer and a second printer for the copies. If these printers are set, the print dialogue for printer selection is omitted during output. |
| : : Copies | |
| User ergonomics | |
| : Window positioning | - |
| : : Save last positioning | - |
| : : : Transient | Specifies whether the position of an open and moved window should be remembered transiently (only during a session) |
| : : : Persistent | Specifies whether the position of an open and moved window should be remembered persistently (even beyond a session) |
| : : : Delete | The window positions stored persistently (in the registry) are deleted from it |
| : : Use saved positioning | Indication whether the transient or persistent positions of a window should be used or the positions as defined in the program script should apply |
| Start script | |
| : Start script | The startup script can be changed in the settings only if the administrator has allowed it in the user. A start script that should be executed once once the user has logged in. InstantView® script that runs automatically immediately after login. If, for example, the birthday calendar is always to be called for the period "from today, 1 week", the following script must be entered CreateTransObject(CX_SPAN_DATE) "today" Over Put 1week Over Put(duration) SendMsg(SHOW_PERSON_BIRTHDAY) |
| : Testing | The start script is called for testing purposes |
| : Inherited | If a check mark is set, the fields (except for "Can be changed by user") cannot be changed and receive their settings (which are now also currently visible here on the screen) from higher-level cost centres or the mandate. |
| : | The question mark button takes you to the editing mask of the object from which the settings have been inherited (if appropriate permissions are available). If there are no authorisations for opening the object, you can move the mouse over the button, which displays a tooltip indicating from which object the data was inherited. |
| Interval checks | |
| : | The interval checks can be edited in the settings only when the administrator has allowed it in the user. |
| : : Check resubmissions | This enables the checking of operation documents with the operation type "Planning", which are created with a resubmission date with or without a time. The resubmissions of the logged-in user can be queried on an interval-controlled basis. Messages that have an earlier or current date for resubmission and the status "Read" is not set are then automatically displayed on the screen. |
| : : Interval | Time interval, at which intervals it should be checked whether resubmissions exist. (e.g.: 30 min) |
| : : Inherited | If a check mark is set, the fields (except for "Can be changed by user") cannot be changed and receive their settings (which are also currently visible here on the screen) from higher-level cost centres or the mandate. |
| : : | The question mark button takes you to the editing mask of the object from which the settings have been inherited (if appropriate permissions are available). If there are no authorisations for opening the object, you can move the mouse over the button, which displays a tooltip indicating from which object the data was inherited. |
| : : Check system messages | The system messages of the logged-in user can be retrieved at intervals. If there are new messages that have not yet been moved to the "Read" status or with a later date for resubmission, they are automatically displayed on the screen. |
| : : Interval | Time interval at which the system checks whether system messages are available. (e.g.: 30 min) |
| : : Inherited | If a check mark is set, the fields (except for "Can be changed by user") cannot be changed and receive their settings (which are also currently visible here on the screen) from higher-level cost centres or the mandate. |
| : : | The question mark button takes you to the editing mask of the object from which the settings have been inherited (if appropriate permissions are available). If there are no authorisations for opening the object, you can move the mouse over the button, which displays a tooltip indicating from which object the data was inherited. |
| : : : Disable check for current session | If the checkbox is set, the interval check for the current session is switched off, if ClassiX is restarted this setting is lost ! It is thus possible to switch the check temporarily ON or OFF. |
| My Apps | Enter menu items that are called up in the "My Apps" window. This function allows each user to quickly call up his or her most frequently used programs. It is also possible to define programme calls via the cost centres. These are added to the user apps, i.e. you can define the most important apps for each cost centre and each user can attach additional apps. Menu items that are locked can be inserted but not called up! |
| Document printer | see |
| Substitute | See |
Set password
This window allows you to give a password directly to a user. This password can be entered as a temporary or a final password. If a temporary password is assigned, the user must change it to a final password immediately after login.
Field Description User: New password Enter the new password. Repeat : Enter the new password again to check that both entries are the same. Set as temporary password
This is useful, for example, if a user cannot request a password for himself by e-mail. The administrator can then do this for the user, but the user must change the password immediately after the first login.
Single sign-on (SSO)
Single sign-on (SSO) defines a functionality that is intended to simplify the handling of the large number of logins of the Windows applications used by reducing them to a single login routine.
As a Windows logon has always been carried out at the start time of ClassiX®, the ClassiX® single sign-on functionality refers to this.
To activate SSO in ClassiX®, the corresponding Windows Security Identifier ( SID ) must be entered in the Windows SID field in the user administration.
If, when ClassiX® is started, exactly 1 of the Windows SIDs stored there matches the Windows SID of the Windows user, the login is automatically carried out with the values of the user found.
The SSO functionality applies to the User + Login and Client + User + Login variants.
When "Re-Login" to ClassiX®, the SSO functionality is bypassed.
Related topics
Technical Documentation
Overview

User base module
Module name
user.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| USER_CHANGED | User object | User was changed | |
| USER_CREATED | User object | User was created | |
| USER_DELETED | User object | User was deleted |
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
| EDIT_USER | NULL or user object | Call up the input window for users | User Editing Module |
User editing module
Module name
useredt.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| EDIT_USER | NULL or user object | Call up the input window for users | |
| EMPLOYEE_SELECTED | Employee object | Employee was selected | |
| LIST_USER | Collection user objects or NULL | Calling up the list window for users | |
| LOAD_USER | Importing users | ||
| PERSON_SELECTED | Person object | Person was selected | |
| USER_CHANGED | User object | User was changed | |
| USER_CREATED | User object | User was created | |
| USER_DELETED | User object | User was deleted | |
| TAPI_SELECTED | Device as string | TAPI device was selected |
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
| CREATE_LETTER | |||
| EDIT_EMPLOYEE | NULL or employee object | Call up input window for employees | Employee editing module |
| EDIT_MAIL | NULL or email object | Call up input window for emails | Email editing module |
| EDIT_PERSON | NULL or person object | Call up input window for persons | Person edit module |
| EDIT_PROCEEDINGS | NULL or operation object | Call up the input window for operations | Process editing module |
| EDIT_USER | NULL or user object | Call up the input window for users | User Editing Module |
| EDIT_USER_HIERARCHY | |||
| LIST_USER | Calling up the list window for users | User Editing Module | |
| SELECT_EMPLOYEE | Zero or collection of employees, recipients of the reply | Call up selection window for employees | Employee selection module |
| SELECT_PERSON | zero or collection of persons, recipients of the reply | Call up selection window for persons | Person selection module |
| SHOW_PREVIEW | Print Preview | Print Preview | |
| USER_CHANGED | User object | User was changed | |
| USER_CREATED | User object | User was created | |
| SELECT_TAPI | Recipient of the reply | Open selection window for TAPI device | Telephone module |
User selection module
Module name
usersel.mod
Classes
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | Security |
|---|---|---|---|
| SELECT_USER | Collection user objects or NULL, recipient of the response | Call up selection window for users | |
| USER_CHANGED | User object | User was changed | |
| USER_CREATED | User object | User was created | |
| USER_DELETED | User object | User was deleted |
| Message | Parameters | Function | Receiver module |
|---|---|---|---|
| EDIT_USER | NULL or user object | Call up the input window for users | User Editing Module |
| USER_SELECTED | User object, receiver | User was selected |
User settings editing app
Module name
userSettingsEdit.app
Security
In addition to restricting access rights via the class and its data fields, the module can be restricted in its use via some of the received messages.
| Message | Parameters | Function | security |
|---|---|---|---|
| EDIT_USER_SETTINGS |
| Message | Parameters | Function | Receive module |
|---|---|---|---|
| ADVANCED_SEARCH | |||
| ASK_STRING | |||
| EDIT_DEFAULT_TRANSACTION | |||
| EDIT_KEY_SHORTCUT | |||
| EDIT_OBJECT | |||
| EDIT_PASSWORD | |||
| EDIT_PROCEEDINGS | |||
| EDIT_STAFF_MEMBER | |||
| EDIT_USER | |||
| EDIT_USER_SETTINGS | |||
| INITIALIZE | |||
| LOCALE_SET | |||
| LOG_FILE_STATISTICS | |||
| PASSWORD_VALIDITY_CHANGED | |||
| SELECT_ACCESS_CONTROL_USER | |||
| SELECT_APP_TRIGGER | |||
| SELECT_PERSON | |||
| SELECT_PRINTER | |||
| SELECT_STAFF_MEMBER_WITH_USER | |||
| SELECT_TAPI | |||
| USER_CHANGED | |||
| USER_DELETED |