OnBase WorkView allows organizations to build and define an application through a point-and-click interface within OnBase Studio. Before configuration, define the following:
-
The business problem to be solved.
-
The type of information to be recorded for each interaction.
-
The user interface of the application.
-
The criteria by which you wish to search, categorize or group interactions (for example, all payment issues that have not been resolved within 2 days).
The OnBase WorkView product is integrated with the OnBase document management system. WorkView data is stored in an OnBase database. In addition to storing WorkView data, documents stored in an OnBase database can be attached to WorkView issues and interactions. The WorkView security is also based on the same user group security defined in OnBase.
The most important part of configuration is defining what you need your application to do. Before you begin configuration, carefully chart the business process you wish to track and the problems that you want your WorkView application to help solve. Configuration itself is a simple process of defining the WorkView components described below.
The following components are used during creation of an application:
-
Class: A category of items to be tracked within WorkView. For example, Accounts Payable Issues.
-
Class Title: The configured class title name will appear in the screens associated with this class.
-
Attribute: Information that further defines a Class. For example, Vendor Name, Vendor Address, Status, Accounts Payable Clerk Name are all potential attributes for a class. Attributes can be used to define filter columns and criteria. For example, Accounts Payable issues can be accessed based on issue status.
-
Object: A specific collection of data belonging to a Class. Each object has its own set of attribute values. For example, a dispute over a specific invoice can be an object. Objects are created by users in the WorkView client, not during configuration, and consist of pertinent data.
-
Filter: A query that enables a user to search for objects of a particular class. Filters can list all objects or limit the objects that are returned based on attribute values or can prompt users for search parameter input. For example, you may wish to search for all objects with a status of “open.”
-
Filter Bar: Groups and names a set of one or more filters. Filter bars can be used to effectively group related filters together. Each filter bar can have multiple filters configured. Likewise, a filter can be displayed on multiple filter bars.
-
View: Used to enter and display object data within a screen. A view is identified by a single tab within a screen.
-
Screen: Collection of views for a class. Each class has only one screen. The screen collectively holds all object data displayed within views. It can consist of multiple tabs/views. It always has a History tab and a Documents tab.
-
Filter View Attributes: Displays column headings for attributes in a filter.
-
Filter User Entry Attributes: Attribute search fields that users will be able to enter values into in order to retrieve objects using filters.
-
Filter Fixed Constraints: Allows administrators to limit the filter results a user receives. An administrator can add attributes and attribute values that must match in order for objects to be displayed.
-
Shared Objects: Shared objects consist of Data Sets, actions, sequences, calendars, keytype maps, timers, and notifications that can be used by any application.
Examples of application screens follow: