Managing Applications 4-3
For more information about uploading documents, see Oracle® Fusion Middleware Users Guide for Imaging and Process Management.
4.2 Creating An Application
Open the Manage Applications panel in the navigator pane of the Oracle IPM user interface to start the process of defining an application.
You will complete the following tasks in the following order:
1.
Specifying General Properties : Name and describe the application
2.
Defining Application Fields : Define fields used and indexed in the application
3.
Assigning Application Security : Assign application security permissions.
4.
Assigning Document Security : Assign document security permissions.
5.
Assigning a Storage Policy : Define a storage policy for content.
6.
Configuring Workflow Integration : Configure any workflow processes for content
within the application.
7.
Reviewing Application Settings : Review application settings and submit.
4.2.1 Specifying General Properties
You must provide each application with a name. The application name is displayed in the Applications panel in the navigation pane once the application is created. You
must also specify the repository for the application. Once the application is created, you cannot change the repository selection. An optional brief description of the
application can be entered that displays on the application summary page when an application is selected. To view this page, see
Section A.24, Application General Properties Page.
Note: The Oracle IPM user interface displays different panels in the
navigator pane based on your permissions. Unless you have application system permissions, or administration permissions to at
least one individual application, the Manage Applications panel is not displayed in the navigator pane. You must have either Create or
Administrator permission to create an application. The user creating an application must also have at least View permission to the
connection repository being used.
Note: Changes to the repository DOCMETA table caused by
creating, deleting, or modifying an application can potentially cause a problem on an active repository server if any other operation is also
affecting the table. While this is unlikely, it can cause a problem uploading documents and so it is helpful to coordinate changes to an
application with idle time on the Oracle Content Server repository server.
To help mitigate any potential problems, multiple Oracle Content Server repository instances can be used to isolate business units so
that any one application change has less impact on the enterprise organization.
4-4 Administrators Guide for Oracle Imaging and Process Management
To specify the application general properties, do the following:
1.
Expand the Manage Applications panel in the Navigator Pane
and click the Create Application
icon. The Application General Properties Page
is displayed.
2. Enter a name for the application in the Name field. For example, if creating an
invoicing application for XYZ Company to store invoices from the United States division, name the application Invoices_US. The application name is displayed to
users on the Upload Document page and to system administrators when creating inputs and searches. This field is required.
3. Optionally enter a description of the application in the Description field. For
example, All Invoices for the United States Division. This description is displayed beneath the title on the application Summary page, when using the Document
Upload Tool, and when you hover your cursor over the application name in the Manage Applications panel in the
Navigator Pane .
4.
Select a repository for the application from the field. Because it is likely that you will have many repositories, this field specifies which Oracle Content Server
repository to use for this application. Multiple Oracle Content Server repositories can be used for different applications to balance the load or to offer a way to
isolate content to specific business units. In the XYZ Company example, one repository can be used to hold all invoices from the European division, another
repository can be used to hold all invoices from the United States division, and another can be used to hold all Human Resource documents, etc. Once defined
and the application is created, the repository cannot be changed. This field is required.
5.
Specify if you want to be able to search the full text of a document. In order to do so, the repository server must be set to index full text and the document must be in
a format that has text information. Many imaging solutions do not require full-text indexing or need to search text information. For example, the XYZ Company
Invoices_US application does not require full-text indexing because the invoices are scanned in and uploaded as TIFF images. TIFF images of documents do not
contain text information, and so cannot be full-text indexed, and invoices are searched for using the metadata values. However, the Human Resources
department may upload resumes and employment contracts as electronic files and have a need to search for the text of the files. In such a case, an Employment
Contract application may need to be full-text indexed.
6. Click Next to go to the
Application Field Definitions Page .
4.2.2 Defining Application Fields
