AppBuilder 24.1
AppBuilder 24.1
Reference Guide
Includes:
Installation Guide
Administration Guide
User Guide
Foundation 24.1
App Builder
Documentation Notice
Information in this document is subject to change without notice. The software described in this
document is furnished only under a separate license agreement and may only be used or copied
according to the terms of such agreement. It is against the law to copy the software except as
specifically allowed in the license agreement. This document or accompanying materials may
contain certain information which is confidential information of Hyland Software, Inc. and its
affiliates, and which may be subject to the confidentiality provisions agreed to by you.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the
rights under copyright law, no part of this document may be reproduced, stored in or introduced into
a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying,
recording, or otherwise), or for any purpose, without the express written permission of Hyland
Software, Inc. or one of its affiliates.
Hyland, Hyland Experience, OnBase, Alfresco, Nuxeo, and product names are registered and/or
unregistered trademarks of Hyland Software, Inc. and its affiliates in the United States and other
countries. All other trademarks, service marks, trade names and products of other companies are the
property of their respective owners.
© 2024 Hyland Software, Inc. and its affiliates.
The information in this document may contain technology as defined by the Export Administration
Regulations (EAR) and could be subject to the Export Control Laws of the U.S. Government including
for the EAR and trade and economic sanctions maintained by the Office of Foreign Assets Control as
well as the export controls laws of your entity’s local jurisdiction. Transfer of such technology by any
means to a foreign person, whether in the United States or abroad, could require export licensing or
other approval from the U.S. Government and the export authority of your entity’s jurisdiction. You are
responsible for ensuring that you have any required approvals prior to export.
DISCLAIMER: This documentation contains available instructions for a specific Hyland product
or module. This documentation is not specific to a particular customer or industry. Hyland
customers are responsible for making their own independent assessment of the information in
this documentation. This documentation: (a) is for informational purposes only, (b) is subject to
change without notice, and (c) does not create any commitments or assurances by Hyland or its
affiliates. This documentation is provided “as is” without representation or warranty of any kind.
Hyland expressly disclaims all implied, express, or statutory warranties. Hyland’s responsibilities and
liabilities to its customers are controlled by the applicable Hyland agreement. This documentation
does not modify any agreement between Hyland and its customers.
Document Name
App Builder
Department/Group
Documentation
Revision Number
Foundation 24.1
Overview
Contents
Understanding App Builder.....................................................................................................................1
How it Works................................................................................................................................................1
Definitions.......................................................................................................................................... 1
Source........................................................................................................................................... 2
Action............................................................................................................................................ 2
Tile................................................................................................................................................. 2
Card............................................................................................................................................... 2
Screen........................................................................................................................................... 2
Master Detail with Sources.................................................................................................... 2
Quick Access...........................................................................................................................4
Licensing........................................................................................................................................................ 5
Privileges....................................................................................................................................................... 5
Installation Guide
Installation
Overview....................................................................................................................................................... 7
General Requirements....................................................................................................................... 7
Server and Core Services Hardware Requirements.........................................................................7
Web Browser Requirements..............................................................................................................7
Database Requirements........................................................................................................................... 7
Databases Supported........................................................................................................................ 7
Oracle............................................................................................................................................ 7
Microsoft SQL Server................................................................................................................... 8
Database/File Servers....................................................................................................................... 8
Pre-Installation............................................................................................................................................8
Installation.................................................................................................................................................... 8
Web Server Web.config Settings...........................................................................................................8
Studio Installation
Requirements............................................................................................................................................ 10
General Requirements..................................................................................................................... 10
Pre-Installation......................................................................................................................................... 10
Installation..................................................................................................................................................10
Installer Options...............................................................................................................................10
Standard (EXE or MSI) Installers............................................................................................... 10
ClickOnce Installers....................................................................................................................11
User Account Control (UAC)...................................................................................................... 11
Silent Installation Using setup.exe............................................................................................ 12
Installing OnBase Studio................................................................................................................. 12
Connection Strings in Web.config.................................................................................................. 18
Name...........................................................................................................................................19
ConnectionString........................................................................................................................19
SQL Server Connection String Tokens.................................................................................19
Administration Guide
Configuration
User Rights Within the Configuration Module...............................................................................30
Considerations for Configuring Applications................................................................................. 30
Launching OnBase Studio......................................................................................................................30
Connecting to a Repository.................................................................................................................. 30
Refreshing Repositories.................................................................................................................. 32
Expanding and Collapsing Items in the Repository Pane..............................................................32
Viewing Items in the Designer Pane............................................................................................... 33
Using Repositories in OnBase Studio................................................................................................ 34
Searching the Repositories Pane.........................................................................................................34
Creating Applications............................................................................................................................. 34
Modifying Applications....................................................................................................................38
Changing the Assigned User Groups..............................................................................................39
Deleting Applications.......................................................................................................................39
Creating Screens.......................................................................................................................................39
Creating Master Detail with Sources.............................................................................................. 40
Adding Sources.......................................................................................................................... 42
Custom Query....................................................................................................................... 43
Document Retrieval...............................................................................................................44
Reporting Dashboard............................................................................................................44
Workflow Queue....................................................................................................................45
WorkView Filter..................................................................................................................... 45
Adding Source Groups............................................................................................................... 46
Modifying Sources..................................................................................................................... 47
Modifying Source Groups.......................................................................................................... 47
Deleting Source Groups and Sources....................................................................................... 48
Creating Quick Access Screens...................................................................................................... 48
Creating Cards............................................................................................................................ 49
Creating Tiles..............................................................................................................................50
Modifying Screens........................................................................................................................... 53
Changing the Default Screen.......................................................................................................... 53
Deleting Screens.............................................................................................................................. 54
Creating Actions.............................................................................................................................. 54
Create Unity Form.......................................................................................................................54
Create WorkView Object............................................................................................................ 56
Navigate to Screen/Data Source............................................................................................... 57
Open URL.................................................................................................................................... 59
Upload a New Document........................................................................................................... 60
Modifying Cards, Actions and Tiles................................................................................................ 62
Deleting Cards, Actions and Tiles................................................................................................... 62
Changing the Displaying Sequence.................................................................................................... 62
App Builder Shortcut Keys.................................................................................................................... 63
Studio Administration
Connecting to Repositories.................................................................................................................. 64
Configuring Repository Properties................................................................................................. 66
Configuring the Environment Value Management URL........................................................... 66
Configuring the Administration Portal Web Application URL.................................................. 66
Refreshing Repositories.................................................................................................................. 67
Expanding and Collapsing Items in the Repository Pane..............................................................67
Viewing Items in the Designer Pane............................................................................................... 68
Searching in Studio.................................................................................................................................. 69
Search Options.................................................................................................................................70
Search Results................................................................................................................................. 72
Exporting Search Results...........................................................................................................73
Output Tab..................................................................................................................................................73
Shortcuts..................................................................................................................................................... 73
The Reset Server Cache Button...........................................................................................................74
Studio Options...........................................................................................................................................74
General............................................................................................................................................. 74
Doctor............................................................................................................................................... 75
Managing Locks.........................................................................................................................................78
Output Window........................................................................................................................................79
Controlling the Interface Display........................................................................................................79
Best Practices
App Builder Best Practices................................................................................................................. 121
Sources organizing........................................................................................................................ 121
User interface.................................................................................................................................121
Administration............................................................................................................................... 122
User Guide
Usage
Usage..........................................................................................................................................................124
Accessing the Application...................................................................................................................124
Application Overview.......................................................................................................................... 125
Using a Master Detail with Sources Screen................................................................................. 125
Adjusting a Master Detail with Sources Screen..................................................................... 127
Usign a Quick Access Screen....................................................................................................... 127
Settings......................................................................................................................................................129
Changing Theme............................................................................................................................129
Accessing Screens..................................................................................................................................130
Going Back to the Default Screen.................................................................................................... 130
Retrieving Documents......................................................................................................................... 130
Using Folders...........................................................................................................................................133
Working with Folder Notes............................................................................................................135
Folder Notes Requirements.....................................................................................................135
Viewing Folder Notes and Bookmarks....................................................................................135
Adding a Folder Note or Bookmark.........................................................................................136
Viewing a Bookmarked Document..........................................................................................136
How it Works
App Builder allows organizations to build and define an application through a point-and-click
interface within OnBase Studio.
App Builder is integrated with the OnBase document management system, including its security that
is based on the same User Group security defined in OnBase.
Applications created by an administrator are used as an interface between the end user and
functions provided by the OnBase system. They can be viewed as a collection of customized
shortcuts to facilitate usage of the OnBase system in an intuitive manner.
Definitions
An application comprises one or multiple sources, cards, tiles, and actions, all combined within one
or more screens.
To learn more, see:
• Source on page 2
• Card on page 2
• Tile on page 2
• Action on page 2
• Screen on page 2
Source
A source is a basic element of your application. It is a link to a system resource, such as a collection
of documents, Workflow queue, or reporting dashboard.
You can configure sources for a Master Detail with Sources on page 2 screen and then add them
to a Quick Access on page 4 screen to provide easier access.
You can use the sources to look for documents, check how many items are in a Workflow queue, or
execute a Custom Query.
Action
An action is a way for the user to interact with the system components or to access a direct link to a
resource outside of the system, such as an external URL or creating a form.
You can configure actions for any type of screen.
Tile
A tile is a direct link to a source configured within the application.
You can configure tiles to be displayed at a Card on page 2 within the Quick Access on page
4 screen.
Card
A card is a collection of sources and actions grouped by the administrator for easier access. Each
particular element is represented by a tile that is added to the card.
You can configure multiple cards at a Quick Access on page 4 screen to group functions
according to user roles or other criteria.
Screen
A screen represents a collection of sources and actions that can be used by the end user.
There are two types of screens you can include in your application:
• Master Detail with Sources on page 2
• Quick Access on page 4
The image below presents an example of a Master Detail with Sources screen:
Element Description
C: Tabs with other screens A list of tabs with names of other screens.
You can click a screen name to change the screen. The currently
selected screen name is underlined.
D: List of sources A list of all sources configured for the Master Detail with
Sources screen, grouped as configured by the administrator.
You can click a source name to access it. Its name becomes
highlighted when clicked.
For more information, see Source on page 2.
Element Description
Quick Access
A Quick Access screen is a collection of cards grouped by the administrator for easier access to
system resources and external actions. This type of screen can be used as a home page or landing
page, dashboard, or a quick access page.
The image below presents an example of a Quick Access screen:
Element Description
C: Tabs with other screens A list of tabs with names of other screens.
You can click a screen name to change the screen. The
currently selected screen name is underlined.
D: Quick Access Screen logo, title, Elements displayed as a part of your company's branding.
and subtitle The logo, title, and subtitle can be configured to suit your
company's visual style.
E: Card and card title A list of cards configured for the screen.
You can click on the elements collected within the card to use
them.
The card title is bold and the optional instruction is gray.
For more information, see Card on page 2.
Licensing
App Builder itself does not require additional licensing. However, appropriate licenses are required to
use its particular functions, such as Workflow queues.
Privileges
App Builder itself does not require additional privileges. However, appropriate privileges are required
to use its particular functions, such as Workflow queues.
Installation Guide
Foundation 24.1
Installation
Overview
The following sections outline requirement information specific to App Builder in OnBase Foundation
24.1.
General Requirements
For general requirement information that applies to App Builder and other modules, see the sections
on the following topics in the Installation Requirements manual:
Database Requirements
Databases Supported
The following sections list the databases supported by this module in OnBase Foundation 24.1.
Oracle
The following versions of Oracle® are supported:
• Oracle 19c
When using Oracle databases, also note the following:
• It is strongly recommended that you have a certified Oracle Database Administrator on staff.
• If you are using ODBC drivers with your Oracle database, it is recommended that you select Bind
Timestamp to Date.
Database/File Servers
Server requirements are site-specific. Database/file servers should be dedicated purpose servers;
that is, these servers should not be used as a domain controller, email server, print server, or proxy
server. Network and disk I/O hardware should be optimized for performance and redundancy.
Multiple network interface cards on servers are often required to minimize network bottlenecks.
Pre-Installation
The OnBase 64-bit Application Server must be running and connected to the database using App
Builder. OnBase Web Server must also be installed. In addition, the Impersonated Identity account
configured in the Web Server's web.config file within the <identity> element must be granted the
Full Control rights for the directory storing the style sheets. See the Web Server documentation for
further information.
Installation
App Builder is configured through OnBase Studio. For more information, see Installation on page
10 for Studio.
The created application is accessed through the Web Client. Installing the Web Client completes the
installation process for the App Builder. For more information, see the Web Server documentation.
Note: Inreasing the value of MaxResults property may cause performance decrease.
Requirements
The following sections outline requirement information specific to App Builder in OnBase Foundation
24.1.
General Requirements
For general requirement information that applies to App Builder and other modules, see the sections
on the following topics in the Installation Requirements manual:
• Database Requirements
• Operating System Requirements
• OnBase Client Hardware Requirements
• Server and Core Services Hardware Requirements
Pre-Installation
If you are using Workflow notifications, consult the Workflow module reference guide for information
about installing and configuring the system to send notifications.
Installation
Installer Options
Before using a product installer, consider the following information about installer options.
Note: The Microsoft .NET Framework prerequisite must always be installed separately before
running either the EXE or MSI installer.
When performing a silent installation, and both an executable file and MSI are available, use the MSI.
Since the MSI package does not validate prerequisites, you must ensure that Windows Installer 3.0
or greater is installed on each workstation and that all other prerequisites are met before running the
MSI. If any prerequisites are not met, a silent installation from the MSI will fail without alerting the
user.
For more information about configuring a silent installation, see https://docs.microsoft.com/en-us/
windows/win32/msi/command-line-options.
ClickOnce Installers
Some OnBase modules are installed for deployment using ClickOnce. ClickOnce is a Microsoft
technology that installs a deployment package to a central server. This package can then be
accessed by users to install the application on their local workstations. The application is installed
entirely under the user's profile, ensuring that it cannot interfere with other applications installed on
the workstation.
ClickOnce deployments also have the following advantages:
• Previously installed versions of the module can be easily and automatically updated to the
latest version with little or no user interaction, as long as the deployment server and deployment
instance name are not changed.
• The module is installed on a per-user basis and does not require administrator privileges for local
installation.
• There can be multiple instances of the module deployed, allowing for different versions of the
module to be installed on a per-user basis, to match the version requirements of the workstation
it is being installed to.
For more information on Microsoft's ClickOnce technology see https://docs.microsoft.com/en-us/
visualstudio/deployment/clickonce-security-and-deployment.
Note: ClickOnce-deployed applications are not supported by Microsoft within a Remote Desktop
environment.
OnBase modules that are deployed using ClickOnce should either take advantage of the ClickOnce
deployment method as an alternative to a Remote Desktop deployment, or the module should be
installed using a standard installer and deployed using the Remote Desktop methodology.
Note: Not all OnBase modules that support ClickOnce have a standard installer available. Contact
your first line of support if you are unsure how to install and deploy a specific module.
Note: You should check the return value of the setup.exe process. A return value of 0(zero) indicates
success. Any other value returned may indicate that an error was encountered and the installation
failed.
Note: If the installer is being copied from the source location to be run from a different location, the
entire \ OnBase Studio\ folder and its contents must be copied to the new location.
3. Enter the top-level installation directory in the field provided, or click Change to browse to it.
Note: This location does not affect components not installed under the top-level directory. If the
installer provides for the installation of multiple components, the specific installation locations of
each component can be changed later in the installation process.
If Change is clicked the Change destination folder dialog box is displayed.
Enter a Folder name in the field provided or select it from the Look in drop-down list, then click
OK.
If the Destination Folder is not changed, the default location is used.
5. Select Create Desktop shortcut(s) when applicable to create shortcuts to the installed
components in the Windows Start | All Programs | Hyland menu, on the Windows desktop, or in
both locations, when applicable.
6. Click Install to continue with the installation, or click Cancel to cancel the installation.
7. When the installation is complete, click Finish.
Tip: In order to ensure that the required system settings take effect, it is a best practice to restart
the installing machine once the installer has finished.
The connection strings dialog box allows you to configure connection strings.
8. To encrypt all connection strings configured in the application's .config file, ensure the Options
| Encrypt Connection Strings menu option is selected. This option is automatically selected by
default every time you open the connection strings dialog box, and the connection strings are
encrypted when the .config file is saved.
CAUTION: It is strongly recommended to encrypt the connection strings. If they are not
encrypted, all data source connection information is visible in the .config file and could expose
sensitive data, including any entered database user names and passwords.
9. Click Add to start creating a new connection string. The fields on the right become available for
interaction.
10. If you are configuring Reporting Dashboards with a secondary connection string with a read-
only database user account, select Options | Populate Read-Only User. This optional feature
populates the User ID and Password fields with the credentials for the read-only user. See the
Reporting Dashboards documentation for more information.
If you are creating a connection string for any other purpose, skip this step.
11. In the fields on the right, enter the following information about the data source:
Option Description
Data Source Name A unique name that you create to identify the connection string.
Note: This identifying name may be different from the name of the
actual database.
Data Provider The data provider type used for the database. Select one of the
following:
• System.Data.SqlClient: Select this for a SQL Server database.
• Oracle.ManagedDataAccess.Client: Select this for an Oracle
database.
Note: Only SQL Server and Oracle data providers can be used to
connect to the OnBase database.
12. Depending on your selection for Data Provider in the previous step, enter the following database
connection information:
• If System.Data.SqlClient is selected (for a SQL Server database):
Oracle.ManagedDataAccess.Client Description
Option
TNS Connection String Select this option to enter a full TNS connection string
to connect to the Oracle database. Deselect the option
to use the connection name instead.
Note: Selecting this option enables the Host,
Database, Protocol, and Port fields for interaction.
Oracle.ManagedDataAccess.Client Description
Option
Option Description
Integrated Security Select this option to use Windows Authentication to connect to the
database.
CAUTION: It is strongly recommended to use integrated security
instead of a database account for authentication. To use integrated
security, the Windows user connecting to the database must be the
same user that is running the connecting server or service (such as
the Application Server). This user must also be configured with the
configgp role in the database.
User ID The user name of the database user account accessing the database.
Note: This user name is for a database user account, not a user
account for OnBase.
Password The password of the database user account accessing the database.
Note: This password is for a database user account, not a user account
for OnBase.
Option Description
Additional Options Any additional options for the connection string. For more information
on available connection string options and syntax, see the
documentation for your database provider (SQL Server or Oracle).
15. Click Test Connection to test whether the entered information forms a valid connection string.
16. Click Create to save the information in the fields and create the connection string. The name
of the data source is added to the Data Sources list on the left, and the connection string is
displayed in the Connection String section.
Note: ADO.NET and connection strings are Microsoft .NET Framework concepts, but each database
provider (such as SQL Server or Oracle) has its own implementation of ADO.NET. For more
information on building a valid connection string or using additional options, see your database
provider's documentation on connection strings.
It is important to note the following considerations for connection strings:
• It is strongly recommended to use integrated security instead of a database account for
authentication. To use integrated security, the Windows user connecting to the database must be
the same user that is running the connecting server or service (such as the Application Server).
This user must also be configured with the configgp role in the database.
• It is strongly recommended to encrypt the connection strings. If they are not encrypted, all data
source connection information is visible in the .config file, including the database user names
and passwords in the connection strings.
Encryption can be performed using the aspnet_regiis command line utility for IIS or using Web
Application Management Console. See the documentation from Microsoft for more information
on using the ASP.NET IIS Registration Tool. See the Web Application Management Console
module reference guide for more information on encrypting connection strings using the OnBase
Web Application Management Console.
See the following subsections for information on each element of a connection string:
• Name on page 19
• ConnectionString on page 19
• ProviderName on page 20
For examples of connection strings for all supported database platforms, see Connection String
Examples on page 20.
Name
The name element is a unique name that you create to identify the data source connection string.
Note: This identifying name may be different from the name of the actual database, which is
specified in the Data Source and database attributes.
For example: name="DataSourceName"
ConnectionString
The connectionString element contains connection information for the database. The tokens
needed for the connection information depend on the database platform used.
Token Description
Data Source The server\instance name of the SQL Server instance hosting the
database.
User Id The user name of the user account accessing the database. This is a
database user account, not a user account in OnBase.
Note: If using integrated security, the User Id token is not used.
Password The password of the user account accessing the database. This is a
database user account, not a user account in OnBase.
Note: If using integrated security, the Password token is not used.
Integrated Security A true or false value specifying whether to use integrated security to
access the database.
Token Description
Token Description
User Id The user name of the user account accessing the database. This is a
database user account, not a user account in OnBase.
Note: If using OS Authentication, enter a forward slash in place of the
user name. For example: User Id=/
Password The password of the user account accessing the database. This is a
database user account, not a user account in OnBase.
Note: If using OS Authentication, the Password token is not used.
ProviderName
The providerName element specifies the data provider type used for the database. Only SQL Server
and Oracle data providers can be used to connect to the OnBase database.
Oracle providerName="Oracle.ManagedDataAccess.Client"
Note: The following examples are provided for illustration purposes only. Each database provider
has its own implementation of ADO.NET and connection strings, and your particular situation may
require including different or additional options than the ones illustrated in these examples. For more
information on building a valid connection string or using additional options, see your database
provider's documentation on connection strings.
Oracle Examples
This connection string would create a data source is called ConnectOracle, used to connect to the
Oracle database TestDB:
<connectionStrings>
<add name="ConnectOracle" connectionString="Data Source=TestDB;
User Id=username;Password=password"
providerName="Oracle.ManagedDataAccess.Client"/>
</connectionStrings>
Similarly, this example would connect to the same database, but it would use OS Authentication
instead of database user authentication:
<connectionStrings>
<add name="ConnectOracle" connectionString="Data Source=TestDB;
User Id=/" providerName="Oracle.ManagedDataAccess.Client"/>
</connectionStrings>
The following example would connect to the same database, but it uses the connect descriptor for
the Oracle database:
<connectionStrings>
<add name="ConnectOracle"
connectionString="Data Source=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)
(HOST=hostname)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=TestDB)));
User Id=username;Password=password"
providerName="Oracle.ManagedDataAccess.Client"/>
</connectionStrings>
Option Description
Repair Repair errors in the most recent installation of the component, such as missing
and corrupt files, shortcuts, and registry entries.
Note: This option is not available from all installers. Repair does not include
errors made in the configuration options set by the user during installation. For
specific troubleshooting information regarding an installed component, see the
module reference guide for that component.
Feature Names
To install OnBase Studio, the value of the ADDLOCAL property is Workflow_Studio.
The ADDLOCAL property is added to the installation command line, as shown here:
msiexec /i "Hyland Workflow Studio.msi" ADDLOCAL=Workflow_Studio
Properties
When controlling the installation of components from the command line you must also configure the
settings for each component you are installing by using the properties listed in the following table. If
a property is not included, the default value is configured for that property.
Property Description
Note: Only one instance of OnBase Studio can be installed, either the 32-bit version or the 64-bit
version.
Post-Installation
Some functionality must be configured directly in the configuration file, obstudio.exe.config, which
is found in the Destination Folder selected during installation.
Note: The following steps assume that App Builder has already been set up for IdP authentication.
For steps on configuring App Builder for IdP, see the Integrating with Hyland IAM Services
documentation.
Upgrade Considerations
The following upgrade considerations have been compiled by OnBase subject matter experts.
These upgrade considerations are general and applicable to most OnBase solutions and network
environments and should be considered each time an upgrade is performed.
Carefully consider the impact of making any changes, including those listed below, prior to
implementing them in a production environment.
For additional general information about upgrading OnBase, refer to the Upgrade Guidelines
documentation, and visit the Hyland Community.
Import/Export Considerations
The following should be considered with regard to importing and exporting in Studio:
• When using the Import/Export tool, for best results, ensure that the version and build from which
you are exporting matches the version and build to which you are importing. For example, if
version 23.1 is used to export, version 23.1 is used to import.
• If restoring a backed-up database, or using an export file to rapidly set up a new environment, it
is important to ensure that all the required Disk Groups and the System Documents are already
configured. When using Studio to import a configuration file, a system verification report is
generated after importing. If the System Documents are not configured properly, an error will
be displayed and the process will have to be executed again after the Disk Groups and System
Documents have been configured.
Post-Upgrade Considerations
The following should be considered with regard to post-upgrade maintenance in Studio:
• It is highly likely that after upgrading you will find new System Document Types available within
OnBase. Navigate to Document | Document Types in the Configuration module in order to
assign these new Document Types to the appropriate System Disk Group and System Document
Type Group.
Troubleshooting
There are two main places to access log information. These include:
• The Output window in OnBase Studio.
• The Error and Configuration tabs in the Diagnostics Console.
These two interfaces will record errors and other activity related to OnBase Studio. There are some
configuration steps necessary for OnBase Studio to log information to the Diagnostics Console and
the Output window.
For more information about the Output window, see Output Window section. For more information
about the Diagnostics Console, see the Diagnostics Console MRG.
Note: Any profiles not listed in the include-profiles key will not be logged.
Use the exclude-profiles key in a route to disable logging for specific profiles. List the excluded
profile names in a comma-separated, case-sensitive list in the value attribute of the key. For
example:
<add key="exclude-profiles" value="example1,example2" />
Note: Any profiles not listed in the exclude-profiles key will be logged. Also, the include-profile key
overrides the exclude-profiles key, so if a profile is listed in both keys, it will be logged.
Trusted Certificates
In order to help increase the security of the system, the AllowAllSSLCertificates setting is set
to False by default. This ensures that if the certificate used for an HTTPS connection cannot be
verified, then the connection is refused and users cannot log on to OnBase Studio. To help maintain a
higher level of security, it is recommended that the AllowAllSSLCertificates setting is set to False.
Language Support
OnBase Studio will respect the regional settings of a workstation. In addition, you can set the
<DisplayLanguage> setting in wfstudio.exe.config to set the interface to a specific language.
Note: Only the following languages have full support for generating documentation from OnBase
Studio in that language: Spanish, French, Arabic, Japanese, and Portuguese.
The following settings are available for OnBase Studio to language settings at the application level.
Culture The interface displays dates, time, currency, and numeric values using
the default Windows locale settings configured in Regional and Language
Options.
To override the default Windows locale in the interface, set the Culture to
an ISO code such as de-CH for German (Switzerland).
Note: This setting is commented out by default. This means that this
setting cannot be used until you remove the <!-- preceding <Culture> and
the --> following </Culture>.
Note: The < DisplayLanguage> and < Culture> settings are not required
to match, except when < DisplayLanguage> is configured as Arabic
(Saudi Arabia). When < DisplayLanguage> is configured as ar-SA, <
Culture> must also be configured as ar-SA. However, when < Culture> is
configured as ar-SA, the < DisplayLanguage> is not required to be ar-SA.
Note: The *.config file should only be edited in a plain-text editor, such as Notepad, or a utility
specifically designed to edit XML files. It should not be edited in a binary editor, such as
Microsoft Word. Using a binary editor can introduce invalid characters to the file and make it
unreadable by the software.
3. Locate the ConfigurationImport_DatabaseTimeout key within the <appSettings> element.
4. For the value of ConfigurationImport_DatabaseTimeout, enter the time you would like to allow
for the import process in seconds. The default value is 300 seconds.
For example: <add key="ConfigurationImport_DatabaseTimeout" value="360" />
5. Save and close the web.config file.
6. Recycle the application pool for changes to the web.config file to take effect.
7. Locate the obstudio.exe.config file of OnBase Studio.
Note: The *.config file should only be edited in a plain-text editor, such as Notepad, or a utility
specifically designed to edit XML files. It should not be edited in a binary editor, such as
Microsoft Word. Using a binary editor can introduce invalid characters to the file and make it
unreadable by the software.
9. Locate the ConfigurationImport_DatabaseTimeout key within the <appSettings> element.
10. For the value of ConfigurationImport_DatabaseTimeout, enter the time you would like to allow
for the import process in seconds. The default value is 300 seconds.
For example: <add key="ConfigurationImport_DatabaseTimeout" value="360" />
11. Save and close the obstudio.exe.config file.
12. If OnBase Studio is running, restart OnBase Studio.
Contacting Support
When contacting your solution provider, please provide the following information:
• The OnBase module where the issue was encountered.
• The OnBase version and build.
• The type and version of the connected database, such as Microsoft SQL Server 2022 or Oracle
19c, and any Service Pack that has been installed.
• The operating system that the workstation is running on, such as Windows 11 or Windows Server
2022, and any Service Pack that has been installed. Check the supported operating systems for
this module to ensure that the operating system is supported.
• The name and version of any application related to the issue.
• The version of Internet Explorer and any Service Pack that has been installed, if applicable.
• A complete description of the problem, including actions leading up to the issue.
• Screenshots of any error messages.
Supplied with the above information, your solution provider can better assist you in correcting the
issue.
Administration Guide
Foundation 24.1
Configuration
Note: The following sections describe how to work with repositories in OnBase Studio. For
additional, general information about OnBase Studio, see the Studio module reference guide.
Connecting to a Repository
To configure custom capture processes with the Capture Process Designer (CPD), you must connect
to a database through a repository.
To open a database connection repository:
1. Database connection repositories are opened via the Connect dialog box. Open the Connect
dialog box in one of two ways:
• Launch OnBase Studio. The Connect dialog box is displayed on startup.
• If OnBase Studio is already connected to a repository, click Connect in the Home ribbon
menu to open another repository.
The Connect dialog box is displayed.
Note: In order to connect to an Application Server, the Application Server and Studio must both
be of the same major and minor version, and the same service pack version. For example, if the
Application Server is version 16.0.1, then Studio also needs to be version 16.0.1.
Note: Studio does not support remoting as a communication method for the Application Server.
SOAP must be used. Ensure that the full Application Server URL to the service page uses
Service.asmx.
3. Enter a Data Source or select one from the drop-down list. When Local is selected as the
connection type, the Data Source list is populated with all available data sources. When
connecting via an Application Server, the data source entered is saved as an option in the Data
Source drop-down list for future selection once you have connected successfully.
4. Select an Authentication Type from the drop-down list. The following options are available:
• Active Director Federation Services (AD FS) - Select this option to use Active Director
Federation Services authentication. To use this option, you must have the Application Server
configured for AD FS, and you must modify the Studio configuration file. For information on
how to modify the Studio configuration file to enable AD FS, see the Legacy Authentication
Methods module reference guide.
Note: AD FS is not available for use with the Local connection type.
• NT Authentication - Select this option to use Active Directory authentication. To use this
option, your system must be configured for Active Directory - Enhanced authentication. For
more information, see the Legacy Authentication Methods module reference guide.
• NT Authentication (Interactive) - Select this option to enter credentials for Active Directory
authentication. The User Name must include a domain. To use this option, your system must
be configured for Active Directory - Enhanced authentication. For more information, see the
Legacy Authentication Methods module reference guide.
• Standard Authentication - Select this option to use standard OnBase credentials.
Additional authentication methods may be available depending on the configuration of OnBase
Studio and your solution. Contact your system administrator for more information about
additional authentication methods.
5. If you are prompted, enter a User Name and Password.
Select Remember password if you want OnBase to remember your password.
6. Click Connect.
Refreshing Repositories
You can refresh a repository in order to work with the most up-to-date configuration for the database
that the repository is associated with. To refresh a repository, right-click on an item in the repository
within the Repositories pane and select Refresh or select an item and press F5 on the keyboard.
Refreshing will update the open repository, which has an item selected in it, with all changes that
have been saved to the database since the repository was opened. A refresh is not limited to
changes made by the current user, but will update the repository with all changes that have been
saved to the database. Items with changes that have not been saved to the database are not
refreshed.
If you mouse over the tab for an item open in the pane, you can see the current repository and user
information for that item.
Note: If there is a system lock, you will be unable to open the repository.
In order for your changes and additions to a repository to be reflected, you must save the repository.
Any changes you make will not be saved until the repository is saved. You can save a repository by
clicking Save button on the Home ribbon. Alternatively, you can click the Save drop-down menu and
select a specific repository to save or Save All to save all of the repositories.
Items that have been changed and not saved are denoted with an asterisk (*).
Upon clicking Save or Save All, a Saving Repository status window is displayed. You can click
Cancel to abort saving.
Creating Applications
An Application is a user-facing container with OnBase functionalities. It can be easily customized
and adjusted to suit your needs.
Create the application by following the steps:
1. In the App Builder tab, within the New group, select New Application.
Note: The title can include only alphanumeric and international characters, and spaces.
The System Name and Route fields are automatically populated with the value entered in the
Title field.
3. Modify the System Name field as needed. The system name is the name shown in the App
Builder structure in the Repositories pane. It must be unique.
4. Modify the Route field as needed.
Note: The Route field represents the part of the URL that will be used to access the newly
created application. In the example presented here, the address is: <web_server>/<virtual-
dir>/Apps/<app-route> so an example address would be: https://myserver/AppNet/Apps/
myapplication
where the <web_server> is your server address, <virtual-dir> is the name of your virtual directory,
and the <app-route> is the route you gave your application.
The route accepts only lowercase alphanumeric characters, "-" and "_".
5. In the Theming section, adjust the Theme Color and Font Color, using the … buttons on the
right. The theme color is set as the primary color for pages, such as headers. The font color is
used as the foreground color.
Theming allows to adjust the application to the specific color requirements of a brand and to
distinguish multiple applications from each other.
CAUTION: When changing colors, make sure that the items are displayed appropriately and are
easy to read for the end user.
Note: The theme will be displayed when appearance is set to the Light Mode. When set to the
Dark Mode, the application uses the default Web Client theme.
6. Click Next.
The user group selection screen is displayed.
Tip: The scope of a persona-based application should be limited to the functionality that only the
specific group need.
If you need to separate functionalities (screens, actions, source groups) by user groups, verify
whether you should break these functionalities out into multiple apps for multiple user groups.
8. Click Add. The selected group is displayed under the Name column.
9. When all required groups are added, click Next.A Summary screen is displayed.
The Launch Create Screen Wizard box is checked by default. If you do not want to proceed
directly to the Create Screen Wizard, uncheck the box. For details on screen configuration, see
Creating Screens on page 39.
10. If you are satisfied with your application, click Finish.
The newly created Application is displayed under the App Builder tab in the Repositories pane, and in
the Properties tab.
Modifying Applications
To modify an existing application:
1. In the Repositories pane, under the App Builder tab, select the application that you want to
modify. Its properties are displayed in the Properties pane, similarly to the example below:
Note: The theme will be displayed when appearance is set to the Light Mode. When set to the
Dark Mode, the application will use the default Web Client theme.
CAUTION: The route is used to accessed the application and its functions. Renaming it will break
any links that reference it. Do it only when necessary.
3. When you are satisfied with the changes, click Finish.
Deleting Applications
To delete an application:
1. In the Repositories pane, right-click on the application that you want to delete and select Delete.
CAUTION: This operation will remove the application permanently. It is not possible to recover
the application, unless it was previously exported.
CAUTION: It will be no longer possible to use any links or bookmarks to access the application,
unless a new one with the same route is created.
2. A message stating Are you sure you want to delete '[Application Name]'? Deleting [Application
Name] will delete all its configuration items. This operation cannot be undone. is displayed. Click
Yes to continue the deletion.
3. The application is deleted and removed from the App Builder tab.
The Application is deleted with all of its related configuration items. This happens once the
repository is saved.
Creating Screens
Applications can be divided into many screens. A single screen represents a collection of sources
and actions that can be used by the end user. Options and features configured here will be shown at
the target page.
Note: The first created screen will be displayed as the first one in the application tree in the
Repositories pane and will be used as the default screen when loading the application. The
default screen can be later changed by dragging-and-dropping other screen to the primary
position in the application tree.
The Add Screen wizard is displayed.
Note: The system name and route must be unique within an application.
3. Modify the System Name. The system name is the name shown in the App Builder structure in
the Repositories pane.
4. Modify the Route field.
Note: The Route field represents part of the web address that will be used to access the newly
created screen. It accepts only lowercase alphanumeric characters, "-" and "_".
5. Click Next.
The Create Source Group screen is displayed.
Enter the Title and System Name of the initial source group. This is the default group for the
sources added to the screen.
6. Click Next.
Note: Sources that are added to your screen must already exist in your system. If you need a new
source, configure it in OnBase Configuration or OnBase Studio first.
The Create Source screen is displayed for the selected source.
8. Enter the required details of your source.
To see more details, check the following:
• Custom Query on page 43
• Document Retrieval on page 44
• Reporting Dashboard on page 44
• Workflow Queue on page 45
• WorkView Filter on page 45
9. Configure additional sources.
10. Click Next.
A Summary screen is displayed.
11. If you are satisfied with your configuration, click Finish.
The newly created screen is displayed in the App Builder tab in the Repositories pane under the
application it was created for, and in the Properties tab.
Adding Sources
To add new sources to a source group:
1. Right-click the source group name in the Repositories pane and click New | Source.
Custom Query
You can create a source to a custom query configured in the OnBase system to allow the user to use
the query. The available types of custom query are: Document Type, Document Type Group, Folder
Type, and Keyword.
To configure a custom query source:
1. Select a custom query configured in your system from theCustom Query drop-down list.
Note: Adding a Custom Query with more than 15 columns as an application source may cause
performance decrease. It is recommended to limit the number of columns when configuring the
Custom Query. For more information, see the System Administration documentation.
The Label and Route fields are completed automatically, basing on your selection.
2. Modify the label and route as needed.
3. Enter the system name in the System Name field.
4. Optional: enter the additional, user-friendly instructions in the User Instruction field.
5. Click Next.
Document Retrieval
You can create a source to a Document Retrieval configured in the OnBase system to allow the user
to retrieve a document type.
To configure Document Retrieval source:
1. Select a document retrieval configured in your system from the Document Retrieval Query drop-
down list.
The Label and Route fields are completed automatically, basing on your selection.
2. Modify the label and route as needed.
3. Enter the system name in the System Name field.
4. Optional: enter the additional, user-friendly instructions in the User Instruction field.
5. Click Next.
The Source Options are displayed.
6. Set the source Workflow options. Check the Show Ad-hoc Tasks or Show System Tasks to
show the user Workflow tasks and allow them to be executed.
System tasks are prioritized and shown to the user in the toolbar, while ad-hoc tasks are moved
into the action menu.
7. Click Next. The Summary screen is displayed.
8. If you are satisfied with the configuration, click Finish.
The newly added source is listed in the Repositories pane.
Reporting Dashboard
You can create a source to a Reporting Dashboard configured in the OnBase system. The user can
view the dashboard and perform basic actions on it.
To configure a Reporting Dashboard source:
1. Select a reporting dashboard configured in your system from the Reporting Dashboard drop-
down list.
The Label and Route fields are completed automatically, basing on your selection.
2. Modify the label and route as needed.
3. Enter the system name in the System Name field.
4. Optional: enter the additional, user-friendly instructions in the User Instruction field.
5. Click Next. The Summary screen is displayed.
Note: The user has to have the proper privileges and licensing to use the Reporting Dashboard. For
more details, see the Reporting Dashboards documentation.
Note: App Builder does not respect the Web Server web.config setting for
DashboardCacheTimeoutSeconds.
Workflow Queue
You can create a source to a Workflow queue configured in the OnBase system to allow the user to
see the queue and perform tasks on the queued documents.
To configure a Workflow queue source:
1. Select a Workflow queue configured in your system from theLife Cycle drop-down list.
The Workflow Queue drop-down list becomes available.
2. Select a Workflow queue from the Workflow Queue drop-down list.
The Label and Route fields are completed automatically, basing on your selection.
3. Modify the label and route as needed.
4. Enter the system name in the System Name field.
5. Optional: enter the additional, user-friendly instructions in the User Instruction field.
6. Click Next.
The Source Options are displayed.
7. Set the source Workflow options. Check Show System Tasks to show the user Workflow tasks
and allow them to be executed. The Show Ad-Hoc Tasks option cannot be unchecked.
Ad-hoc tasks are prioritized and shown to the user in the toolbar, while system tasks are moved
into the action menu.
8. Click Next. The Summary screen is displayed.
9. If you are satisfied with the configuration, click Finish.
The newly added source is listed in the Repositories pane.
Note: To use the Workflow queue, the user has to have the proper privileges and licensing. For more
details, see the Workflow documentation.
WorkView Filter
You can create a source to a WorkView Filter configured in the OnBase system. The user can see
WorkView objects based on the configured filter.
To configure a WorkView filter source:
1. Select a WorkView Filter configured in your system from the WorkView Filter drop-down list.
The Label and Route fields are completed automatically, basing on your selection.
2. Modify the label and route as needed.
3. Enter the system name in the System Name field.
4. Optional: enter the additional, user-friendly instructions in the User Instruction field.
5. Click Next.
The Source Options are displayed.
6. Set the source Workflow options. Check the Show Ad-hoc Tasks or Show System Tasks to
show the user Workflow tasks and allow them to be executed.
System tasks are prioritized and shown to the user in the toolbar, while ad-hoc tasks are moved
into the action menu.
7. Click Next. The Summary screen is displayed.
8. If you are satisfied with the configuration, click Finish.
The newly added source is listed in the Repositories pane.
Note: To use the WorkView Filter, the user has to have the proper privileges and licensing. For more
details, see the WorkView documentation.
3. Enter the title in the Title field. The System Name field is populated automatically with the text
entered in the Title field.
Modifying Sources
You can modify sources in the Repositories pane, under the App Builder tab, select the source that
you want to modify. Its properties are displayed in the Properties pane.
You can modify the Label, Route, data source and Workflow options.
CAUTION: The route is used to accessed the application and its functions. Renaming it will break any
links that reference it. Do it only when necessary.
You can change the source System Name by right-clicking it in the Repositories pane and selecting
Rename. The System Name must be unique within the application.
CAUTION: This operation will remove the source or the source group permanently.
CAUTION: It will be no longer possible to use any links or bookmarks to access the source or the
source group, unless a new one with the same route is created.
2. A message stating Are you sure you want to delete '[Element Name]? Deleting '[Element Name]'
will delete all its configuration items. This operation cannot be undone. is displayed. Click Yes to
continue the deletion.
The source or source group is deleted and removed from the App Builder tab once the repository is
saved.
Note: The system name and route must be unique within an application.
3. Modify the System Name field. The system name is the name shown in the App Builder tree in
the Repositories pane.
4. Modify Route as needed.
Note: The Route field represents part of the web address that will be used to access the newly
created screen. It accepts only lowercase alphanumeric characters, "-" and "_".
5. Click Next.
The next screen allows you to choose the Banner options.
Note: If the file size is other than 350px x 54px, it will be scaled to this size. While any image can
be scaled to fit the size, it is recommended to upload images in the right size. Small images can
get pixelated and large images can affect performance when the page is loading.
8. Click Next. A Summary screen is displayed.
9. If you are satisfied with the screen, click Finish.
The newly created screen is displayed in the App Builder tab in the Repositories pane under the
application it was created for, and in the Properties tab.
Creating Cards
A card is a collection of actions and tiles at a single screen that can be accessed and used quickly
and easily.
3. Enter the label in the Label field and the system name in the System Name field. The system
name is used to display the card name in the Repository pane.
Creating Tiles
Tiles allow you to access pre-configured sources within an application from the Quick Access
screen.
To create a tile:
1. In the Repositories pane, select a Quick Access Card for which you want to create a tile. Right-
click it and select New | Tile.
2. Enter the label in the Label field and the the system name in the System Name field. The system
name is used to display the card name in the Repository pane.
3. Click Next.
A screen with selection of tile types is displayed.
5. Select the source using the drop-down lists under Screen, Source Group and Source. You can
choose only from the sources that were already configured for a master screen. You can check
the instructions for adding new sources in the Adding Sources on page 42 section.
6. Click Next. A Summary screen is displayed.
7. If you are satisfied with the tile, click Finish.
You can add up to 12 tiles to a single card.
Modifying Screens
To modify an existing screen:
1. In the Repositories pane, under the App Builder tab, select the screen that you want to modify. Its
properties are displayed in the Properties pane.
2. To modify the Banner section enter the new Title,Sub Title, or select a new logo. These Banner
section is available only for the Quick Access screens.
3. Change the Screen Title and Route as required.
CAUTION: The route is used to accessed the application and its functions. Renaming it will break
any links that reference it. Do it only when necessary.
4. When you are satisfied with the changes, click Finish.
Deleting Screens
To delete a screen:
1. In the Repositories pane, right-click on the screen that you want to delete and select Delete.
CAUTION: This operation will remove the screen and all its properties permanently. It will be no
longer possible to use any links or bookmarks to access it, unless a new screen with the same
route is created.
2. A message stating Are you sure you want to delete '[Screen Name]'? Deleting [Screen name] will
delete all its configuration items. This operation cannot be undone. is displayed. Click Yes to
confirm the deletion.
The screen is deleted once the repository is saved.
Creating Actions
Actions can be executed by the user to interact with the system. Up to 12 actions can be created for
a master screen or a quick access card.
You can create the following actions:
• Create Unity Form on page 54
• Create WorkView Object on page 56
• Navigate to Screen/Data Source on page 57
• Open URL on page 59
• Upload a New Document on page 60
2. Enter the label in the Label field. The System Namefield is automatically populated with the
phrase entered into the Label field. It is used to name the action in the Repositories pane.
A screen with selection of types of actions is displayed.
3. Select the Create Unity Form action.
The Create Action screen is displayed.
Note: Remember that the user must have creation rights for the Unity Form to be created.
Note: Only Unity Forms can be created using this action. The following form types are excluded:
Image Forms, Unity Forms - Agenda, Unity Forms - Workflow.
5. Click Next. A Summary screen is displayed.
6. If you are satisfied with your action, click Finish.
2. Enter the label in the Label field. The System Namefield is automatically populated with the
phrase entered into the Label field. It is used to name the action in the Repositories pane.
A screen with selection of types of actions is displayed.
3. Select the Create WorkView Object action.
4. Select the application from the Application drop-down list to filter the available classes.
5. Select the desired class from the Class drop-down list.
6. Click Next. A Summary screen is displayed.
7. If you are satisfied with your action, click Finish.
2. Enter the label in the Label field. The System Namefield is automatically populated with the
phrase entered into the Label field. It is used to name the action in the Repositories pane.
A screen with selection of types of actions is displayed.
3. Select the Navigate to Screen/Data Source action.
The Create Action screen is displayed.
4. Select the screen to which the target source is assigned from the Screen drop-down list.
5. Select the Source Group and Source from the drop-down lists.
6. Click Next. A Summary screen is displayed.
7. If you are satisfied with your action, click Finish.
Open URL
This action allows the user to go directly to an external website. The target website will be opened in
a new window.
To create a new action:
1. In the Repositories pane, select a screen or a card for which you want to create an action. Right-
click it and select New | Action.
The Create Action wizard is displayed.
2. Enter the label in the Label field. The System Namefield is automatically populated with the
phrase entered into the Label field. It is used to name the action in the Repositories pane.
A screen with selection of types of actions is displayed.
3. Select the Open URL action.
Note: Remember that the HTTPS protocol is more secure. It is recommended to open external
sites using this protocol.
5. Enter the URL to the target website.
6. Click Next. A Summary screen is displayed.
7. If you are satisfied with your action, click Finish.
2. Enter the label in the Label field. The System Namefield is automatically populated with the
phrase entered into the Label field. It is used to name the action in the Repositories pane.
A screen with selection of types of actions is displayed.
3. Select the Upload a New Document action.
The Create Action screen is displayed.
Note: Remember that the user must have the appropriate rights for the Document Type to upload
documents.
5. Click Next. A Summary screen is displayed.
6. If you are satisfied with your action, click Finish.
The properties depend on the object type. To change them, enter the new properties or select them
from the drop-down menus and save the repository.
You can change the system name by right-clicking the card, action, or tile in the Repositories pane
and selecting Rename. The system name must be unique within the application.
Shortcut Description
Ctrl + a When a card or its subcatalogs are selected in the Repository pane tree,
opens the Create Action wizard.
Ctrl + g When a card or its subcatalogs are selected in the Repository pane tree,
opens the Create Source Group wizard.
Ctrl + p When the App Builder tab is selected in the Repository pane tree, opens the
Create Application wizard.
Ctrl + r When an application is selected in the Repository pane tree, opens the
Create Screen wizard.
Ctrl + t When a card or its subcatalogs are selected in the Repository pane tree,
opens the Create Tile wizard.
Ctrl + q When a card or its subcatalogs are selected in the Repository pane tree,
opens the Create Card wizard.
Connecting to Repositories
To access a repository, in the Repositories window, select the repository from the drop-down
list. You will either be automatically logged into the repository or you will be prompted for user
credentials.
Note: If there is a system lock, you will be unable to open the repository.
In order for your changes and additions to a repository to be reflected, you must save the repository.
Any changes you make will not be saved until the repository is saved. You can save a repository by
clicking Save button on the Home ribbon. Alternatively, you can click the Save drop-down menu and
select a specific repository to save or Save All to save all of the repositories.
Items that have been changed and not saved are denoted with an asterisk (*).
Upon clicking Save or Save All, a Saving Repository status window is displayed. You can click
Cancel to abort saving.
To open a database connection repository:
1. Database connection repositories are opened via the Connect dialog box. Open the Connect
dialog box in one of two ways:
• Launch OnBase Studio. The Connect dialog box is displayed on startup.
• If OnBase Studio is already connected to a repository, click Connect in the Home ribbon
menu to open another repository.
The Connect dialog box is displayed.
Note: In order to connect to an Application Server, the Application Server and Studio must both
be of the same major and minor version, and the same service pack version. For example, if the
Application Server is version 16.0.1, then Studio also needs to be version 16.0.1.
Note: Studio does not support remoting as a communication method for the Application Server.
SOAP must be used. Ensure that the full Application Server URL to the service page uses
Service.asmx.
3. Enter a Data Source or select one from the drop-down list. When Local is selected as the
connection type, the Data Source list is populated with all available data sources. When
connecting via an Application Server, the data source entered is saved as an option in the Data
Source drop-down list for future selection once you have connected successfully.
4. Select an Authentication Type from the drop-down list. The following options are available:
• Active Director Federation Services (AD FS) - Select this option to use Active Director
Federation Services authentication. To use this option, you must have the Application Server
configured for AD FS, and you must modify the Studio configuration file. For information on
how to modify the Studio configuration file to enable AD FS, see the Legacy Authentication
Methods module reference guide.
Note: AD FS is not available for use with the Local connection type.
• NT Authentication - Select this option to use Active Directory authentication. To use this
option, your system must be configured for Active Directory - Enhanced authentication. For
more information, see the Legacy Authentication Methods module reference guide.
• NT Authentication (Interactive) - Select this option to enter credentials for Active Directory
authentication. The User Name must include a domain. To use this option, your system must
be configured for Active Directory - Enhanced authentication. For more information, see the
Legacy Authentication Methods module reference guide.
• Standard Authentication - Select this option to use standard OnBase credentials.
Additional authentication methods may be available depending on the configuration of OnBase
Studio and your solution. Contact your system administrator for more information about
additional authentication methods.
5. If you are prompted, enter a User Name and Password.
Select Remember password if you want OnBase to remember your password.
6. Click Connect.
Note: For more information on Environment Value Management, see the Change Control
documentation.
Note: For more information about the OnBase Administration Portal, see the Configuration
Administration Portal documentation.
3. Expand Configuration.
4. Click Settings.
5. Enter the URL for the Administration Portal in the OnBase Administration Portal Web
Application URL field.
6. Click OK. The URL is saved and used to access the OnBase Administration Portal.
Refreshing Repositories
You can refresh a repository in order to work with the most up-to-date configuration for the database
that the repository is associated with. To refresh a repository, right-click on an item in the repository
within the Repositories pane and select Refresh or select an item and press F5 on the keyboard.
Refreshing will update the open repository, which has an item selected in it, with all changes that
have been saved to the database since the repository was opened. A refresh is not limited to
changes made by the current user, but will update the repository with all changes that have been
saved to the database. Items with changes that have not been saved to the database are not
refreshed.
If you mouse over the tab for an item open in the pane, you can see the current repository and user
information for that item.
Searching in Studio
You can search open server repositories for items within OnBase Studio. To access this feature,
press Ctrl + f on the keyboard, click Find in the Home ribbon, or right-click in the Repositories pane
and select Find. The Find dialog box is displayed.
Note: If the Find dialog box is opened when there is no repository open, the fields are disabled. Once
a repository is opened, the fields are enabled.
Enter search options and click Find All. Results are displayed in a tab at the bottom left windows of
OnBase Studio.
Search Options
Option Description
Repository Select the repository you want to search from this drop-down list.
Look at these types (Find This drop-down list allows you to specify the type of item you
Name) would like to search for.
The following options are available for the Find Name option:
• <All>
• Task Automator
• Storyboards
• Values / Local Data
• Workflow
• Actions
• Life Cycles
• Queues
• Rules
• Task Lists
• Timers
• WorkView
• Actions
• Applications
• Filter Bar Items
• Filter Bars
• Filters
• Folders
• Views
Option Description
Look at these types (Find This drop-down list allows you to specify the type of item you
Dependency) would like to search for.
The following options are available for the Find Dependency
option:
• AutoFill Keyword Sets
• Document Types
• Folder Templates
• Folder Types
• Keyword Type Groups
• Keyword Types
• Note Types
• Unity Scripts
• VB Scripts
• Task Automator
• Values / Local Data
Option Description
Find What You can enter what you want to search for in this field.
Look in You can search in all life cycles within the selected repository, the
currently selected life cycle, or a specific life cycle.
Find Options Match case: Select this if you want the text entered in the Find
What field to be used as a case sensitive search.
Match whole word: Select this if you want to search for the
complete words entered in the Find What field.
Exclude disabled items: Select this if you want to exclude
disabled items from Workflow search results.
Use: You can select this option and then select Regular
expressions to use the text in the Find What field as a regular
expression or Wildcards to allow wildcard usage in the search.
Note: Only valid regular expressions can be used to search.
Result options Find results 1 window: When this option is selected, the search
results will be displayed in the Find Results 1 tab.
Find results 2 window: When this option is selected, the search
results will be displayed in the Find Results 2 tab.
Search Results
Search results are displayed in one of two results windows, Find Results 1 and Find Results 2. Click
on the tab of the results window you want to view, and the results are displayed.
Results can also be filtered by right-clicking in the Find Results window and selecting Allow
Filtering in the context menu. Once enabled, click in the filter drop-down list to filter the results.
You can double-click on an item in the results list to open it in the Properties pane.
Note: If the value of a result begins with =, +, -, or @, a space and a single quote (') are prefixed to
the value.
Output Tab
The Output tab displays a log of all of the actions taken in OnBase Studio within a session. This log
contains actions that were completed in any repository during the session. The log items contain a
date and time stamp as well as a short description of the action.
You can copy the contents of the Output tab by selecting the text you want to copy, right-clicking on
the tab and selecting Copy. Alternately, you can press Ctrl + c on the keyboard to copy the selected
text.
You can clear the contents of the tab at any time. To clear the contents of the tab, right-click in the
Output tab and select Clear.
Shortcuts
The Repositories pane can be navigated using the left and right arrow keyboard keys. These keys
can be used to navigate and expand items in the pane.
You can also use the * key on the number pad or Shift + the right arrow key to expand a tree item and
its children in the Repositories pane. These shortcuts do not work on the repository top level item or
on the Life Cycles folder.
You can also use the Shift + the left arrow key to collapse a tree item and its children in the
Repositories pane. These shortcuts do not work on the repository top level item or on the Life
Cycles folder.
Press F2 to rename a selected item.
Click Esc while renaming an item to cancel renaming it and revert to its previous name. Click Esc
while creating an item to cancel the creation.
Press F5 to refresh the repository in which you have an item selected.
Press Y to select a Yes button.
Press N to select a No button.
If a dialog box contains a Cancel button, you can use the Esc keyboard key to cancel out of the
dialog box.
CAUTION: Using the Reset Cache option in OnBase Configuration or the Reset Server Cache
option in OnBase Studio may have a negative impact on system performance. Requests to the
Application Server will be forced to wait until the cache is rebuilt before they can be processed.
Depending on the size of the OnBase system, as well as the current server load, the performance
impact of resetting the cache may be severe. To avoid performance issues, only reset the cache of
the Application Server during off-peak hours. For more information about the Reset Cache option in
OnBase Configuration, see the System Administration documentation. For more information about
the Reset Server Cache option in OnBase Studio, see the Studio documentation.
In order for the Reset Server Cache button to be enabled, the user must belong to a user group that
has been granted rights to the Application Server Administrative Processing Privilege product right
and the System Configuration configuration right. See the System Administration module reference
guide or the Configuration help files for more information about product rights.
Studio Options
OnBase Studio has several display options. The Studio Options are accessed by clicking File |
Studio Options. The Studio Options dialog box is displayed:
General
The following options are configured in the General screen:
Option Description
Maximum Recent Items You can specify the maximum number of recently viewed items
that are displayed on the start page in the Maximum Recent Items
field.
Display the ID of Items When this option is selected, item IDs are displayed beside items.
Retrieve all items when the When this option is selected, all items are retrieved when a
repository is opened repository is opened.
Note: If a repository is large, this setting can increase the time it
takes to open the repository.
Option Description
Restore Default Layout You can restore the layout of the application to the original default
layout by clicking the Restore Default Layout button. The layout is
restored to the default.
Enable spell checking When this option is selected, the spell check feature will be
enabled.
Doctor
The following options control the user of the Workflow Doctor within the Studio. The following
options are available:
Option Description
Enable doctor validation This option controls whether or not the doctor validates items.
Deselecting this option disables all of the following WorkflowApp
Builder Doctor options.
Validate when the repository Select this option if you want a repository to be evaluated by
is opened the App Builder Doctor upon opening a repository in the OnBase
Studio.
Note: If a repository is large, this setting can increase the time it
takes to open the repository.
Validate when the repository Select this option if you want a repository to be evaluated by the
is refreshed App Builder Doctor upon refreshing the repository or checking out
a life cycle.
Validate when a portfolio Select this option if you want the App Builder Doctor to evaluate
relation is changed items when a portfolio relation is changed.
Underline repository tree When this option is selected, life cycle items that have warnings
items that contain warnings identified by the App Builder Doctor will be underlined in blue and
and error (requires restart) life cycle items that have errors identified by the Workflow Doctor
will be underlined in red. If both errors and warnings exist, the life
cycle item will be underlined in red.
Note: After changing this option, the OnBase Studio must be
restarted.
Highlight error issues in When this option is selected, errors are highlighted in the
property pages (requires Properties pane to easily identify the specific issue.
restart)
Note: After changing this option, the OnBase Studio must be
restarted.
Option Description
Highlight warning issues When this option is selected, warnings are highlighted in the
in property pages (requires Properties pane to easily identify the specific issue.
restart) If an action type is not defined, it is not highlighted, but can be
listed as an error in the Doctor Results tab.
Note: After changing this option, the OnBase Studio must be
restarted.
Actions and rule configuration When this option is selected, actions and rules are checked for
issues configuration issues.
Action and rule licensing When this option is selected, actions are checked for licensing
issues issues.
Actions that have no action When this option is selected, actions are checked for when no
type set action type is set.
API Task configuration issues When this option is selected, all configuration issues except
disabled API tasks, are reported.
Disabled actions and rules When this option is selected, life cycles are checked for disabled
actions and rules.
Disabled API tasks When this option is selected, the Doctor reports a warning when an
API task is disabled.
Disabled task lists When this option is selected, life cycles are checked for disabled
task lists.
Disabled workflow events When this option is selected, the Doctor reports a warning when a
App Builder event is disabled.
Life cycle configuration issues When this option is selected, life cycles are checked for
configuration issues.
Notification configuration When this option is selected, notifications are checked for
issues configuration issues.
Obsolete actions and rules When this option is selected, action and rules that are not
supported in the OnBase Studio are reported.
Portfolio Type configuration When this option is selected, portfolio types are checked for
issues configuration issues.
Queue configuration issues When this option is selected, queues are checked for configuration
issues.
Rules that have no rule type When this option is selected, rules are checked for when no rule
set type is set.
Task list configuration issues When this option is selected, life cycles are checked for task lists
with configuration issues.
Option Description
Timer configuration issues When this option is selected, timers are checked for configuration
issues.
Transition configuration When this option is selected, life cycles are checked for transition
issues configuration issues.
Unsupported user interaction When this option is selected, Workflow Doctor reports issues if
an action or rule requires user interaction that a client does not
support. (specified in the display issues related to client category)
User form configuration When this option is selected, user forms are checked for
issues configuration issues.
Workflow event configuration When this option is selected, all App Builder event configuration
issues issues except disabled App Builder events, are reported.
WorkView configuration When this option is selected, WorkView calculated attributes and
issues triggers are reported.
Client Core-based interface When this option is selected, issues directly related to the Core-
based Client Workflow interface are reported.
Unity When this option is selected, issues directly related to the Unity
Workflow interface are reported.
Web When this option is selected, issues directly related to the Web
Client Workflow interface are reported.
Managing Locks
You can manage locks within OnBase Studio. To access the Manage Locks dialog box, select File |
Manage Locks. The Manage Locks dialog box is displayed.
In addition to OnBase related locks, locks related to OnBase Studio are listed. If you want to only
see OnBase Studio related locks, select the Display only life cycle locks check box. All locks not
directly related to OnBase Studio are hidden from view.
Each row on the Locks tab contains the following information:
Column Description
User Displays the name of the user that placed the lock.
Note: Depending on your system configuration, the real name of the user may be
displayed.
Date Locked Displays the date and time that the lock was created.
Column Description
To remove a lock, select a row and click Remove Selected. To refresh the list, click Refresh.
Note: Depending on your configuration, you may or may not be able to see and manage the locks
associated with other users.
Output Window
Note: In order to use the Output window, OnBase Studio must have been configured for logging
during installation.
The Output window logs the events that occur within OnBase Studio The Output window can report
on any issues encountered in OnBase Studio as well as expected events, for example, opening and
saving repositories.
You can copy the contents of the Output window by highlighting the text you want to copy, right-
clicking and selecting Copy Ctrl + C. Alternatively, you can select the text you want to copy and
press Ctrl + C on the keyboard.
You can clear the Output window by right-clicking the window and selecting Clear.
The Window Position arrow button allows you to set the window to display in one of the following
ways: Floating, Dockable, and Auto Hide.
Selecting Floating displays the window is a undocked window outside of the main interface. This
window can be positioned anywhere on the screen. You can re-dock a window by right-clicking on the
window header and selecting Dockable and then double-clicking on the header of the window.
Selecting Dockable pins the window in a position within the main studio window.
Selecting Auto Hide enabled the window to hide when not in use. When a window is in Auto
Hide mode, a tab is displayed in the interface. Hovering over that tab will display the window. The
following is an example:
The Auto Hide button allows you to pin and unpin the window, toggling on and off the Auto Hide
mode for the window.
Upon clicking this drop-down menu, you can select one of the following options:
Option Description
Show Below the Ribbon This option is available when the Quick Access
Toolbar is displayed above the ribbon. When
selected, the Quick Access Toolbar is moved below
the ribbon.
Show Above the Ribbon This option is available when the Quick Access
Toolbar is displayed below the ribbon. When
selected, the Quick Access Toolbar is moved above
the ribbon.
Spell Check
Note: Spell check is only supported if OnBase App Builder is configured for one of the following
languages: English, French, German, and Spanish.
Note: Enabling or disabling the spell check option requires a refresh of the repository to take
effect.
The spell check option also allows you to add words to the custom dictionary file. This file
is referenced by the spell check option when looking for misspellings or when populating
suggestions for corrected spelling. To add words to the custom dictionary file:
4. Select File and click the Studio Options button. The Studio Options window is displayed.
5. In the General Options section, Locate the Custom Dictionary option under the Enable spell
checking check box.
6. Click the Open in Notepad button to open the custom dictionary file in the Notepad application.
7. Add a word to the document.
8. Save and close the file.
9. Click the OK button to exit the Studio Options window.
Note: Each word that is added to the custom dictionary file must be placed on a separate line
within the document.
When the spell check option is enabled, misspelled words are automatically underlined by a wavy red
line.
Right-click the underlined word to view the spell check right-click menu. The right-click menu
contains the following options:
• Spelling correction suggestions for the underlined word.
• Ignore All: This option allows you to set the spell check option to ignore all instances of the
same spelling error in the text box.
• Cut: When the underlined word is highlighted, this option allows you to remove the entire word
from the text box.
• Copy: When the underlined word is highlighted, this option allows you to copy the word to the
clipboard.
• Paste: This option allows you to paste the word that was copied to the clipboard into the text
box.
Exporting
You can export configurations from a database repository to an import package that can be
imported into another database repository.
Note: Depending on your system's licensing and your user rights and privileges, only certain
configuration items may be available for export.
The following configuration types can be exported in OnBase Studio:
• App Builder
• Capture Processes
• Document Composition ODBC Inputs
• Document Composition Templates
• Document Types (if there are multiple revisions of a Document Type, the latest revision is
exported)
• EIS Message Broker Types
• EIS On-Ramp
• EIS Workflow XML Messaging
• Folder Templates
• Folder Types
• Form Templates
• Item Generator Sets
• Item Generators
• Notifications
• Packet Templates
• Portfolio Relations
• Portfolio Types
• Print Formats
• Reading Groups
• Scan Queues
• Storyboards
• Unity Form Themes
• Unity Scripts
• Web Service Publishing
• Workflow Approval Processes
• Workflow Life Cycles
• Workflow System Events
• Workflow System Tasks
• Workflow User Forms
• WorkView Applications
• WorkView Classes
Export Considerations
• It is highly recommended that export packages are exported and imported using the same
database version and OnBase version.
• When certain configuration items are exported, related configuration items may also
automatically be exported, although they are not displayed in the export summary or available to
select for export. For example, when you export a Document Type, associated Keyword Types,
User Groups, and Document Type Groups are exported and available to import into a destination
database.
• When Folder Types are selected for export, only File Cabinets and Folder Types are able to be
exported. The following are not exported:
• Related folders
• Default templates
• Default filters
• Folder Types configured for Document Tracking cannot be exported.
• When an External AutoFill Keyword Set using a VBScript is exported, its VBScript, like its
Keywords, are automatically exported as separate objects, which can then be imported as well.
• Only published and active Unity Scripts are available for export.
• WorkView Item Generators are not available to be exported and Item Generator Sets that contain
WorkView Item Generators are not available to be exported.
• Translation strings configured for configuration items are exported with those configuration
items, however, additional manual configuration is required in the destination database the first
time a specific language is imported.
Exporting a Configuration
To export a configuration:
1. With the repository containing items you want to export selected, click the Export button in the
Home ribbon within the Import/Export ribbon group.
Note: If there are unsaved changes in the selected repository, you are prompted to save the
repository before exporting.
Note: You can export from OnBase Studio while using a Local connection the database.
2. Verify that the information listed for the Application Server and Data Source is correct.
3. Select a configuration item type from the item type selection list to display all available items in
the database for that configuration item type:
Note: The configuration item types displayed in the selection list is dependent on your licensing
and the context from which you access the Export wizard.
By default, configuration item types are organized in groups. To collapse all groups, click
Collapse All:
To search for a specific configuration item type, enter a search term in the search field. The
selection list is filtered as you type:
4. Select one or more configuration items from the configuration item selection list.
To select multiple configuration items, do one of the following:
• Hold Ctrl and click individual configuration items.
• Select a configuration item, hold Shift, and click another configuration item to select all
configuration items listed between the two.
To search for a specific configuration item, enter a search term in the search field. The
selection list is filtered as you type:
To search for a specific configuration item, enter a search term in the search field. The selection
list is filtered as you type:
5. Click Add to add the selected configuration items to the export package:
To add all configuration items in the selection list to the export package, click Add all:
6. Repeat the process as necessary to add different types of configuration items. The configuration
items are listed and grouped by configuration item type in the export package list:
To collapse a configuration item group in the export package list, click the collapse button:
To remove selected configuration items from the export package list, click Remove:
To remove all configuration items from the export package list, click Remove all:
Note: When clicking Remove all, you are prompted to confirm the action.
7. Click Start Export. The Export Progress page is displayed and the export process begins:
8. When the export process is complete, the Export Results page is displayed and any relevant
errors, warnings, or informational messages are listed in order of severity, sorted by event type.
Warnings cause the export to be partially successful, allowing you to still download and save the
export package. Errors cause the export to fail, preventing you from downloading and saving the
export package. An example of an error is that a required document, such as a template, could
not be exported.
To toggle whether errors, warnings, or informational messages are shown, click Show Errors,
Show Warnings, or Show Informational Messages, respectively:
Tip: You can copy errors, warnings, and informational messages to your clipboard by right-
clicking the message pane and selecting Copy or by selecting a message and pressing Ctrl + C.
If changes to the export package are necessary, click Back to Item Selection to return to the
Item Selection page.
9. To customize the export package, click Customize Export. The Export Details page is displayed:
To return to the Export Results page without regenerating the export package, click Back to
Export Results and skip to step 14.
To return to the Item Selection page, click Start Over.
10. In the export package item list, the following columns are displayed:
Column Description
Column Description
• Configuration items that reference multiple items in the export package are displayed as
descendants under each referenced item. If a displayed descendant is also the descendant
of a configuration item more closely related to the configuration items explicitly selected for
the export package, it is designated with the following icon:
• Configuration items that cannot be customized are designated with the Map Only Item icon:
11. Select a configuration item to view its descendants in the Selected Properties pane. If multiple
configuration items are selected, all descendants of all selected configuration items are
displayed. The number of configuration items selected and the number of descendants that
reference the selected configuration items are displayed:
Descendants are grouped by configuration item type. To collapse a configuration item group,
click the collapse button:
12. To queue the selected configuration items for partial reference, click Make Partial. To queue the
selected configuration items for full reference, click Make Full.
Note: Configuration items explicitly selected for export cannot be queued for partial reference.
The queued configuration items are displayed. The number of changes to be made to the export
package and the total number of unique configuration items to be included in the export package
are displayed:
13. Click Regenerate Package. The Export Progress page is displayed. With the customizations
applied, the export process begins again, and the Export Results page is displayed when the
export process is complete:
14. Do one of the following to specify the encryption of the export package:
• To encrypt and require a password for the export package, select Encrypt Export File.
• To export the package without encryption and password protection, deselect Encrypt Export
File.
Note: Depending on system settings, the Encrypt Export File option may be enabled or
disabled. If the option is enabled, entering a password for the package is optional. If the
option is disabled, entering a password for the package is required.
15. Click Save Package.
16. If Encrypt Export File was selected, enter a password in the Password field, and reenter it in the
Confirm field.
Keep this password in a safe place. It is required when uploading the package in the Import
wizard. If the password is lost, it cannot be retrieved.
Note: Passwords must adhere to any displayed requirements. All passwords must be at least 14
characters in length. If a password policy is being used and it requires fewer than 14 characters,
the export cannot be completed.
17. In the Windows Save As dialog box, specify a location and enter a file name for the export
package. Ensure that Export package files (*.expk) is selected as the Save as type.
18. Click Save.
19. Close the Export dialog box.
Importing
Once you have exported a configuration, you can import it into the appropriate repository.
Note: Importing involves careful scrutiny of the data presented in the import dialogs. Care must be
taken to identify each element in the life cycle to be imported, and determine how those elements
will be mapped to the import life cycle.
Note: To ensure no errors are encountered, ensure the SYS Upload Reconciliation Document Type
has a Disk Group assigned.
Import Considerations
• Before importing an export package, ensure Disk Groups are properly configured.
• It is highly recommended that export packages are exported and imported using the same
database version and OnBase version.
• Disk Groups can only be mapped during import, and cannot be created or used to replace
existing Disk Groups.
• When a Keyword Type is mapped, only those Keyword Types sharing the same Data Type in the
destination database are displayed (i.e., you do not have the option to map an alphanumeric
Keyword Type to a numeric Keyword Type).
• When mapping an Alphanumeric Keyword Type, it is considered a best practice to ensure the
length of the imported Keyword Type matches the length of the Keyword Type in the destination
database.
• When a Keyword Type is replaced, Keyword Type Data Set values from the imported Keyword
Type are imported only when the Keyword Type in the destination database contains no existing
Keyword Type Data Set values.
• When an encrypted Keyword Type is imported, the encryption is removed. You are notified that
the encryption of the Keyword Type is modified upon verifying your import changes.
• You cannot replace AutoFill Keyword Sets or Cascading Data Sets using AutoFill Keyword Sets or
Cascading Data Sets from an export package. This is because once these sets are created, you
cannot modify the Keywords contained within them.
• External AutoFill Keyword Sets using a WorkView filter can only be mapped to an existing AutoFill
Keyword Set; they cannot be created or used to replace another existing AutoFill Keyword Set.
• External AutoFill Keywords Sets using an EIS data source can be created or mapped to an
existing AutoFill Keyword set; they cannot be used to replace another existing AutoFill Keyword
Set.
• When importing Folder Types, understand the parent/child relationship between folders and
how import actions can affect the relationship. For example, if you select Create to create the
parent folder in the destination database but select Map to map a child folder to another folder
in the destination database, the relationship between the two folders is broken. The child folder
becomes either a parent or a child of another folder, depending on how it was mapped.
CAUTION: When importing a Folder Type from an export package created in OnBase 15, the
respective file cabinet is created but not linked to a Folder Type. As a result, some folder
configuration, such as auto-foldering, is not maintained after import. As a best practice, do not
select to create Folder Types from an export package created in OnBase 15; however, if this does
occur, ensure the created file cabinet is linked to a Folder Type to avoid unexpected behavior.
• Some older export packages may contain Unity Form templates or Document Composition
templates with missing document references. While it is no longer possible to export these
configuration items with missing document references, older packages containing missing
references can be partially successful during import (i.e., import will not fail due to missing
references, but it will not be successful in importing the required template document).
• When a process is imported for the Document Import Process or COLD Processor, process paths
are not imported. They must be properly configured in the destination database.
• Environment values are not imported, but are displayed in the Post-Import Report and logged in
the import verification report document archived in the destination database. Environment values
must be properly configured in the destination database.
• When Users are set to Create, they are not assigned to User Groups in the destination database.
User security must be explicitly configured by system administrators.
• If a Unity Script is owned by a deactivated user, upon importing, the MANAGER group will be
assigned as owner.
• When importing packages created prior to OnBase 18, passwords for imported user accounts
must be manually reset.
• Translation strings of Map Only configuration items are not imported.
• When importing WorkView applications with with notification or display template files created
prior to OnBase 23.1, the WorkView Doctor tool has to be used first to update such application
and move its content into database.
Warning: It is not possible to import WorkView applications with notification or display template
files without using WorkView Doctor to perform updates first.
Importing a Configuration
To import a configuration:
1. With the repository containing items you want to export selected, click the Import button in the
Home ribbon within the Import/Export ribbon group.
Note: You can import into OnBase Studio while using a Local connection to the database.
Note: In order to import configurations which were exported using the Configuration module, you
must have the System Configuration configuration right.
2. Verify that the information listed for the Application Server and Data Source is correct.
Note: You are notified if a previous import was left incomplete. You cannot perform a new import
until the previous import is completed. To resolve the previous import, evaluate and complete
it in Import Management, or contact your first line of support. For more information on Import
Management, see the section on viewing import history in the System Administration module
reference guide.
If change control settings have not been configured, continue to step 3. Otherwise, skip to step 7.
Note: Access to import settings is also available from the import layout.
3. Configure change control settings by selecting Import Settings | Change Control Settings.
4. Enter a directory path in the Change Control File Directory field, or click Select Directory to
browse for and select a directory.
Note: A Change Control File Directory must be specified in order for users to perform an import.
When specifying a directory, consider the following:
• The specified directory must be accessible to all Application Servers and clients.
• The specified directory must be writable by all Application Servers.
• The Change Control File Directory is used during the import process to store external files
associated with configuration items that are imported. After import, the imported external
files are stored in a subdirectory of the specified directory.
• An Import folder is created in the specified directory if one does not already exist.
5. Select or enter a value for the following options:
Option Description
Maximum import file size Specifies the largest allowed file size (in megabytes) for a package
(MB) being imported through the Import wizard.
Package encryption Enforces a password policy to encrypted export packages. When the
password policy administrator enters a password for an export package, the password
must adhere to the selected password policy before the package is
exported.
Select None to allow the administrator to use a password that does
not adhere to a password policy.
For more information on password policies, see the section on
enforcing user password security in the System Administration
module reference guide.
Option Description
Force encryption on export When selected, selects and disables the Encrypt Export File option in
the Export wizard. This forces the administrator to enter a password
for the package being exported.
When deselected, enables the Encrypt Export File option in the
Export wizard. This allows the administrator to optionally enter a
password for the package being exported.
6. Click Save.
7. If necessary, select Import Settings | Import Management to view import history. For more
information, see the Viewing Import History section of the System Administration module
reference guide.
Note: Access to import settings is also available from the import layout.
8. In the Selected package field, enter the directory and file name of the export package to import,
or click Browse to locate and select it. Export packages have a file extension of .expk. If you
select any other file type, an error is displayed in the Status area of the Import dialog box.
Note: If the export package is open or has been modified outside of OnBase, an error is
displayed, and you are prevented from importing the package. If the package is open (e.g., using
a zip program), close the package file. If the export package was modified outside of OnBase,
select a different export package, or create a new one.
9. If the package is encrypted, you must enter the password for the package and click Decrypt:
Note: Certain packages may not be valid for import. Configuration settings may restrict
packages due to file size or lack of encryption. Also, depending on the context from which you
are accessing the Import wizard, certain packages may be invalid for the current context. For
example, if you attempt to import a package to the Reporting Dashboards Import wizard that was
exported from the Configuration Export wizard, an error is displayed in the Status area below the
package selection area.
Item Description
A Navigation bar
C Properties pane
The Application Server, data source, user, and package name are displayed in the Navigation bar.
11. In the Configuration Items pane, all configuration items included in the export package are
listed. By default, <<User Exported>> is selected in the left pane, and the configuration items
explicitly selected by the user who created the export package are displayed:
To view all configuration items included in the export package, select <<All Items>> in the left
pane. To view explicit and implicit configuration items by type, select a configuration item type in
the left pane.
To cancel the current import process and start a new import process using a different export
package, click Select a Different Package on the Navigation bar. Any decisions made during
the current import process are not saved, and you are returned to the initial Import wizard page.
12. To view more information about user-selected items and the relationship between all items in the
export package, click Explore Package on the Navigation bar. The explore package dialog box is
displayed:
13. In the export package item list, the following columns are displayed:
Column Description
Column Description
• Configuration items that reference multiple items in the export package are displayed as
descendants under each referenced item. If a displayed descendant is also the descendant
of a configuration item more closely related to the configuration items explicitly selected for
the export package, it is designated with the following icon:
• Configuration items that cannot be customized are designated with the Map Only Item icon:
14. Close the explore package dialog box to return to the import layout.
15. The columns on the Configuration Items pane can be customized in the following ways:
• To sort configuration items alphabetically by Type, Name, Status, or Target Name, click the
corresponding column header.
• To reorder columns, click and drag a column header to the edge of another column header:
• To filter configuration items, use the filter controls at the top of each column.
• To search for a specific value in a column, enter the value in the filter control for that column.
For example, enter the name of a configuration item in the Name field to search for that item
by name. The configuration item list is filtered as you type.
Tip: Click and drag the borders of the columns in the Configuration Items panel to resize them.
16. Each configuration item must be configured with a decision option. To decision configuration
items, see the following:
• To manually decision configuration items, continue to step 17.
• To automatically decision configuration items, see Auto Resolution on page 113.
• To load decisions previously saved to an XML file, see Load Decisions on page 114.
Note: By default, all configuration items included in the export package are configured to not be
imported, and the decision status No Action is displayed in the Status column.
17. One or more configuration items can be decisioned at a time. To decision configuration items,
see the following:
• To decision a single configuration item, continue to step 18.
• To decision multiple configuration items simultaneously, skip to step 19.
18. To decision a single configuration item:
a. Select a configuration item in the Configuration Items pane. The available decision options
are displayed in the Properties pane:
Note: Available decision options may vary based on the configuration item.
b. Select one of the following decision options:
No Action The selected item is set to not be imported into the destination database.
When an item is not migrated using the No Action decision, references
from other items remain. This can lead to orphaned rows that reference the
non-migrated item. It is considered a best practice to remove references to
an item before selecting No Action for it.
Create The selected item is set to be created as a new item in the destination
database. Existing configuration settings and references are carried over to
the destination.
After selecting Create, the New Name field is displayed. If necessary, enter
a different name for the item to be created in the destination database. The
New Name field respects the maximum number of characters allowed for
names belonging to the configuration item type.
Replace The selected item is set to replace a specified configuration item in the
destination database, including related configuration and references.
After selecting Replace, the New Name field is displayed, along with a
list of available configuration items in the destination database. Select
the appropriate item to replace. If necessary, enter a different name for
the item in the destination database. The New Name field respects the
maximum number of characters allowed for names belonging to the item
type you are updating.
Note: When Replace is selected, an item in the destination database is
automatically selected if it matches the name of the item being imported.
If the configuration item selected in the Configuration Items pane has
associated children configuration items, Apply Decision To Children is
enabled. Click Apply Decision To Children to use the decision options
selected for the parent configuration item for all its children configuration
items.
c. If the configuration item selected is a Document Type with associated overlays, the
Documents section is displayed:
For each overlay listed, select No Action, Create, or Map. If Map is selected, select an
overlay to map to from the list that is then displayed.
d. Continue to step 20.
19. To select the same decision options for multiple configuration items simultaneously:
a. Select multiple configuration items in the Configuration Items pane using one of the
following methods:
• Hold Ctrl and click multiple configuration items.
• Press Shift + Down Arrow to select the configuration item below the selected
configuration item in addition to the selected configuration item.
• Press Shift + Up Arrow to select the configuration item above the selected configuration
item in addition to the selected configuration item.
• Press Ctrl + Shift + End to select all configuration items below the selected
configuration item, including the selected configuration item.
• Press Ctrl + Shift + Home to select all configuration items above the selected
configuration item, including the selected configuration item.
• Hold Shift and click two configuration items to select them and all configuration items
between them.
Remove Actions The selected items will not be imported into the destination database. Previous
decisioning for any of the selected configuration items will be removed.
Create as New The selected items will be created in the destination database.
Items
Map to Existing The selected items will be mapped to configuration items in the destination
Items database whose names match exactly. For configuration items whose name
does not have an exact match, no action will be taken.
Replace Existing The selected items will replace configuration items in the destination database
Items whose names match exactly. For configuration items whose name does not have
an exact match, no action will be taken.
21. If errors or warnings result from verification, they are listed in the Errors and Warnings pane in
order of severity, sorted by event type:
Tip: Double-click on an error or warning to select the affected configuration item in the
Configuration Items pane and display its selected decision option in the Properties pane.
Tip: You can copy errors and warnings to your clipboard by right-clicking the Errors and
Warnings pane and selecting Copy or by selecting a message and pressing Ctrl + C.
After resolving errors and warnings, click Run Verification.
22. Click Proceed to Import.
Section Description
Section Description
Items Replaced Lists the item name and target name of the
configuration items decisioned as Replace, organized
by configuration item type.
To return to the previous page and edit decisions, click Back to Decisions.
To verify the information displayed in the Pre-Import Report and begin import, click Start
Import.
24. Once the import is complete, the Post-Import Report is displayed and indicates whether the
import was successful:
If the import is unsuccessful or partially successful, errors or warnings are listed. For more
information about specific error or warning messages, contact your first line of support.
Information regarding the import is stored in a SYS Verification Reports Document Type
document that is automatically generated.
Note: Configuration items decisioned as No Action are not displayed in the import verification
report document.
25. Click Finish.
Auto Resolution
To automatically decision all configuration items listed in the export package:
1. Click Auto Resolution. The Auto Resolution dialog box is displayed:
2. Select Create Unmatched Items to assign the Create decision option to any configuration
items for which a matching item cannot be found to map to. Without this option selected, any
configuration items that do not have a match will not have their decision option changed. This
option is selected by default.
3. Select Override Existing Actions to allow automatic resolution to override and reassign any
decision options that have already been selected by the user.
4. To automatically resolve items based on decisions made for those items during a previous
import, select Auto Resolve Using Previous Decisions. To automatically resolve items based
on item name only, select Auto Resolve Using Item Names Only.
Note: If a configuration item has not been previously imported, it will be resolved based on item
name.
5. Click Automatically Resolve All Items.
CAUTION: Any decisions made by the automatic resolution logic are only suggestions. Verify all
decisions before proceeding to import. Depending on how the decision options are automatically
assigned, you still may need to manually decision some configuration items.
Save Decisions
To save decisions:
1. Click Save Decisions. The Save As dialog box is displayed.
2. Specify a file name and select a location to save the file.
3. Click Save.
Load Decisions
To load previously saved decisions:
1. Click Load Decisions. The Open dialog box is displayed.
2. Navigate to and select a previously saved decisions XML file.
3. Click Open. The decision options of the configuration items in the Configuration Items pane are
updated.
From OnBase Studio, you can view configuration changes that are made to the system
configuration environment.
The following configuration item types can be tracked:
• All items configured in OnBase Studio
• AutoFill Keyword Sets
• Cascading Data Sets
• Currency Formats
• Document Composition Categories
• Document Composition ODBC Inputs
• Document Composition templates
• Document Types
• Document Type Groups
• Keyword Types
• Keyword Type Groups
• Notifications
• Reverse AutoFill Keyword Sets
• Unity Form Data Sets
• Unity Form Templates
• Unity Form Themes
• WorkView Screen
• WorkView View
You can search for configuration changes by date, configuration item name, configuration item
type, and by the user who made the change. Search results displayed in Change Tracking can be
saved to a CSV file.
To view and save configuration change search results:
4. In OnBase Studio, in the Change Control ribbon group on the Home tab, click View Changes.
The Change Tracking dialog box is displayed:
The date and time of the last search and the number of results of the current search are
displayed at the bottom of the Change Tracking dialog box.
To view the current data source, Application Server, and user accessing Change Tracking, click
the info icon:
Parameter Description
Start Date Enter a start date or select a start date by clicking the calendar icon to
view configuration changes made after that date. The default value is
two weeks before the current date.
End Date Enter an end date or select an end date by clicking the calendar icon to
view configuration changes made before that date. The default value is
the current date.
Item Name Enter the name of a configuration item to view configuration changes
made to it.
Parameter Description
Configuration Type Enter a configuration type or select one or more configuration types
from the drop-down list to view configuration changes made to
configuration items of those configuration types. To clear selected
configuration types, click Clear current selection:
User Enter the name of a user to view configuration changes made by that
user.
To clear all search parameters and reset the start date and end date to their default values, click
Reset.
6. Click Search.The search results are displayed with the following columns:
Column Description
Item Name The name of the configuration item that was changed.
Configuration Type The configuration type of the configuration item that was changed.
Change Type The type of configuration change that was made, for example, creating,
modifying, or deleting a configuration item.
User The name of the user who made the configuration change.
Operators
Column filter operators are used to define how to apply a filter to the configuration items list with
regard to the value specified in the column's filter drop-down list.
Operators are available by clicking the operator button:
Operator Description
Equals Values equal to the value specified in the corresponding drop-down list are
displayed.
Not equals Values not equal to the value specified in the corresponding drop-down list
are displayed.
Less than Values less than the value specified in the corresponding drop-down list are
displayed.
Less than or equal to Values less than or equal to the value specified in the corresponding drop-
down list are displayed.
Greater than Values greater than the value specified in the corresponding drop-down list
are displayed.
Greater than or equal Values greater than or equal to the value specified in the corresponding
to drop-down list are displayed.
Contains Any values containing the value specified in the corresponding drop-down
list are displayed.
Does Not Contain Any values containing the value specified in the corresponding drop-down
list are not displayed.
Like (wildcards) Values like (including wildcards) the value specified in the corresponding
drop-down list are displayed.
Not like (wildcards) Values that are not like the value (including wildcards) specified in the
corresponding drop-down list are displayed.
Match (regular Values that match (including regular expression) the value specified in the
expression) corresponding drop-down list are displayed.
For example, typing a*t in the Status column displays configuration items
with the status Create or No Action, because both statuses contain the
letters a and t.
Does not match Values that do not match (including regular expression) the value specified
(regular expression) in the corresponding drop-down list are displayed.
Starts with Values that start with the value specified in the corresponding drop-down
list are displayed.
Operator Description
Does not start with Values that do not start with the value specified in the corresponding drop-
down list are displayed.
Ends with Values that end with the value specified in the corresponding drop-down list
are displayed.
Does not end with Values that do not end with the value specified in the corresponding drop-
down list are displayed.
In This option is intended for use with Reporting Dashboards. For more
information, see the Reporting Dashboards module reference guide.
Not In This option is intended for use with Reporting Dashboards. For more
information, see the Reporting Dashboards module reference guide.
Drop-Down Lists
In conjunction with column filter operators, column filter drop-down lists are used to select or enter a
value that defines how to apply a filter to the configuration items list.
To select an option from a column's drop-down list, click the drop-down arrow:
To enter a value in the drop-down list, click to the left of the drop-down arrow and enter the value.
The configuration items list is filtered as you type.
The following options are available for selection from all drop-down lists:
Option Description
(Custom) The Custom Filter Selection dialog box is opened, and a custom filter can be
created.
For more information, see Custom Filter Selection on page 119.
Each column's drop-down list also contains all the unique values in the configuration items list for
that column. For example, the drop-down list for the Type column lists the configuration item types
contained in the export package:
All filtering applied to the configuration type list column can be cleared by clicking the following
button:
Sources organizing
• Organize sources
There are different ways to make sources available to users. You can either create one master
detail page with many different groups and sources or you can break the sources out into more
pages with less source groups.
• Single Source pages
The first source on a page will be loaded by default. It allows you to highlight important sources
(such as a Dashboard) by giving them their own page and easily navigate to it.
• HUB pages
If users have access to multiple applications, create an application that pulls them all together
like a hub. Create a quick access page with actions that link to other applications.
• Multiple personas with overlapping tasks
If you have multiple personas with similar or overlapping task, you can organize the content in
several ways. An example could be an HR Generalist and a Supervisor. The Supervisor may do
many of the same tasks the Generalist does, but may need some extra ‘admin’ functionalities.
You can choose one of the following options:
• Duplicate an application by exporting it and import it back under a new name with a
different route. Then add additional functionalities that the supervisor needs to the imported
application.
• Both personas use the same applications for day to day functionality. Break the admin
features out into a seperate application that just the supervisor has access to. You can use
the ‘Open URL’ action to allow the supervisor to navigate between the apps.
User interface
• Labels
Labels are displayed to the user in the user interface. When labeling items like sources, actions
and others, try to use the language of the intended persona and avoid technical terms.
You can use 'Create a PTO Request' instead of 'Create a Unity Form', or name a workflow queue
source 'My Assigned Invoices' instead of 'Assigned Invoice Queue'.
Administration
• Copying Applications
Currently, it is not possible to copy or duplicate an application. However, you can easily export
an existing application and import it as a new one. This allows you to quickly create a copy of an
application to create its new version or add additional functionalities to it.
• Versioning
Sometimes you may want to work on a new version of an application while your users are still
working in the app. You can import the application in under a new name and route and make your
modification.
Send some of your power users a link to the new app to test it. Once satisfied, change the route
of the previous application to something else (i.e. app-old) and change the route of the new
version to the previous one. Now users can access the new application through their existing
link.
User Guide
Foundation 24.1
Usage
Usage
App Builder is a point-and-click-configurable application generator that allows you to create custom
applications to meet your specific business needs. The type of information that is tracked and
displayed is completely configurable.
The conent and addresses of the application depend entirely on the configuration, so every
configuration will yield unique results. This section will cover the possible components of the App
Builder. You may or may not have all of the components described.
Tip: If you do not know the details of the application address, you can obtain them from your
system administrator.
3. If you were not logged into the Web Client, a login page is displayed. Enter your OnBase
credentials and click Login.
After logging in, the default screen of the application is displayed.
Application Overview
An application is a collection of one or more screens with pre-configured buttons, options, and
sources.An example of an application is shown below.
Element Description
A: Application Title Title given to the application during configuration. You can click it to
go back to the default screen.
B: User settings and logout You can use the settings to change appearance of the application or
to log out.
The contents and sizes of screen elements depend on the screen on which the application is
displayed.
Element Description
A: Application title Title given to the application during configuration. You can click
it to go back to the default screen.
B: User settings and logout You can use the settings to change appearance of the
application or to log out.
C: Tabs with screens Tabs with other screens configured within the application.
The currently selected screen name is underlined. You can
select the name of a different screen to display it.
D: List of sources List of system resources configured and accessible within the
application. The currently selected and displayed source is
highlighted.
Workflow queues have an additional number of documents
currently in the queue displayed next to them.
E: Keyword pane of All Applicant You can use the keyword pane to search for the documents.
Documents source For details, see Use Keywords for Document Retrieval on page
175.
You can see any configured user instructions when you click
the "i" icon next to the source name.
Element Description
G: Documents retrieved from the For more information, see Viewing Documents on page 137
system and Retrieving Documents on page 130.
• A: You can collapse or expand the sources pane using the blue arrow icon at the bottom of the
pane.
• B: You can resize the width of the sources pane, using the vertical line next to it.
• C: You can resize the width of the query columns, using the vertical line next to the column
name.
Element Description
A: Application title Title given to the application during configuration. You can
click it to go back to the default screen.
B: User settings and logout You can use the settings to change appearance of the
application or to log out.
C: Tabs with screens Tabs with other screens configured within the application.
The currently selected screen name is underlined. You can
select the name of a different screen to display it.
D: Quick Access Screen logo, title and Elements configured in the application for branding
subtitle purposes.
E: Card and card title Cards are a collection of application elements, such as
actions or tiles, which provide faster and direct access to the
resource.
Element Description
G: Tiles Tiles configured for the particular card, which can be used to
access a source directly.
Settings
You can change the settings of the application by clicking the drop-down arrow next to the user icon
in the upper-right corner and selecting Settings.
Changing Theme
You can select one of the three theme options:
• Match System - the theme matches the one set for the Web Client
• Light - the theme matches the one configured by the App Builder administrator
• Dark - sets a dark theme for the application.
Note: The Dark theme is not available if the Web Client is configured to use as OEM Product
Name.
Accessing Screens
A single application can include multiple screens, configured to fit the specific purposes of your
company. A list of all screens available to you is displayed at the top of the application page, under
its name.
The currently selected screen name is underlined. To change the current screen, click on the name of
a different screen on the list.
Note: You can bookmark any of the screens to access them faster.
Retrieving Documents
Document Retrieval is used to retrieve documents, files and other content stored within the system.
1. Do one of the following:
• Go to the Master Screen with a list of sources and select the source you are interested in.
• Select a preconfigured tile to go to the source directly.
• Use your own bookmark to go to the source directly.
2. On the list of sources, select a source that you are interested in. If you used a direct link, the
source is already selected.
Note: The Workflow queue source type has a number of documents in a queue shown next to
the source name.
The source is highlighted and a keyword panel is displayed.
3. Put in the keywords in the keyword panel, marked in red in the image below:
You can use operators to narrow down your search. For details, see Keyword Operators and
Extended Search Features on page 176.
4. Click Search.
5. You can use the following interface options to further narrow down your search:
• A: Use the field with the looking glass icon to search for a particular word.
• B: Use the No Grouping field to allow grouping document by its properties. Once grouping is
selected, the field is changed to the chosen grouping type.
• C: Use the arrow in the column name field to change the sorting order.
6. To open a document in a Document Viewer, click it once. See Viewing Documents on page 137
for further support.
7. If you wish to start a new search or you are not satisfied with the results, you can use the Clear
All button to clear the keywords.
Using Folders
Your application may include a Folder Custom Query. Folders allow you to organize documents
electronically in an easy to use way. Additionally, you can easily spot which documents are missing
from a pre-configured set.
To use Folders:
1. Do one of the following:
• Go to the Master Screen with a list of sources and select the source you are interested in.
• Select a preconfigured tile to go to the source directly.
• Use your own bookmark to go to the source directly.
The Folder Custom Query is displayed.
• Use the field with the Looking glass icon to search for a particular result on the result list.
• Use the No Grouping field to group the results. You can group them by the Folder Name.
• Use the Arrow icon to change sorting of folders to ascending or descending.
4. To open a folder, select it from the results list. Content of the folder is displayed.
If it is configured in your application, you can upload the missing documents. For more information,
see Importing Documents on page 183.
5. Type the note text in the field provided. When adding a bookmark, the Auto-Name string of
the bookmarked document and the page number on which you are placing the bookmark are
displayed in the field by default. This text can be removed or edited as needed.
6. Click Add. The new note is added to the top of the Notes pane.
A dialog box reading Are you sure you want to delete this folder note? is displayed.
2. Click Yes.
The note is deleted.
Viewing Documents
App Builder uses the Web Client Document Viewer to display documents stored in the system.
When working with documents in OnBase, it is important to understand that documents may behave
slightly differently, depending upon their file format. A file format identifies the type of digital file.
The two most common file formats are image documents and text documents. Other file formats
could include XML, video formats, or OLE documents such as those created with Microsoft Office
applications. See your system administrator for specific questions regarding your system's file types
and their default behavior.
Tip: Drag toolbars to different positions to customize the interface. To move a toolbar, position your
pointer over the vertical bar on the left side of the toolbar. Then, click and drag the toolbar to its new
position.
The Web Client Viewer Control toolbar allows you to view the document more efficiently. Use the
buttons to navigate within the document, resize and reorient the page, and print.
Note: A different toolbar is displayed when you are viewing PDF or OLE documents. See Web Client
PDF and OLE Document Viewer Toolbar on page 145 for information about the toolbar that is
displayed when you view PDF or OLE documents.
Button Description
Print displays the Print dialog box, if you have user rights to print the document.
Button Description
Zoom In magnifies the view of a document, reducing the portion that is visible. Every zoom
increases magnification by one third.
Zoom Out reduces the magnification of a document, increasing the portion that is visible.
Every zoom reduces magnification by one quarter.
Actual Size displays the document in its actual size (as it is stored in OnBase).
Clicking this button sets the magnification to 100%.
Note: This zoom level differs from True Size, which takes the monitor's and image's DPI
into account when displaying the image.
Fit Width resizes the document page so that its width is the same as the width of the
document display area.
Fit Height resizes the document page so that its height is the same as the height of the
document display area.
Fit in Window resizes the document page so that it completely fits the document display
area.
Show Alternate Rendition is available only for documents that are allowed to have
multiple renditions. This button allows you to view a different rendition of a document
when the document has multiple renditions. To view a list of the available renditions, click
this button. Select the rendition you want to view from this list.
Text Search allows you to search for specific text strings within the document.
For more information, see Web Client Internal Text Search Toolbar on page 140.
Generate Report allows you to generate a system report of internal text search results.
For more information, see Web Client Internal Text Search Toolbar on page 140.
Button Description
Toggle Annotation enables you to add one or more annotations to the document by
selecting the annotation(s) from the adjacent drop-down list of available annotation types.
You remain in annotation addition mode until you click the Toggle Annotation button
again.
For more information, see Web Client Annotations Toolbar on page 142.
Scale to Gray softens the contrast of text and image documents at zoom levels of less
than 100%. This feature is most noticeable on black-and-white images, making it helpful for
reading scanned documents containing text that is too dark or too light.
From an open text-based document in the Web Client, use the functions in the Internal Text Search
toolbar to search for specific text strings within the document.
Note: You cannot execute an internal text search on a text document that has an overlay applied to it.
Remove the overlay in order to execute the internal text search.
• You can limit the text string search to one or more consecutive columns (character positions).
• If the document is a COLD-processed document with one or more column indexes defined, then
you can limit the search to the block of text defined by a column index. This is recommended for
large documents to improve performance time when searching.
See the following topics for information about the available functionality for performing internal text
searches in the Web Client:
• Performing an Internal Text Search in the Web Client on page 140
• Generating an Internal Text Search Report in the Web Client on page 141
2. Click in the text entry field and type the characters to search for. As you type, results that match
the search string are highlighted on the document.
3. Click the Find Next button or press Enter to find subsequent occurrences of the text.
Occurrences of the specified search string are highlighted on the document.
4. To limit the search between specific columns, click the Expand button:
2. Enter a search term in the Search Term field. This is the search term that will be searched on the
document.
3. Enter a name for the report in the Report Description field. The text entered in this field will be
used as the Description keyword value on the report.
4. If applicable, enter the number of lines of text to show above and below the found text in the
Lines before found text and the Lines after found text fields.
5. Click the Generate Report button. The search report is created and stored as a document under
the SYS Search Reports document type.
Note: If you are viewing a document that is locked by Records Management, the Annotations Toolbar
is also locked and cannot be used.
For information on creating annotations in the Web Client, see Creating Annotations on page 208.
You can easily navigate between the pages of a document by selecting a page in the pages toolbar.
Note: The Move Page To First option is disabled when a page is in the first position in the
existing sequence. The Move Page To Last option is disabled when a page is in the last
position in the existing sequence.
Tip: For complete details on revisions and renditions, see the EDM Services documentation.
For details on configuring user privileges and Document Types, see the System Administration
documentation.
To delete a page in a multi-page image document:
1. Hover the mouse pointer on the thumbnail of the page you want to delete and click the ellipsis
icon on the top-right corner of the thumbnail.
2. Select Delete Page. You are prompted to confirm this action.
Note: The comment field accommodates no more than 250 characters. Depending how revisions
are configured for your system, the comment field may be disabled.
Button Description
Cancel Cancels the revision and does not save the changes to
the document.
Note: When viewing OLE documents, this toolbar is only displayed when the Web Client is integrated
with a Microsoft Office Online Server or Office for the web (Office 365). For more information, see
your system administrator.
This toolbar provides you with many of the existing right-click menu options that are available for
image and text documents, since the OnBase right-click menu is not accessible when viewing these
documents.
Note: PDF and OLE documents are read-only when viewed within the Web Client.
The following menus and options are available in the PDF and Office document viewer toolbar:
Button Description
Process This menu contains options that apply to Workflow and WorkView. For
descriptions of these menu items, refer to the Workflow and WorkView help
files or module reference guides.
Previous Click the Previous Document button to navigate to the next document in the
Document list.
Next Document Click the Next Document button to navigate to the next document in the list.
Note: If an Office Business Application (OBA) is installed, you may be prompted to edit the document
in its native application.
Shortcut Action
Shortcut Action
Enter Starts the search or finds the next instance of the text if the search is in
progress.
Shortcut Action
Note: Shortcut keys do not work when the cursor is positioned over a thumbnail and Thumbnail
Zoom is enabled.
Note: These keyboard shortcuts are not available when viewing embedded OLE documents.
Shortcut Function
Page Up Quickly scrolls up the current page. At the beginning of a page in a multi-page
document, scrolls to the previous page.
Page Down Quickly scrolls down the current page. At the end of a page in a multi-page
document, scrolls to the next page.
Shortcut Function
Ctrl + N Display the Add Note dialog for the current document.
Note: This shortcut is not supported in Chrome.
Ctrl + Shift + N Display the View Notes dialog for the current document.
Note: This shortcut is not supported in Chrome.
1. From the open Document Viewer, right-click and select Delete Document.
2. Click Yes to confirm deletion.
3. The system then sends the document to the Trash Can.
Note: Once documents have been sent to the Trash Can, they can only be recovered by the user
who deleted them or by the system administrator.
Document Properties
You can display the Properties of all documents in the system, as long as you have the proper
privileges.
Property Description
Document Handle The document number assigned to the document when it was brought
into the system. This is the only place in the system where the internal
document handle for a document is displayed. The document handle
can be used to retrieve a specific document and to troubleshoot
problems with the document.
Batch Number The number of the batch in which the document was brought into the
system. A batch number is displayed if the document was brought into
the system through a process such as COLD.
Document Date The date used by the system to refer to the document. This date is
used during searches limited by date. The document date is assigned
to a document during import.
Note: If the has been open overnight, the system date and Document
Date may reflect the previous day's date. If this has occurred, close
and re-open the so that the correct Document Date is stored.
Archival Date The date on which the document was imported into the system. If
an invoice from December 28, 1996 was brought into the system on
March 11, 1997, December 28, 1996 is the document date and March
11, 1997 is the date stored. This date is used for internal tracking. You
cannot search for documents based on the date stored.
This field also contains the time at which the document was imported
into the system. You cannot search for documents based on the time
stored.
Document Type Number The internal number associated with documents of this Document
Type.
Document Type Name The name of the Document Type to which the document belongs.
Document Status Displays the document's position in the system. If the document is
retrievable, a status of 0 is displayed. If the document is in the system,
but not yet available for retrieval, a status of 1 is displayed. If the
document has been deleted, a status of 16 is displayed.
Document Type Revision Displays which revision of the Document Type the document is using.
Different Document Type revisions can have different configurations.
Revision If the document is revisable, the Revision field displays the latest
revision number of the document. For non-revisable documents, this
field is always set to 1.
Created By The name of the user who processed the document into the system.
Property Description
Page The internal page number for a document. Page numbers start at 0,
and are indicative of the number of files used to display the document.
Text documents typically have only one page, while image documents
typically have several. Virtual E-Forms have no pages, so on a Virtual
E-Form this field would display the tag <Virtual E-Form> instead of a
page number.
Disk Group The number associated with the Disk Group in which the document is
stored.
Volume The volume number in the Disk Group in which the file is stored.
# of Pages and # of Lines The characteristics of the document within the file. These values are
useful for text documents. Non-text documents display the number of
pages as 1 and the number of lines as 0.
File Format The number associated with a configured file format. This number
determines how a document is displayed and printed.
Item Offset and Item Size Describes the physical storage of the document within the file. The
Item Offset is the byte offset into the file for the starting point of this
particular document. The Item Size is the number of bytes in the file
that make up this document.
File Path Lists a partial path to the document. The beginning of the path
depends on the location configured for the document's Disk Group.
Note: Dates and times use the Windows regional settings for formatting.
Send To Options
From an open document or from the Document Search Results list, right-click and choose Send To
to display a sub-menu of document export options. You can also select a document in a Document
Search Results list, then select the Context Menu button in the upper-right corner and choose Send
To.
The options available for any particular document depend on the Document Type, your network
capabilities, which modules you are licensed to use, and the user rights granted to you by your
system administrator.
Display Considerations
For documents sent outside of OnBase(Send To | Clipboard, Mail Recipient, or File):
• An overlay is displayed on the sent or saved document only if the overlay is displayed by default
when you open the document in OnBase.
• Overlays are not displayed on documents sent with a content type of Native Format, Original
Format, or Text (.txt).
• Image document rotations are respected only if the rotation has been saved prior to sending.
Note: Depending on your user rights, the new document may not contain masked Keyword
Values from the original document. See the Encrypted Alpha Keywords module reference guide
or help file for more information.
In the Page range field, type the pages (e.g., 1,5) or range of pages (e.g., 1-5) you want to copy
to the new document. (This option is available for multi-page image documents only.)
• Send To | File: Select to save the document to a specified file.
• Send To | Envelope: Select to include the document in an envelope.
• Send To | Internal User: Select to send the document to another user in OnBase.
• Send To | Create DocPop Link: Select to email a link to the document that can be accessed by
recipients via DocPop.
• Send To | Copy DocPopLink: Select to copy a DocPop URL to the clipboard. You can browse to
a new window and paste the link into the subject line to open the document in DocPop.
• Send To | Create DocPop Link to Page: Select to email a link to the document that will open the
document to the page displayed in the viewer. The link allows the document to be accessed by
recipients via DocPop. This option is only available for text and image documents.
Note: If you rotate an image without saving the rotation before sending it to file, the rotation will
not be saved to the file.
Note: Depending on the file type of the selected document, not all of the following content types
may be available.
Option Description
Original Format or Saves or sends the selected documents in the format in which they are
Native Format stored in OnBase(for example, OLE documents such as Word documents
and PDFs, uncompressed text documents, most image documents).
The following limitations apply when using the Native Format option:
• Overlays are not applied.
• For multi-page image documents, including TIFFs and GIFs, this
option saves the document as a single-file TIFF file.
• This content type is only available if the selected documents can be
successfully saved or mailed in their original formats.
Rendered Format or Saves or sends each of the selected documents in the format that most
AutoDetect Format represents a viewable document outside of OnBase. For example, an E-
Form or Virtual E-Form is saved as an HTML file.
PDF (.pdf) Saves or sends the selected documents as PDF files. For multiple
documents selected, each document is converted to a separate PDF.
Available for documents with any of the following file formats:
• Image file format
• PCL
• PCL with overlay
• PDF
• Text report format
• Text report format with overlay
• XML with style sheet
Option Description
Encrypted PDF (.pdf) Sends the selected documents as encrypted PDF files. Each selected
document is encrypted as a separate PDF. Upon choosing this content
type, you will be prompted to enter a password, which the recipient will
need to enter upon opening the attachment.
Available for documents with any of the following file formats:
• Image file format
• PCL
• PCL with overlay
• Text report format
• Text report format with overlay
Text (.txt) Saves or sends the selected documents in plain text format.
Available for documents with a text report format.
Overlays are not applied.
HTML (.htm;.html) Saves or sends the selected documents in .htm or .html format.
Available for documents using HTML and MHTML (for example, E-Forms,
V-Forms).
3. If you selected a content type of Image (.tif), the following options are displayed:
Option Description
Annotation and/or Note Saves the document with any annotations and note icons displayed
Icon On Document on the document. If you move a note before saving the document, the
note is displayed in its last saved location. Note locations are saved
when a document is closed.
Note: When saved, annotations and icons are the same size as they
appear on the document when it is scaled to 100%.
Option Description
Note Text On Document Saves the document with the title and text of any notes in that note's
location on the document, along with the name of the user that
created the note and the date and time it was created. If this option
is selected with Annotation and/or Note Icon On Document, the
text is displayed below the icon. If you move a note before saving
the document, the note is displayed in its last saved location. Note
locations are saved when a document is closed.
Note: This option is not respected by Overlapped Text annotations.
4. If you are saving a PDF document from OnBase, the following option is displayed:
Option Description
Export Notes with Saves the document and converts any OnBase notes and annotations
Document on the document into Adobe Acrobat comments and drawing
markups.
5. If you selected a content type of Encrypted PDF (.pdf), you must enter a password to encrypt
the file.
6. Select the document pages you want to save.
Option Description
All Saves all pages. This is the only available option for documents
saved using the Send To | File option from the Document Search
Results list.
Note: The Auto-Name may be truncated to keep the file name below 256 characters. A Microsoft
limitation restricts the full path to a file to a maximum of 260 characters. For more information, see
http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx.
If the default Save As location already contains a file with a matching file name, OnBase
automatically appends the new file's name with an underscore and an incremental number. For
example, if Checking Statement Acct#1020 already exists in the default Save As location, OnBase
will name the new file Checking Statement Acct#1020_1.tif. See Character Substitutions on page
155 for more information.
Character Substitutions
Certain characters will be substituted in the file name upon saving. Substitutions are as follows:
\ and / -
: _
* +
? !
< [
> ]
“ _
| !
' _
; _
space _
Note: This functionality is only available if your Web Server solution is configured to use a secure
(HTTTPS) connection.
Option Description
3. Click OK.
Note: If the document is currently open in another browser session, a message displays
indicating that a new document cannot be created because the document is locked by another
user.
2. In the Page Range field, enter the pages or page range you want to include in the new document.
Note: The page range option is available for multi-page image documents only.
The page range option is available for multi-page image documents only. A specified page range
is required when creating a new document. You can type complex ranges, such as 1-2,5,8-11.
Tip: The new document will contain the pages you enter in the precise order that they were
entered. For example, if you enter 2-5,1 as your page range, the first page of the original
document will be the last page of the new document.
3. To delete the specified pages from the original document, select Delete copied pages from
original document.
Note: The Delete copied pages from original document option is not available if the original
document is a single page.
4. Index the new document by specifying the Document Type Group, Document Type, Document
Date, and any Keyword Values.
Depending on your user rights, the new document may not contain masked Keyword Values from
the original document. See the Encrypted Alpha Keywords documentation for more information.
5. If the Create as revision of original document option is available, select the option to create
the document as a revision to the original source document. When this option is enabled, the
Document Type and Keywords are reset to the source document and cannot be modified. This
option is available if all of the following are true:
• The OnBase solution is licensed for EDM Services.
• The source Document Type is revisable.
• You have the proper privileges to create revisions.
Select the appropriate Save option, and then click Save. The document is displayed on the
screen.
Note: You cannot reorder pages on a read-only document. If you attempt to do so, the system
informs you that the document is read-only and cannot be modified.
Note: You cannot delete pages from a read-only document. The Delete Page option is unavailable if
the document is read-only.
2. Select the Suppress Blank Pages check box. Clear the check box if you want the blank pages to
remain in the Pages toolbar.
3. Click OK to save your changes. OnBase immediately changes the display of the thumbnails in the
viewer based on whether or not the Suppress Blank Pages option is enabled or disabled.
Navigate
Navigate is a feature available for multi-page text and image documents. You can access the
Navigate options by right-clicking anywhere in the open document and selecting Navigate.
Option Description
Go To Page Select Go To Page and type the page number of the page you want
to display.
Note: You can also access the Go To Page dialog by double-
clicking the Page X of Y section of the status bar.
Scale
The Scale feature provides options for viewing documents.
Option Description
Actual Size Displays the document without any viewer scaling (i.e., in the same
aspect ratio in which it was acquired).
Fit Width Scales the display of the current page in the viewer as adjusted per the
maximum width of the page in the viewer.
Fit Height Scales the display of the current page in the viewer as adjusted per the
maximum height of the page in the viewer.
Fit in Window Scales the display of the current page in the viewer according to the
maximum viewer area.
Zoom In Zoom Out Magnifies (Zoom In) or reduces (Zoom Out) the displayed area of the
image in the viewer.
True Size Displays the image at its original size (monitor DPI divided by image DPI
when rendering at 100%).
For example, if you scanned a 3" x 3" paper document into OnBase, the
document displayed at True Size would occupy 3" x 3" of screen space.
Note: Digital images, such as GIF and ICO files, can have undefined
DPIs. For images whose DPIs are undefined, the True Size option uses a
default image DPI of 200.
Process
There are several process options available when viewing documents.
1. From an open document, right-click and select Process.
2. Select one of the process options described in the following table:
Option Description
Rotate All Pages 180 Rotates all pages of the document 180 degrees from their current
positions.
Note: This option is only available for image documents.
Invert Reverses the colors in the color palette. For example, black pixels
become white and white pixels become black.
A document is inverted only for the duration of its viewing session.
When the document is closed, it resumes its default color properties.
Selecting Save Rotation does not save the inverted document.
3. Right-click and select Process | Save Rotation to save the rotation. A confirmation message is
displayed.
Note: Clicking Save Rotation saves each individual page of the document with any rotations that
have been applied to it.
If you haven't selected the User Option Rotate Auto-Save in the OnBase Client or Web Client,
and you don't select Save Rotation, the document retains the rotation for the current viewing
session and resumes its default display properties upon closing. The document is displayed with
its default properties the next time the document is opened.
From the Add/Modify Keywords dialog box, you can view or edit Keyword Values, depending on your
assigned privileges and the Document Type of the document. Some Document Types are configured
to disallow editing of Keyword Values, which renders a document's Keyword Values read-only.
Note: When editing keyword values that are displayed automatically on an opened document, it may
be necessary to close and reopen the document to correctly auto-display those values.
The title line of the Add/Modify Keywords dialog box displays information about the document. The
first two lines display the Document Type and document name respectively.
Note: If this document is checked out by another user, the Keyword Values will not be able to be
modified regardless of privileges. The Add / Modify Keywords dialog box will be displayed, but all
Keyword Values will be read-only.
Note: You cannot change Keyword Values on E-Forms that have been signed. When a form is signed,
the Add/Modify Keyword dialog box becomes read-only and the re-index menu option is disabled for
the form.
Document Date
The Document Date field displays the date the system matches in a search for documents based on
a date or date range. You can change the date.
Dates use the Windows Regional Settings for formatting.
Keywords
The Keywords section displays the Keyword Types and Keyword Values currently associated with the
document. The Keyword Value is blank if no Keyword Value is currently assigned.
You can use the Add / Modify Keywords dialog box to remove, change, or add a Keyword Value:
• To remove a Keyword Value from a document, delete the contents in the Keyword Type field.
• To change the value, edit the Keyword Value currently residing in the Keyword Type field
• To add another value for a Keyword Type, place the cursor in the Keyword Type field and press
F6, or click the Keyword Type name. An additional field is displayed for the Keyword Type. Fill in
the additional Keyword Value.
You cannot duplicate Keyword Types in Single-Instance Keyword Type Groups or Cascading Data
Sets.
If you duplicate a Keyword Type within a Multi-Instance Keyword Type Group, another instance of the
entire Multi-Instance Keyword Type Group will be added, not just the Keyword Type. This is because
all Keyword Types within the Multi-Instance Keyword Type Group are part of a record. When you
choose to duplicate the Keyword Type, you must duplicate the entire record.
It is recommended that all Keyword Type Values are indexed when a Multi-Instance Keyword Type
Group is duplicated, even if only one Keyword Value is different between the original Keyword Type
Group and additional instances.
A calendar button is available next to date-based Keyword Types, allowing you to select a date from
a calendar. A drop-down arrow may be available for some alphanumeric Keyword Types, allowing you
to select a value from the Keyword Values in the list.
If a security mask is applied to one of the Keyword Types and you have the Access Security
Masked Keywords privilege, the View Security Masked Keyword toggle button is available.
• To view security masked Keyword values without the security mask, click:
• To view security masked Keyword values with the security mask, click:
Note: In some instances, changing Keyword Values will affect the appearance of your document.
Change Keyword Values carefully.
Note: When editing keyword values that are displayed automatically on an opened document, it may
be necessary to close and reopen the document to correctly auto-display those values.
3. When finished, click Save to exit and save changes, or click Cancel to exit without saving
changes.
Note: You will be unable to modify Keyword Values if the Document Type is configured to Disable
Keyword Editing, if the Keyword Values are locked by another user, or if you have insufficient
privileges. Under these conditions, the values will be shown as read-only text (instead of editable
field values), and the Save button will be disabled.
Masked Keywords
Masked Keyword Types must have values entered in a specific format, called a mask format. Fields
for masked Keyword Types prohibit you from typing values that do not satisfy the mask format.
For example, a masked Keyword Type for Social Security Numbers may contain dashes as
static characters and allow users to enter only nine numeric characters. The dashes are entered
automatically as the subsequent characters are typed.
Depending on your system's configuration, a mask may also be applied to certain Keyword Values
upon retrieval.
In the Keyword Panels for retrieving, importing, indexing, and re-indexing documents, the mask
format is displayed below the Keyword Type field, as shown in the following example:
Mask formats are composed of characters that represent the types of characters accepted in a valid
Keyword Value. Use the following table to determine what types of characters you must enter to
satisfy a mask format for a masked Keyword Type.
Any other character Accepts only the character displayed in the mask format. For
example, if the mask format is 000-00-0000, then a dash must be
entered for the fourth and seventh characters; all other characters
must be numeric.
Blank spaces may also be used. For example, if the mask format is
0 000, then the second character must be a space.
The Web Client automatically enters these static characters for
you as you type subsequent characters, so you do not need to type
them manually. If a static character is at the end of a mask format,
the Web Client enters it automatically when you type the second-to-
last character.
• The User Group that you belong to does not have the right to Modify Keyword Values. The Add/
Modify Keywords dialog box displays in read-only mode:
• When you elect to view Keyword Values on a document, OnBase displays a message that
someone has the document checked out, or locked. The Add/Modify Keywords dialog box
displays in read-only mode. Depending on your system setup, this happens if a document is
checked out by another user, or if it is persistently checked out.
Note: When you open Add/Modify Keywords or the Re-Index Document dialog box, the document
is locked for your use so you can modify Keyword Values and save the changes. The document is
unlocked when the dialog box is closed. When another user attempts to Add/Modify Keyword Values
or re-index and a document is locked, the user can view the Keyword Values, but not modify them.
Your system administrator configures Document Types with Keyword Types and Keyword Type
Groups.
5. You can verify if the Keyword Set Configuration permits multiple sets by checking the Settings.
In the Configuration Module, select Keyword | AutoFill Keyword Sets, select the AutoFill
Keyword Set you want to verify and click Settings.
Note: Your User Group must have rights to that AutoFill Keyword Set to have access to it in the
AutoFill Keyword Sets Configuration dialog box.
The Allow Multiple Keyword Set Selection will be checked if the AutoFill Keyword Set is
configured to allow for more than one set of AutoFill Keyword set values for one Primary
Keyword Value. This setting can be changed once the AutoFill Keyword Set has been created.
6. When all fields are populated, click Import.
Note: If you change the Primary Keyword Value and press Tab, all Secondary Keyword Values are
updated to reflect the new Primary Keyword Value. If you create another Primary Keyword Type
field and enter a second Primary Keyword Value, OnBase adds another set of values associated
with the second Primary Keyword Value while retaining the values associated with the first
Primary Keyword Value.
Note: Every workstation that will be accessing External AutoFill Keyword Sets must have an
ODBC connection that has the same name as the one configured in the Configuration module.
See your system administrator for details. In the case of Web Server, only the Web Server itself
must have the ODBC connection, not the client workstations.
CAUTION: AutoFill Keyword Sets may unexpectedly re-populate Secondary Keyword Values when
re-indexing to a Document Type associated with the same Keyword Type Group (KTG) or Multi-
Instance Keyword Type Group (MIKTG) as the current Document Type. For more information, see
Considerations for Re-Indexing Documents and Adding or Modifying Keyword Values on page
182.
3. Select the Document Date using the Calendar or by entering a date in the field.
4. If necessary, modify the Keyword Values on the document:
Changing the Primary Keyword Value to another Primary associated with the AutoFill
Keyword Set: If this occurs, all Secondary Keyword Values are updated to reflect the values
associated with the new Primary Keyword Value.
To avoid undesired Keyword Value changes, click on any field in the dialog box before clicking
the Re-Index button. This will trigger the AutoFill Keyword Set and allows the user to review any
changes made to the Secondary Keyword Values before re-indexing the document.
If more than one AutoFill Keyword Set is associated with the same Primary Keyword Value:
Multiple AutoFill Keyword Sets are displayed in a selection box after the Primary Keyword Value
is entered. Depending on how your system is configured, you may be able to select one AutoFill
Keyword Set or you may be able to select multiple AutoFill Keyword Sets.
If you are only permitted to select one AutoFill Keyword Set, the Keyword Values associated with
the AutoFill Keyword Set populate the Keyword Type fields.
If you are permitted to select more than one AutoFill Keyword Set, the document is indexed with
Keyword Values from all AutoFill Keyword Sets. Only one instance of a Keyword Value common
to both sets is displayed. Additional instances of Keyword Types are added to hold Keyword
Values not common to both AutoFill Keyword Sets.
5. Add Keyword Values to any Keyword Types that are not associated with the previous Document
Type but are associated with the new Document Type.
6. Click Re-Index.
Once the document has been re-indexed, it no longer exists in the database as the original
document, and can only be retrieved using the new Document Type and any new Keyword Values.
Note: You cannot add additional instances of Keyword Types that are part of a Single-Instance
Keyword Type Group or a Cascading Data Set.
Note: When documents are indexed with multiple instances of the same Keyword Type, multiple
results for the same document can be returned in a Document Search Results list. This occurs
because of the way that OnBase searches for multiple Keyword Values.
Operator Description
<> Keyword Values that are not equal to the specified value.
> Keyword Values that are greater than the specified value.
>= Keyword Values that are greater than or equal to the specified value.
< Keyword Values that are less than the specified value.
<= Keyword Values that are less than or equal to the specified value.
" The string literal operator (double quote) used with alphanumeric Keyword Types.
Selecting this button will match the literal string. If a wildcard is used in the string,
the search will look for the exact match, including the wildcard treated as a standard
character.
Note: Available operators vary depending on the Keyword Type. For example, only the =, <>, and "
operators are available for alphanumeric Keyword Types.
Operator Description
And Searches for documents containing the Keyword Values preceding and following the
logical operator.
Or Searches for documents containing either the value preceding the logical operator or
the value following the logical operator.
To Searches for all values that are between the two values (i.e., that are greater than or
equal to the first value and less than or equal to the second value). This operator is
unavailable for alphanumeric Keyword Types.
Note: When you use the Or operator and one document has both Keyword Values, OnBase retrieves
two separate records for that document. For example, you perform a search for the Keyword Values
Sarah Adams Or John Adams. If the same document has both values associated with it, then
OnBase displays a record for each occurrence of the Keyword Value (one record for Sarah Adams,
one record for John Adams).
If you have more than two Keyword Values for the same Keyword Type, then the logical operators are
processed in order of occurrence.
Wildcard Characters
A wildcard character can be used to match Keyword Values where one or more characters are
unknown. Wildcards can only be used to match alphanumeric Keyword Values.
Note: Depending on your system's configuration, some alphanumeric Keyword Types may not allow
wildcard characters to be used, or searches that include wildcards may return unexpected results.
Type one of the following wildcard characters directly into the Keyword Type field to search for text
strings containing one or more unspecified characters:
Wildcard Description
Re-indexing
Re-indexing provides the ability to change Keyword Values, Document Date, and Document Type.
Re-Indexing Documents
Each document stored in OnBase has an associated Document Type, Document Date, and optional
Keyword Types. This information is usually entered when a document is first imported into OnBase
upon indexing.
You can change this associated information using the Re-Index feature.
Note: Ensure you understand the effects of re-indexing documents before proceeding. For more
information, see Considerations for Re-Indexing Documents and Adding or Modifying Keyword Values
on page 182.
1. Save any changes that you have made to a document before re-indexing.
2. Perform one of the following actions to open the Re-Index Document dialog box.:
• From an open document or from a Document Search Results list, right-click and select Re-
Index.
• From a Document Search Results list, click the Context Menu button in the upper-right
corner and select Re-Index.
Note: If the original Document Type contains a Multi-Instance Keyword Type Group, the
Document Type to which you want to re-index must contain the same Multi-Instance Keyword
Type Group.
3. Select a Document Type from the Document Type drop-down list. All Document Types that you
have rights to create are displayed.
If the destination Document Type is configured to use Default Keyword Values, these Keyword
Values are assigned to the document when the destination Document Type is selected from the
Document Type drop-down list.
Note: If you select a different Document Type at any point during the re-indexing process,
Keyword Values for common Keyword Types are retained. For example, if there is a value for
the City Keyword Type, and you switch to a different Document Type that also contains the City
Keyword Type, the original City Keyword Value is retained. This also applies to Keyword Types
configured to use Default Keyword Values on the initial Document Type. These values are not
replaced, even if the new Document Type uses a different set of Default Keyword Values.
CAUTION: If you are re-indexing a document associated with a Keyword Type Group (KTG)
or Multi-Instance Keyword Type Group (MIKTG) filled by an AutoFill Keyword Set to another
Document Type associated with the same KTG or MIKTG filled by an AutoFill Keyword Set,
the AutoFill Keyword Set may unexpectedly re-populate secondary Keyword Values once
the Document Type is changed. For more information, see Considerations for Re-Indexing
Documents and Adding or Modifying Keyword Values on page 182.
4. Change the File Type, if needed.
• Select another file format available from the File Type drop-down list.
• You can easily change the file format by re-indexing the document instead of re-scanning or
re-importing it to OnBase with the corrected file format.
• File formats available for Re-Indexing depend on your system setup and the file format itself
(certain file formats are only available through document processes or system functions.)
CAUTION: Contact your system administrator before selecting the Image Rendered PDF
file format, as selecting this file format without the proper system specifications can cause
unexpected behavior.
5. Change the Document Date, if needed. If a document date is not specified when the document is
processed into OnBase, the Document Date is the same as the Date Stored.
Click the Calendar icon next to the Document Date to select a date.
6. Depending on your system configuration, the Initiate Workflow check box may be displayed.
If this check box is selected, a Workflow event is triggered if the creation of a document of this
Document Type is configured to trigger a Workflow process. If this check box is not selected, a
Workflow process is not triggered even if the creation of a document of this Document Type is
configured to trigger a Workflow event.
7. Change Keyword Values as desired. You can use the Tab key to move to the next Keyword Value
field. Note the following:
• Some Keyword Types may be configured to be uppercase only, while others may be
configured to appear in mixed or lowercase.
• Depending on your system's configuration, certain Keyword Types may appear as read-only
in the Re-Index Document dialog box to certain users. These Keyword Types may also be
masked.
• OnBase will not retain two sets of duplicate Keyword Values. For example, a Document Type
contains two instances of the Keyword Type First Name, and one value is John and the other
value is Sarah. If you change the value of Sarah to John, upon clicking Re-Index, OnBase will
only retain one instance of John. If two Multi-Instance Keyword Type Groups share identical
values, only one of those Multi-Instance Keyword Type Groups is retained.
CAUTION: After changing Keyword Values, click on any field in the dialog box before you click
the Index button. This will trigger any AutoFill Keyword Sets that may have been affected by the
Keyword Value change. See your system administrator for information regarding your system's
AutoFill Keyword Set configuration. Click Exit to cancel changes if you get undesired results.
8. To add a new Keyword Type field of the same Keyword Type to the document, place the cursor
inside the Keyword Type field that you want to duplicate and press F6. This adds a new Keyword
Type field. Enter the new Keyword Value.
If the Keyword Type that you duplicate belongs to a Keyword Type group, then it can only be
duplicated if the group is a Multi-Instance Keyword Type Group. The entire group is duplicated,
not just the selected Keyword Type.
9. Press Clear Keywords if you want to clear all existing Keyword Values and re-enter new values.
10. Click Re-Index to save your changes and re-index the document. Click Close to cancel changes.
Note: Review changes carefully before saving. Once re-indexed, documents can be retrieved
using only the new Keyword Values.
Note: You can also change Keyword Values by right-clicking the document, selecting Keywords,
and entering new Keyword Values in the appropriate fields. Re-indexing allows you to change the
Document Type in addition to Keyword Values.
Note: The F5 function is only available for Keyword Types that are configured to use a drop-down
menu.
If two or more consecutive Keyword Types contain drop-down lists and are ordered in such a way as
to show a hierarchical parent/child relationship, the Keyword Types may be part of a Cascading Data
Set. Selecting a Keyword Value from the parent drop-down list filters the available Keyword Values
from the subsequent child drop-down list. To show all of the available values in a Cascading Data
Set, hold the Ctrl key and click the drop-down arrow.
Note: Changing the Primary Keyword Type Value prior to changing the Document Type will
prevent the AutoFill Keyword Set from re-populating Secondary Keyword Type Values after a new
Document Type is chosen, because the AutoFill Keyword Set is not triggered by the modified
Primary Keyword Value, unless the modified Primary Keyword Value is also a Primary Keyword
Value in an AutoFill Keyword Set associated with the new Document Type. Then, the modified
Primary Keyword Value would cause the existing Secondary Keyword Values to be replaced by
the associated Secondary Keyword Values.
Note: This only affects Keyword Type Groups or Multi-Instance Keyword Type Groups. Individual
AutoFilled Keyword Types will retain any modified, individual, AutoFilled Keyword Values when
a document is re-indexed, even if values from Keyword Type Groups or Multi-Instance Keyword
Type Groups are overwritten on the same document.
• Require Changes to Child Values in a Cascading Data Set
A Cascading Data Set is an indexing feature that defines parent/child relationships between
drop-down Keyword Values available on a document or folder. Changing a parent Keyword Value
in a Cascading Data Set will not update the child Keyword Values that depend on it. For example,
suppose a document is indexed with a selected State and County, where the County Keyword
Value is a child to the selected State Keyword Value. If you change the State Keyword Value, then
the County will retain its original value and will not be updated to reflect the new State.
• Trigger Auto-Foldering
If you re-index a document that is configured for auto-foldering, it will trigger an auto-foldering
process.
• Alter the contents of Dynamic folders
Because Dynamic Folders contain documents according to their Keyword Value, re-indexing a
document or adding or modifying Keyword Values may dynamically move the document from its
current folder to another folder.
• Affect the appearance of your document
The appearance of an XML file format document may change if you add or modify the Keyword
Values or re-index the document. Your system administrator determines whether the document's
appearance is dependent on Keyword Values.
• Affect Workflow
Keyword Values can affect Load Balancing and certain Workflow actions, such as Set Related
Document's Keyword Equal to This Document's Keyword. See the Workflow module reference
guide or help files for details.
Note: Re-indexing a document or adding or modifying Keyword Values may trigger different
results depending upon the Workflow action.
• Notes and Annotations
When re-indexing a revisable document with notes or annotations, the notes or annotations are
not transferred to the next revision. The notes or annotations are only retained on the original
document.
Importing Documents
If configured, you can use the application to upload documents into the system.
Document import consists of a two-stage process. Users either browse to a file location and select
a file to import, or users can drag and drop a file onto the document import screen. The document
is held in an imported Document Queue while Document Type and Keyword information is added.
Once the necessary information is entered, the document can be imported. Depending on your
configuration settings, you can also preview image files for easier indexing.
To import documents:
1. Select the Upload Document type of action configured for your application.
3. Select the Show Preview option to preview the document being imported. Only previews of
image files are displayed. Previews are not displayed for PDF documents larger than 100 MB.
Note: This option is only available if it has been configured by your system administrator.
4. Select the Initiate Workflow option to add this new document to Workflow.
Note: This option is only available if your system is licensed for Workflow, the Document Type is
part of an existing life cycle, and the Document Type is not configured to automatically initiate
Workflow when a document is imported.
5. From the Document Type drop-down list, select the Document Type to assign the document to.
(The list includes all Document Types configured for import by your system administrator.)
6. If a file type has not already been selected, select the appropriate type from the File Type drop-
down list.
Note: If OnBase can correlate the file extension to a file type (format), it will automatically select
that file type in the File Type field. For example, if you import a file whose extension is .doc,
OnBase will select Microsoft Word document (.doc).
Note the following:
• Depending on your system configuration, only certain file types may be available.
CAUTION: Contact your system administrator before selecting the Image Rendered PDF
file format, as selecting this file format without the proper system specifications can cause
unexpected behavior.
7. Select the Document Date. To retain the selected date for future uploads, click the lock button
next to the calendar. The selected date is retained until you click the lock button again to unlock
it, or until you log off of OnBase.
8. Type Keyword Values in the Keyword Type fields. Note the following:
• Depending on your system's configuration, some values may be provided by default. Other
Keyword Types may be configured as read-only, preventing you from indexing the document
with a value for that Keyword Type. If the Keyword Type name is displayed in red, a Keyword
Value is required.
• If you select a different Document Type during import, entered Keyword Values for common
Keyword Types are retained. For example, you enter a Keyword Value for the City Keyword
Type and switch to a different Document Type also containing the City Keyword Type. The
entered City Keyword Value is retained. This logic does not apply to Default Keyword Values.
Default values for common Keyword Types are either updated or cleared when selecting a
different Document Type during import, depending on whether the selected Document Type
has default values for those Keyword Types.
Note: You can include special characters (such as ñ, å, etc.) in Keyword Values.
9. If you make a mistake, use the following buttons available at the bottom of the Import
Document pane to clear the current indexing values.
Button Description
Clear Imported Documents: Click to clear the list of imported documents in the
Document Queue.
Clear All: Click to reset all indexing fields except for the file name, which retains the
name of the file.
10. Click the Import button in the toolbar at the bottom of the panel. The App Builder imports the
document to OnBase. If more information is needed to complete the import, a message displays
the appropriate instructions.
• Depending on how the Document Type is configured, or if the imported document is a
revision you may be prompted to enter a comment.
• When the import is complete, a confirmation message is displayed next to the document in
the Document Queue.
Note: Before importing the document, OnBase checks its file size against the maximum size
allowed for imports. If the document is too large, you are notified that the import failed.
If you receive an Import Failed message, contact your system administrator.
Note: You can view notes on an OLE document (such as a Microsoft Office document or PDF) in the
Notes pane in the Document Viewer. See Notes Pane Viewer for OLE Documents on page 202. To
add, edit, or delete notes on an OLE document, you must use the Notes dialog box. See Notes Dialog
Box on page 194.
CAUTION: If a note, redaction, burned markup, or deficiency is not in the location you expect, do not
save or sign the document until the location has been corrected by your system administrator. When
the document is saved or signed, the pending redaction, burned markup, or deficiency is permanently
placed in the shifted location. The shifting of notes that do not permanently alter the document can
be corrected any time by your system administrator.
Notes Overview
Digital notes can be placed on documents and can be used for many purposes, including the
following:
• Emphasizing specific content within the document
• Clarifying or explaining items in a document
The characteristics of different Note Types are defined by your system administrator:
• Some notes may be configured to hide by default. To view any hidden notes, you can display a
list of all notes on the document and open any notes from the list.
• Depending on your system setup and user privileges, you may be able to view, modify, delete or
add notes to a Document Type, as well as set privacy options.
• You can type text in notes and search for note text in Document Retrieval or Custom Queries.
Some notes are configured with default text that is also searchable using Document Retrieval or
Custom Queries.
• Typically, notes are configured to show an Auto-Name string in the title bar, identifying the type
of note when it is placed on a document. Other typical items in an Auto-Name string are note
creation date and time and the name of the user who created the note.
Note: Any time or date in the note Auto-Name string (the top line of the note header) respects the
Windows Region and Language settings of the user applying the note at the time the note is added.
The time and date in the second line of the note header respect the Windows Region and Language
settings of the user currently viewing the note.
Note Icons
Depending on the Note Type configuration and the Document Type, the note may display as an icon,
indicating the type of note, such as a Received stamp.
Note: Note icons can only be displayed on image and text documents.
Options
The Options button on the Viewer Control toolbar allows you to choose whether note icons and
annotations are displayed while you're viewing a document.
Viewing Notes
You can view notes or annotations using any of the following methods:
• Right-click a document in the Document Search Results list and click Notes.
• Select a document in the Document Search Results list, then click the Context Menu button in
the upper-right corner and select Notes.
• Double-click the note's icon from the Document Viewer.
• Right-click an open document and select Notes | View Notes.
• Double-click the note in the Notes List toolbar.
• Double-click the Note(s) section or the Highlight(s) section of the status bar.
If a note or annotation exists on a document, it is listed in the Select Note dialog box.
The list includes the page where the note is found, the note type, the text of the note, and the date the
note was created. Click on the column headings to sort the notes by that column.
Open a note by either selecting the note in the Select Notes dialog box and clicking OK, or by double-
clicking the note in the Select Note list.
Note: Depending on your system's configuration, you may be unable to open certain notes in the
Select Note dialog box. See your system administrator if you have any questions.
Moving Notes
To move a note, click and drag the note icon on the document. Release the mouse button when you
have moved the note to its new position. The new position is saved automatically.
Note: If you have privileges to create a note but do not have privileges to modify it, you can modify
the note's text and position only during the same viewing session that you created the note. After you
close the document, the note's text becomes read-only. You can reposition the note while viewing the
document, but the note will return to its original position when you close the document.
Take note of the following when working with notes and annotations:
• Notes and annotations may contain messages that can be displayed and edited. If you have
appropriate privileges, you can delete both notes and annotations from the Notes right-click
menu.
• Annotations are created using the Annotations toolbar. To add an annotation to a document, see
the procedure for creating annotations.
Add a Note
Users with privileges to create notes can add new notes to documents from the Add Note dialog
box. Users can only add notes of the type(s) that his or her User Group(s) has rights to create.
To create a note:
1. Right-click on the document and select Note | Add Note, or press Ctrl + N. The Add Note dialog
box lists the available Note Types.
3. Edit or type a message in the note's text box. Notes are limited to 250 characters.
• To minimize a note on an HTML document, double-click the note's title bar. The note's icon is
displayed while the note is minimized. To view the note's text, double-click the note's icon.
• To delete a note from an HTML document, click the X in the note's title bar. Click Yes to verify
that you want to delete the note.
• To change the note type, right-click the note and select Change Note Type. Select a new
note type for the note.
Note: If you are unable to access the text box, you may not have user rights to edit the note.
• Undo- select to undo the last typed action
• Cut- removes selected text and place it on the clipboard
• Copy- retains selected text, but place it on the clipboard
• Paste- inserts clipboard text in to the active area (last place the mouse was clicked)
• Delete- deletes selected text
• Select All- selects all text (including default note text)
Note: Changes to notes and annotations are saved automatically. Notes that are moved off of the
document revert to their last saved position.
Some options may be unavailable depending on how the Note Type was set up by a system
administrator.
2. Select one of the following options to restrict other users from performing the corresponding
action.
Disallow View Selecting this check box disallows users from viewing the note.
Disallow Update Selecting this check box disallows users from updating information on
the note.
Disallow Delete Selecting this check box disallows users from deleting the note.
Deleting a Note
Click Yes when prompted to confirm.
Note: You cannot delete an existing note on a locked document. See your system administrator for
information regarding Document Lock Administration.
Note: The Change Note Type option in the Notes List toolbar is only available when the page the
note belongs to is displayed in the Document Viewer. For example, the option is not available if page
1 is displayed, and the note you right-click is on page 2.
Select the new type of note from the Change Note Type dialog box and click OK.
bar or in the heading of the Notes pane in the Document Viewer. See Notes Pane Viewer for OLE
Documents on page 202 for more information on viewing notes on OLE documents.
Note: If you have privileges to create a note but do not have privileges to modify it, you can modify
the note's text only during the same viewing session that you created the note. After you close the
document, the note's text becomes read-only.
Click Hide Document to hide the document and show only the notes in the dialog box.
Note the following limitations with viewing a document alongside notes in the Notes dialog box:
• Notes can only be added to the first page of a multi-page document in the Notes dialog box.
• Annotations cannot be drawn on a document being viewed in the Notes dialog box.
To accomplish any of these actions, perform them in the Document Viewer, not in the Notes dialog
box.
2. Select a note to view any note text in the Note Text box.
2. Select a note type from the Note Type drop-down list, and click Add. The new note is added to
the Notes list. If the note type is configured to include default text, it is displayed in the Note
Text field.
3. Enter or modify the text of the note in the Note Text field. The character counter displays the
remaining characters allowed in the note.
4. Select the privacy options to enable or disable for the selected note. The following privacy
options are located below the Note Text field:
Disallow View Prohibits all other users from viewing the note.
Note: If this option is selected, other users can still successfully search
for text in the note using the OnBase Client, but they will not be able to
view the note.
Disallow Update Prohibits all other users from editing the note.
Disallow Delete Prohibits all other users from deleting the note.
Note: Depending on the configuration of the note type, you may be unable to modify some
privacy options. For more information on note privacy options, see Setting Note Privacy Options
on page 201.
5. Click Save to save the note to the document and keep the Notes dialog box open, or click Save
and Close to save the note and close the Notes dialog box.
Note: If you delete a Staple note from the Notes list on one document, the corresponding staple
that was attached to the deleted staple is still displayed on the other corresponding document. If
you do not want the staple on the corresponding document, you must delete it also.
2. Select the note that you want to modify from the Notes list.
3. Select the privacy options to enable or disable for the selected note. The privacy options are
located below the Note Text field. The following privacy options are available:
Disallow View Prohibits all other users from viewing the note.
Note: If this option is selected, other users can still successfully search
for text in the note using the OnBase Client, but they will not be able to
view the note.
Disallow Update Prohibits all other users from editing the note.
Disallow Delete Prohibits all other users from deleting the note.
4. Click Save to save the note to the document and keep the Notes dialog box open, or Save and
Close to save the note and close the Notes dialog box.
The Notes pane displays all of the notes on the document, and each note's color is displayed next to
the name of the Note Type. The total number of notes is also displayed in the heading of the pane.
Note: The Notes pane only allows you to view the notes on the OLE document. To add, edit, or delete
notes, you must use the Notes dialog box by clicking Edit on a note in the Notes pane, or clicking
the Note(s) section of the status bar. For more information on using the Notes dialog box, see Notes
Dialog Box on page 194.
The following functions are available in the Notes pane of the Document Viewer:
• To expand a note and view its contents, click the note in the Notes pane. Click the heading of the
note again to collapse the note.
• To view additional information on a note, expand it and then click More. The note's icon, creation
date and time, and creator's user name are displayed.
• To edit a note, expand the note and click Edit. The Notes dialog box is displayed, which allows
you to edit the note.
• To add a new note, click the Add Note button at the top of the Notes pane. The Notes dialog box
is displayed, which allows you to create a new note.
• To expand all notes, click the Expand All button at the top of the Notes pane. Click the button
again to collapse all notes.
• To filter the list of notes, click the filter button at the top of the Notes pane and enter search
terms into the Note Text field. The list is filtered to display only the notes that contain matching
text. Click the red X to remove the filter.
• To hide the Notes pane, click the handle next to the pane.
• If any notes have specific positions on a PDF document, the Notes pane contains a notice
explaining that the document viewer cannot display the position of these notes on the PDF. To
display the positions of notes and note icons on a PDF document, use the Web Client PDF viewer
instead of the web browser's PDF viewer. See your system administrator for more information.
Annotations
Annotations are similar to OnBase notes. An annotation can be used to call attention to items in a
document, it can contain a message, and it may be represented by an icon. However, annotations
also allow you to call attention to a portion of the document with special markings, such as arrows,
highlights, and ellipses.
Note: If you are viewing a document that has been locked by Records Management, the Annotations
toolbar is locked and cannot be used.
Characteristics such as color and title are predefined when the note is configured for use. Several
types of annotations can be created:
• Arrows typically point to a specific item.
• Ellipses typically circle an area of interest.
• Overlapping Text allows user-defined text to be displayed over the document.
• Highlights place a translucent color over the area of interest.
Redaction annotations can be used to produce an entirely new image document, in which the
annotation is permanently applied to the document.
Note: The Arrow, Ellipse, and Overlapped Text note types are not available for use on all documents.
Availability depends on the file format of the document.
Annotations Toolbar
The Annotations toolbar provides buttons for adding annotations or redactions to a document. You
can show or hide the Annotations toolbar; by default it may be hidden.
Note: If you are viewing a document that is locked by Records Management, the options on the
Annotations Toolbar are selectable, but do not perform any tasks.
You can view, modify, or delete annotations the same way you do notes.
Button Description
Toggle Redaction lets you draw black or white rectangles over a portion of the document.
The color of the redaction is determined by the adjacent drop-down list. You remain in
redaction creation mode until you click the Toggle Redaction button again.
This option is available for image documents only. You must have sufficient privileges to
modify the document.
Save Redactions saves any redactions that you have added to the document but not yet
saved.
You can save redactions only if the following requirements are met:
• You have sufficient privileges to modify the current document.
• The document is configured to allow redactions.
• The document has an image or text report format.
Toggle Annotation enables you to add one or more annotations to the document by
selecting the annotation(s) from the adjacent drop-down list of available annotation types.
You remain in annotation addition mode until you click the Toggle Annotation button
again.
Note: Not all File Formats allow annotations. See your system administrator if the Toolbars |
Annotations right-click option is not available.
Creating Annotations
If you have sufficient privileges, you can create annotations on text and image documents.
To create and place an annotation on a text or image document:
1. In the Document Viewer toolbar, select the type of annotation from the drop-down list:
3. Using your mouse pointer, define the location and size of the annotation by clicking and
dragging the pointer over the document. Release the mouse button when finished to display the
annotation.
Note: Ensure that the annotation is large enough to be visible. Annotations are required to be a
certain size before they can be created and saved.
Tip: When using the arrow keys on the keyboard to move an annotation, press and hold the Ctrl key
while pressing the arrow keys to move the note more quickly.
To resize an annotation on a document, do the following:
1. In the Document Viewer, double-click the annotation you want to resize. The annotation is
selected.
2. Click and drag the edges or corners of the annotation until the annotation is the correct size. The
mouse pointer changes to indicate the direction in which the annotation can be resized.
3. When you are finished resizing the annotation, click a different area of the screen to deselect the
annotation.
Redactions
A redaction is a special kind of annotation used to hide confidential information on an image or
text document. A redaction is a permanent black or white rectangle that obscures an area of the
document.
Redactions can be created and saved on image documents, text documents, and Image Rendered
PDFs that are part of Document Types configured to allow redactions. See your system administrator
to verify whether a Document Type has been configured for redactions.
A redaction cannot be deleted (or undone) once it has been saved. When a redaction is saved,
the redacted document is stored either as a new document in another Document Type or as a
revision of the current document. How the redacted document is stored depends on your system's
configuration.
Note: Depending on your system's configuration, redaction annotations may be available from the
annotations drop-down list. These annotations are supported only in the OnBase Client and Unity
Client and should not be used for creating permanent redactions in the Web Client.
CAUTION: If a note, redaction, burned markup, or deficiency is not in the location you expect, do not
save or sign the document until the location has been corrected by your system administrator. When
the document is saved or signed, the pending redaction, burned markup, or deficiency is permanently
placed in the shifted location. The shifting of notes that do not permanently alter the document can
be corrected any time by your system administrator.
Creating a Redaction
You can apply and save redactions to a document if all of the following conditions are met:
• You have sufficient privileges to modify the document.
• The document's file type supports redactions. Only image and text files can be redacted.
Note: You can print redacted documents on an ad hoc basis even if their Document Types are
not configured for redactions. Apply the redactions, and then print the document. Then, close the
document without saving the redactions.
2. From the redaction drop-down list, select whether you want to create a black redaction or a white
redaction. If you select Black Redaction, the redacted area will be defined by a black, opaque
rectangle. If you select White Redaction, the redacted area will be defined by a white, opaque
rectangle.
3. Using your mouse, define the location and size of the redaction by clicking and dragging the
pointer over the area you want to redact. Repeat for each area you want to redact.
4. Save the redacted image by clicking the Save Redaction button.
• OnBase displays the message Your redaction has been saved successfully, indicating
that the redacted document has been created. Depending on your system's settings, this
redacted document is saved to another Document Type (the original document may also
be deleted in this scenario), is saved as a revision of the current document, or replaces the
original document.
Note: If your system is configured to save the redacted document as a revision, you may
lose annotations or notes that were applied to the original document. See your system
administrator for questions regarding redaction settings.
• If OnBase indicates that the redaction could not be saved, the Document Type may not be
configured for redactions.
• If the document is closed or refreshed before one or more redactions have been saved, a
message box prompts you to Save Redactions or Close. To save all created redactions, click
Save Redactions. To discard them, click Close.
Note: If you switch between Overlay and Non-Overlay modes, a message is displayed indicating
that the redaction will be removed.
System Interaction
App Builder can interact with additional system modules.
Reporting Dashboards
If Reporting Dashboard is properly configured and OnBase solution is licensed for Reporting
Dashboard, you can access a Dashboard as a source. You can do it by selecting it at the Master
Detail with Sources screen, using a tile on a Quick Access screen, or using a bookmark.
Once opened, a Reporting Dashboard with preconfigured data is displayed. It is highlighted in the
sources panel.
Depending on application configuration, you can display a document or a folder that the document
belongs to.
For further information, see Reporting Dashboards documentation.
Unity Forms
If your Unity Form is properly configured and your OnBase solution is licensed Unity Forms, you can
create a new Unity Form instance in the application.
Unity Form creation can be accessed from an action, or with a direct link to it.
Unity Form templates are configured in the Unity Forms Designer. For information on Unity Forms
configuration, see the Unity Forms module reference guide or help file.
Workflow
If your Workflow Life Cycle is properly configured and your OnBase solution is licensed Workflow, you
can access Workflow in the application.
The following are possible:
• Viewing Workflow Queues on page 213
• Using Workflow Tasks on a Single Document on page 213
• Using Workflow Tasks on Multiple Documents on page 214
For more information, see the Workflow module reference guide or help files.
3. Click the required document once to open it. It is opened in a new window.
4. You can use the arrow to get back to the Workflow queue.
Note: Workflow tasks can be executed from any type of source. You do not have to use the
Workflow queue to access them.
2. Open a document from the source. A Document View is displayed. Workflow tasks are displayed
as buttons in the upper-right corner.
3. Select the desired task. If you do not see the task directly, use the dots button to see more tasks.
4. If the task execution takes longer, a window is displayed saying: "Executing task. Please wait."
5. When the task is finished, you are brought back to the document list.
Note: If a document belongs to a Workflow-related document type, the Workflow tasks will be
displayed in every source that you access the document from.
2. Select documents from the document list. All available tasks shared by the selected documents
are displayed in the upper-right corner.
Note: When the tasks are accessed from a document retrieval source, system tasks are
displayed first and ad-hoc tasks are under the More button.
When the documents are accessed from a Workflow queue, ad-hoc tasks are displayed first and
system tasks are under the More button.
3. Select the task.
4. When the task is finished, you are brought back to the document list.
WorkView
If you are licensed for WorkView, you can create and see WorkView objects in the configured
application.
You can create a WorkView object using an action, or a direct link.
You can open WorkView objects that are associated with a Workflow queue.
For more information, see the WorkView module reference guide or help files.