OrganiZATOR User's Guide

[Home]  [Init]  [Index]


The Configuration option from the menu bar of the main screen, contains a number of utilities that allow manage certain aspects of the functioning of Zator, and enable certain options. These include:

  • Work areas.  Define work areas.

  • Commands catalog.  Define shell commands and/or applications that can be executed.

  • Messaging addresses.  Define users and the address of its corresponding mailboxes of the messaging system.

  • e-mail accounts.  Define accounts that may be used for sending and receiving email. 

  • Frequently used panel.  Edit the panel with information about data frequently used.

  • Initial settings.  Define certain parameters that set some operation details of Zator.

  • Standard Users:

  • Added Users:

  The changes made by the previous options, are done on the dBase connected at that moment in the main zone, and not all options are available to all users. Some of them require Owner; Super User or System Operator privileges. The idea is that from an installation, it is possible to establish the operating conditions of other sites if you have the appropriate access privileges, enabling centralized control of operation for the stations on a LAN from a single point, which could correspond to the system operator.

Note that as mentioned, it is possible to establish the contents of the frequently used panel of any remote area. While selecting the option to view the panel, from the option Util-1 > Frequently used panel, or the corresponding button on the toolbar, you always see the local area panel, irrespective of the area connected at that moment in the main zone.

Remember that when you create a new work area, users who are currently in the current area are copied into the new one, along with its privileges and passwords. So the password change of a user in one area, can modify its access rights in others. The reason is that each user has three attributes in each area: name, password, and access level, and when you change from the current area to another, the access is only granted if in the new area there is the same user (same name) with the same password (or the new area has a public access). Under these conditions, the level of access achieved in the new area is the one defined that user, regardless of the level which had in the original area.

We will clarify with an example: Suppose that in the local area of an installation there are a user named John Doe with owner access level and whose password is 12345678. Someone starts the application as Super User, and in Configuration > Work areas, creates a new area with the name "Test-1" and assigning a directory D:\xxxx, where for the moment, we assume that there not exist a file named zDB1.

Then, the previous Super User, select the option Util-1 > Work-area in main-zone. When you try connect the initial area with the newly defined, a message appears: "The dBase stated in the connection D:\xxxx\zdb1 does not exist. Do you want create a new dBase in that address" [1]. Answering yes, an empty dBase is created in the directory, and the connection is done. Subsequently, if the user John Doe launches the application and connects the new area Test-1, the access is without problems, because the existing users at the time of creation, are copied to the new dBase with its corresponding levels of access and associated passwords.

Now suppose that in the previous installation, you change the Doe's password is changed to 87654321, and then repeat the process: John Doe starts the application and tries to connect with Test-1, at which time a message appears: "John Doe does not have access to that area" (assuming of course that did not exist in the dBase a public access, because in such case, it would also be copied into the new area.) The reason is that now, the password with which John have accessed, does not match the with the one of the user John Doe in Test-1.



[1]  Note that if this attempt is done by a user with guest or owner access level, the message is: "The system can't find the specified file D:\xxxx.zdb1". Without giving option to create a new area in that address.