38 Oracle Imaging and Process Management

This chapter describes issues associated with Oracle Imaging and Process Management. It includes the following topics:

38.1 General Issues

This section describes general issues. It includes the following topics:

38.1.1 I/PM Session Time Out When Using OSSO Requires Browser Refresh

When using Oracle Single Sign On and an I/PM session expires, WebLogic Server will return an internal server error. Refreshing the page returns to the I/PM log in page for reauthentication to start a new session.

38.1.2 Mixed Translations On Page

Oracle products support 10 standard languages for administrative tasks and 27 standard languages for user tasks. This means that in instances when a selected language is supported for user but not administrative tasks and an administrative task is performed, multiple languages may be displayed in the user interface.

38.1.3 Deleting More Than 100 Documents Can Cause Http 404 Errors

There is a known issue with Microsoft Internet Explorer if attempting to delete more than 100 documents using a search results table. Doing so can cause Internet Explorer to return a 404 Page Not Found error or potentially lock. This is due to Internet Explorer limiting URL strings to a maximum of 2083 characters. If it is necessary to delete over 100 documents using a search results table, Mozilla Firefox supports URLs up to 65,000 characters.

38.1.4 Time Zone Option Removed from Preferences Page

The option to specify a local time zone has been removed from the Personal Information section of the Preferences page. All time information is now based on the time zone of the I/PM server. This means that any date metadata generated by the Oracle I/PM system, such as document creation date, modify date, or other audit events, is governed by the time zone of the I/PM server, and not the user time zone. This can cause date data to be displayed differently to what may be expected on some documents because the time zone may cross midnight.

For example, if the I/PM server is in the Greenwich Mean Time (GMT) time zone and a document is created in the GMT+6 time zone on January 10th at 2:00 AM local time, the creation date that will be displayed in the user interface will be January 9th at 8:00 PM. This can have implications when searching for content based on creation and modification dates of documents.

38.1.5 I/PM Documents May Be Visible Natively Within WebCenter

If an I/PM is viewed through WebCenter, then the document is cached in WebCenter. This means that if a document is viewed in WebCenter prior to being annotated, the non-annotated document is viewable until such time as the WebCenter cache is refreshed. Redacting a document after it has been cached in WebCenter does not cause the original document to be purged from the WebCenter cache, and so redacted content may be compromised. To help protect redacted content when I/PM is integrated with WebCenter, use the Viewer on the Upload page to redact documents prior to uploading to I/PM.

38.1.6 Removing Full-Text Search Capabilities From Defined Applications

Removing full-text search capabilities from a defined application can cause an error in any defined search against that application if the Document Content condition is not also removed from the search. When modifying an existing application to remove full-text indexing capabilities, ensure that you also remove all Document Content conditions from any defined searches against that application.

38.1.7 Application Field Limitations When Using Oracle Text Search

When Oracle I/PM is configured to use OracleTextSearch and an application is defined to do full-text indexing, a maximum limit of 20 SDATA fields for the Content Server repository is imposed on I/PM. SDATA fields are defined as optimized fields by the Oracle Text Search component and are typically non-text, non-memo fields, although other criteria can exist to define text fields as optimized SDATA fields.

When defining an application, Oracle I/PM queries the repository DOCMETA table for the number of available SDATA fields and does not allow the creation of any non-text fields within the application beyond the available number. However, additional components installed on the Content Server repository, such as Folders or Discussions, may reduce the total number of available SDATA fields. Because other configurations may consume SDATA outside of the DOCMETA table, you may be able to add fields to an application but get an error when trying to rebuild the search index in Content Server. If this occurs, you must redefine the application with fewer non-text fields until you are able to successfully rebuild the search index.

38.2 Browser Compatibility Issues

This section describes browser compatibility issues. It includes the following topics:

38.2.1 Safari: No Keyboard Access To Reorder Columns Select Order Buttons

On the Reorder Columns page in Safari, the buttons to move a selected item up or down the page are not accessible when using keyboard commands to access the page elements. The Reorder Columns page is displayed when selecting View, then Reorder Columns on a search results page. To work around this issue, you must either use a different browser that supports these keyboard commands, such as Microsoft Internet Explorer or Mozilla Firefox, or navigate the Reorder Columns page with a mouse in Safari.

38.2.2 Safari: Unexpected Tab Order In Search Results Toolbar and Viewer Menus

When using the keyboard tab button to select functions on the Toolbar of a Search results page, the expected behavior is to focus on the first option (View) and then move to the next (Email). Instead, the tab button causes focus to move through the hidden View submenus before moving the focus to Email. Similarly, when using the tab button to select menus on the Viewer, the expected behavior is to move focus from the first Viewer menu (File) to the next (View). Instead, the tab button causes the focus to move through the hidden submenus of each top-level menu before moving focus to the next menu.

38.2.3 Safari: Viewer Menus and Dialog Boxes Hidden Beneath Main Page Region

There is a problem with how Safari handles layer order of page items in the Viewer. This causes the main page region where documents are displayed to hide all or parts of Viewer menus and dialog boxes when a document is viewed using Safari. To work around this issue, expand the Properties, History, or Sticky Notes panel into the main page region enough to allow the obscured items to be displayed, prior to accessing the menus or any dialog boxes. This is not an issue when using either Microsoft Internet Explorer or Mozilla Firefox, and an alternate workaround would be to use either of these browsers to view documents.

38.2.4 Safari: Unable to Use Keyboard to Select Panels In Viewer

When using the keyboard tab button to select items on the Viewer, none of the panels (History, Sticky Notes, or Properties) can be selected. This is a known issue with Safari. If you need to use the keyboard to select a panel in the Viewer, you must use either Microsoft Internet Explorer or Mozilla Firefox to view documents.

38.2.5 Safari: Cannot Get Out Of The Applet Using Keyboard

When using the keyboard tab button to select items on the Viewer, keyboard commands cannot focus outside of the Viewer applet and tabbing will stay within the Viewer. This is a known issue with Safari. If you need to use the keyboard to select one of these options, you must use either Microsoft Internet Explorer or Mozilla Firefox.

38.2.6 IE: Non-ASCII Characters Not Supported in Internet Explorer for ExecuteSearch

The Search URL Tool (ExecuteSearch) does not work in Microsoft Internet Explorer if non-ascii characters are used in the search name. If it is necessary for your search name to have non-ascii characters, you must use Mozilla Firefox version 3.5 or higher and set the following parameters:

  • prefs.converted-to-utf8=true

  • network.standard-url.escape-utf8=true

  • network.standard-url.encode-utf8=true

  • network.standard-url.encode-query-utf8=true

38.3 Accessibility Issues

This section describes accessibility issues. It includes the following topics:

38.3.1 Firefox: Focus Issue With Upload Button Using Keyboard

With Firefox, when creating an input using Manage Inputs options, an issue occurs with keyboard focus for the Upload button. When attempting to tab to the Upload button, the focus changes to the browser banner instead. Use Shift+Tab to return to the dialog window and the focus should stay in the dialog window, or use a different supported browser.

38.3.2 Focus Issue Adding Document Security Using Keyboard

On the Document Security page of the Application Creation Wizard, clicking Search incorrectly changes the focus away from the dialog box. This issue occurs in Internet Explorer and Safari. This issue does not occur in screen reader mode.

38.3.3 Name of File Selected For Import Not Displayed in Screen Reader Mode

When in screen reader mode and selecting a file to import, the file is loaded and the Next button becomes available, but the name of the file to be imported is not displayed.

38.3.4 Issues Selecting From Calendar Using Keyboard

In Internet Explorer 7, when selecting dates from a calendar using the keyboard, you cannot select a day. This is not an issue in Firefox, Internet Explorer 8 or Safari 4. In addition, the following buttons are skipped when tabbing: Previous month, Previous year, Month increase/decrease, and Year increase/decrease. An alternative to selecting the date with the keyboard is to manually enter the date with the number keys.

38.3.5 Focus Issue in Create Searches Wizard Using Keyboard

After completing fields in the Create New Search Wizard, the keyboard focus changes to the browser URL and you must tab through the banner and navigation before you can edit the current page.

38.3.6 Annotations Not Recognized By JAWS

When viewing a document with annotations while running JAWS, you can tab to an annotation, but no description is read by JAWS.

38.3.7 403 Link Error Returned For Collapse Pane Link

When viewing a document using screen reader mode and Advanced Viewer mode, JAWS reaches the Close Tab options in the Viewer and reads a collapse pane link that is not visible after More options. If you click when JAWS reads link, a 403 Forbidden Page error is returned.

38.3.8 Internet Explorer: Focus Issue During Search Using Keyboard

When searching using Internet Explorer, expanding and collapsing the instructions tree using the keyboard incorrectly changes the focus to the Skip to Content link instead of the next row.

38.3.9 Date Selected From Calendar Lost Using Keyboard

When using the keyboard to select a date from a calendar control, the selected date is not retained. The workaround is to enter the date into the date field using the number keys on the keyboard.

38.3.10 Viewer Keyboard Shortcuts Missing From Documentation

The shortcuts listed in Table 38-1 are available in the viewer. All shortcuts except the first one listed (M) apply to the Advanced Viewer when the applet has focus.

Table 38-1 Image Viewer Keyboard Shortcuts

Keyboard Shortcut Description


Exits the applet and changes the focus to the menus at the top of the viewer page.


Adds a highlight.


Adds a redaction.


Adds a line.


Adds a sticky note.


Opens a new text annotation.


Places a stamp annotation.


Tabs forward through the toolbar and annotations.

Shift + Tab

Tabs backward through the toolbar and annotations.


Selects the next annotation.


Selects the previous annotation.

Arrows (or number pad arrows)

Moves the selected annotation.

Shift + Arrows (or Shift + number pad arrows)

Sizes the selected annotation.


Copies the selected annotation.


Pastes the copied annotation.


Deletes the selected annotation.


Undoes the last deletion.


Rotates the document clockwise.


Rotates the document counterclockwise.


Changes the magnification to fit the document's height.


Changes the magnification to fit the document's width.


Zooms to a quadrant on the document.


Opens the GoTo Page dialog box.

38.3.11 Some Annotation Buttons Incorrectly Read by JAWS

When you first open a document in Advanced Viewer mode using screen reader mode, JAWS incorrectly adds the phrase Insert F1 Help Text after each button name.

38.3.12 Internet Explorer: Long Panels Not Visible In Screen Reader

When using Microsoft Internet Explorer and I use a screen reader is enabled on the user preferences page, some panels in the Navigation pane may not display, although the text of the panel title is still read. This is caused when the panel name is too long. Depending on the user interface language, this could happen to one or multiple panels. If you expand the panel above the hidden panel, the hidden panel is then displayed.

38.4 Document Errata

This section has the following topic:

38.4.1 Incorrect Date Specified in User Interface Section of Administrator Guide

The Oracle® Fusion Middleware Administrator's Guide for Imaging and Process Management has incorrectly specified a date in section A.34.1 on page A-38. The example in the Format Values element description for formatting a date field currently states:

". . . if the Format Value field were populated with yyMMMdd - HH:mm:ss, the Sample Date would display 10Jan01 - 15:16:59 for a date and time of January 10th, 2010 . . ."

Instead, the statement should correctly read:

". . . if the Format Value field was populated with yyMMMdd - HH:mm:ss, the Sample Date would display 10Jan01 - 15:16:59 for a date and time of January 1st, 2010 . . ."