1-12 Administrators Guide for Oracle Application Adapters for Oracle Enterprise Content Management
1.3.1.1 Attachments Scenario 1: Capturing Identity Documents
A Managed Attachments solution configured for capturing employee identity documents such as passports might work as follows:
1. From the business application, a user retrieves a record such as an employee
record.
2. The user launches the Managed Attachments solution, by selecting a command or
clicking a link or button called Scan Employee Document. 3.
Oracle Distributed Document Capture launches and automatically initiates a scan if a scanner is attached to the desktop or enables the user to upload electronic
images from desktop.
4. The user selects attachment settings, clicks Scan Document, then enters index
values metadata in Oracle Distributed Document Capture to store with the images.
5. The user clicks Send, which transmits the captured document images and their
metadata from Oracle Distributed Document Capture to Oracle UCM.
6. The user clicks the Refresh button to see the newly scanned or imported
document listed as attached to the selected employee record.
1.3.1.2 Attachments Scenario 2: Viewing and Editing Identity Documents
A Managed Attachments solution configured for viewing employee identity documents might work as follows:
1.
From the business application, the user retrieves an employee record.
2.
The user launches the Managed Attachments solution, by selecting a command or clicking a link or button called View Employee Documents.
3.
The Managed Attachments screen displays, listing attachments for the employee record.
4.
An attachment may show its revision number, and if it was checked out by the user or another user. If revision-specific mode has been configured and an older
revision is attached, the user can either view the older attached revision or view the newer revision and make it the new attached version.
5. The user selects an attached document’s Edit icon. As the user makes updates to
the document, it is checked out to the user and other users cannot edit it. When the user checks in the revised document, its revision number is incremented.
6.
The document displays in Oracle UCM or the AutoVue viewer, where the user can view its images, and with appropriate permissions, apply annotations or
redactions.
1.3.2 About the AXF Command and Service Used By the Attachments Solution
The Managed Attachments solution uses an AXF solution namespace called UCM_ Managed_Attachments
to orchestrate user requests from the business application to display the Managed Attachments user interface for the Oracle UCM Content Server
repository.
■
When the business application user activates the Managed Attachments command from a business application entity, the adapter makes an AXF request. The solution
supports a single AXF command namespace called UCM_Managed_Attachments, which invokes the AF_GRANT_ACCESS command.
Solutions Overview 1-13
■
The AF_GRANT_ACCESS command implements the AF_GRANT_ACCESS service. This Oracle UCM service temporarily grants a user who has logged into
the business application access to all Oracle UCM documents associated with the selected business application entity and to which the user has security group
access. This service also returns an AXF response containing a Managed Attachments URL to invoke the Oracle UCM attachments framework search. This
framework search lists all documents associated with the business application entity.
■
With the returned URL, the adapter opens the Managed Attachments browser window for the business application user, also displaying key values AFLabel for
the business application entity with which the attachment list is associated.
How Oracle UCM Access is Granted to the Business Application User The adapter uses a temporary authorization mechanism for managed attachments
access. Communicating through a trusted RIDC mechanism, AXF invokes the AF_ GRANT_ACCESS service with the application entity and user information needing
authorization. The AF_GRANT_ACCESS service grants access to the user for the specified period, then ends the user session.
1.3.3 Managed Attachments Solution System Architecture
Figure 1–11 illustrates the Managed Attachments architecture when installed for
Oracle E-Business Suite use.
Figure 1–11 System Architecture for an Oracle E-Business Suite Adapter Managed Attachments Solution
Figure 1–12 illustrates Managed Attachments architecture when installed for Oracle
PeopleSoft use.
1-14 Administrators Guide for Oracle Application Adapters for Oracle Enterprise Content Management
Figure 1–12 System Architecture for an Oracle PeopleSoft Adapter Managed Attachments Solution
1.4 About the Adapter Components
The adapter includes the following main components:
Application Extension Framework AXF AXF is included in ECM installation. AXF solution tables are automatically created
during installation.
Business Application Plug-In This portion consists of a business application plug-in Oracle E-Business Suite, or
Oracle PeopleSoft, or both.
■
Configuring the Oracle E-Business Suite plug-in consists of running PLSQL scripts against the Oracle E-Business Suite database that populate tables and
configure functionality. You also upload files to the Oracle E-Business Suite system that integrate custom actions with pre-existing Oracle E-Business Suite Forms. See
Section 2, Configuring the Oracle E-Business Suite Plug-In.
■
Configuring the Oracle PeopleSoft plug-in consists of importing the Oracle PeopleSoft project, configuring the Integration Broker to communicate with AXF,
setting user roles, and enabling AXF functionality on Oracle PeopleSoft pages. See Section 3, Configuring the Oracle PeopleSoft Suite Plug-In.
Oracle UCM Components If using the Managed Attachments solution, this portion includes Oracle UCM
components bundled in ZIP files that you install and enable using Component Manager. They include the AppAdapter framework core files. See
Section 6.3, Configuring the Oracle UCM Components.
