UMS Terminology

The following list defines the many of the terms used throughout the iTopia UMS views:

  • Views – Views consist of columns selected from various related tables in a specified database that make up the Search Criteria, Search Results and Details of an individual resource. There are four types of views:

    1. System views – created by Pointforce Enterprise or by the System user at your site and are commonly know as Individual Resources. These views can be accessed by users assuming the proper roles and permissions have been assigned to the view.

    2. Personal views – views that a user has created from a system view, through Personalization, and has saved with a new name. Such views are automatically stored in the users "My Views" folder. Only the user that has created the view can access this type of view unless they grant permission to others enabling access.

      • The ability to grant permissions to other users to access a Personalized view can only be done if the original Individual Resource has the Grant operation assigned to it.

    3. User Management System (UMS) – views used to manage the users in your iTopia system.

    4. Metadata Administration – views used to display table, column, domain, view and database information as well as maintain literal text.

  • Literal Text - Literal Text is the actual text for the literal. This text is displayed as view and column headings as well as menu items.

  • Individual Resource – An Individual Resource is a single view created by any user.

  • Group Resource – Group Resources are indicated by a folder icon on the iTopia menu system. Group Resources can contain both other Group Resources and/or Individual Resources.

  • Database – Databases contain information about the tables and columns within the tables. The two Databases that are shipped with iTopia are ibis and meta.

  • Table – Tables are defined for a database and contain information that defines the function of the views created from the table. For example, a view can be read-only only or it can be used for transaction entry.

  • Column – Columns are defined for a database table. Each column is defined with a Text name that appears as column headings in a view as well as other criteria that control how the column functions in the view.

  • Domain – Domains are defined for a database. A domain is used to assign a set of properties, such as the logical datatype, to a database column. Its attributes provide information about how such a column object should be displayed and what rules should be used when validating data of this type.

  • Related tables – Related Tables define an association or link between two tables. When tables are related, the columns from both tables are selectable for views.

  • Role – Roles define job functions, with associated authority and responsibilities, within the context of an organization. For example, the Role ibis_ap contains permissions for Individual and Group Resources that pertain to Accounts Payable functions. Note: The user is also considered a type of Role. When assigning Permissions to Roles you can assign the permissions to an individual user or to a predefined Role.

  • Operations – Operations (or Permissions) are assigned to both Individual and Group Resources that allow or disallow the user certain functionality within the view. For more information about Operations click here.

  • Parent/Child Resource - Parent Resources are normally Group Resources that can contain both Individual and Group Resources. These Individual and Group Resources contained within a Parent Resource are known as Child Resources.

    • Parent Resources can also be Child Resources of other Parent Resource. For example, the ibis_ap_menu (Accounts Payable menu folder), which is a Group Resource, is a Parent Resource.

    • The Child Resources associated with the ibis_ap_menu Parent Resource are:

      • ibis_apnot1 (AP Vendor Notes), an Individual Resource.
      • ibis_ap37.resouces (Cancelled Receipts Journal(AP37)), a Resource Group.

    • The ibis_ap37.resources (Cancelled Receipts Journal(AP37)) is also a Parent Resource for the following Child Resources:

      • ibis_aprgg (Cancelled Receipts Journal(AP37)), an Individual Resource.
      • ibis_aprgs (CancelledReceipts Journal-GL Summary(AP37)), an Individual Resource.
      • ibis_aprgd (Cancelled Receipts Journal-Receipts Detail(AP37)), an Individual Resource.

 
Back