Oracle Public Sector Revenue Management

Release Notes

Release 2.5.0.0.0

E71302-01

March 2016

Documentation build: 2.13.2016 4:41:49 [T1_1455367309000]

Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Preface

These release notes provide an overview of the enhancements, known issues, and other changes in Public Sector Revenue Management

Audience

Public Sector Revenue Management Release Notes is intended for anyone installing or using Public Sector Revenue Management.

Related Documentation and Resources

Installation Guides

- Public Sector Revenue Management Release 2.5.0.0.0 Quick Install Guide

- Public Sector Revenue Management Release 2.5.0.0.0 Installation Guide

- Public Sector Revenue Management Release 2.5.0.0.0 Database Administrator’s Guide

- Public Sector Revenue Management Release 2.5.0.0.0 Optional Products Installation Guide

- Public Sector Revenue Management Release 2.5.0.0.0 License Information User Guide

Administrative and Business User Guides

- Public Sector Revenue Management Release 2.5.0.0.0 Administrative User Guide

- Public Sector Revenue Management Release 2.5.0.0.0 Business User Guide

Supplemental Documents

- Public Sector Revenue Management Release 2.5.0.0.0 Server Administration Guide

- Public Sector Revenue Management Release 2.5.0.0.0 Security Guide

Documentation Conventions

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Release Notes

Next in This Section

- Introduction

- Release Overview

- New Functionality

- Oracle Utilities Application Framework Enhancements

- Known Issues

- Deprecation Notices

- Demo Data Information

Introduction

This document provides general information about Public Sector Revenue Management Release 2.5.0.0.0, including new functionality, known issues, and other important information.

Refer to the Public Sector Revenue Management Quick Install Guide and Public Sector Revenue Management Installation Guide for information regarding supported platforms and installation steps.

This section includes the following:

- Release Overview

- New Functionality

- Oracle Utilities Application Framework Enhancements

- Known Issues

- Deprecation Notices

- Demo Data Information

Release Overview

This section contains general information about this release of Public Sector Revenue Management Release 2.5.0.0.0.

This release includes the following components:

- Public Sector Revenue Management Release 2.5.0.0.0

- Oracle Utilities Application Framework Release 4.3.0.1.0

New Functionality

This section describes new and enhanced features in this release of Public Sector Revenue Management.

New User Interface

Public Sector Revenue Management Release 2.5.0.0.0 adopts the Oracle Alta User Interface (UI) standard. The Oracle Alta UI is the new standard for Oracle Applications and Oracle Cloud-based services. The new user interface enables a strikingly modern, simpler and more engaging experience to address customers’ increased user interface expectation. For backward compatibility, the structure of existing screens is retained.

Full Java Release

Public Sector Revenue Management Release 2.5.0.0.0 is a full Java release. All implementation-specific customizations/extensions to the base product will be required to be written in Java or scripting language (COBOL is no longer supported).

For existing Public Sector Revenue Management implementations upgrading to Release 2.5.0.0.0, all existing implementation-specific customizations/extensions written in COBOL are required to be converted/migrated to Java.

Oracle Utilities Application Framework Enhancements

This section describes new and enhanced features in this release of Oracle Utilities Application Framework v4.3.0.1, including:

- System Wide Enhancements

- Online Help Enhancements

- Security Enhancements

- Configuration Tool Enhancements

- Batch Enhancements

- To Do Enhancements

- Miscellaneous Enhancements

- Extendable Lookup Enhancements

- Web Service Enhancements

System Wide Enhancements

New Login Screen Images

In this release, the image visible in the Login screen for the application has been changed.

New Session Expiration Behavior

In previous releases, if a user's session had expired, the user was still able to perform some tasks that did not require interaction with the server. When the system attempted to interact with the server, the user was then returned to the login screen or was presented with an error.

In this release, the system has been enhanced to detect the timeout and show an alert that the session has expired, informing the user to login again.

Indicating Required Fields

In this release, required fields (elements) are marked using an asterisk. This is visible on the maintenance dialog objects defined using a business object that are maintained on a portal-based page (also referred to as 'new style'). It is not visible on objects maintained on a fixed page (also referred to as 'old style').

Required elements for a row in a child collection (list) are also marked with an asterisk. Note that the system does not have any visual marking to indicate that at least one row in a child collection is required. It is only able to highlight which elements must be populated for each row.

The system relies on the field or element configuration (table/field metadata and BO schema configuration) to display the asterisk. If there are elements that are required via an algorithm or some other procedural code, the system is not able to detect that condition in order to display the asterisk.

If an implementation does not wish to enable this functionality, it may be turned off via the properties file. To turn this functionality off, uncomment the following setting #com.oracle.ouaf.ui.disableRequiredFieldIndicators = true in the spl.properties.template file.

Menu Behavior Enhancements

In the previous release, the menu behavior changed from the 4.2.x code line. In this release, some further changes have been made to the display of menus:

- Clicking the Menu or Admin button causes the first sub-menu to appear. If other submenu options are available, a right arrow is visible on the menu line, the user can mouseover the menu line to show the sub-menu. The user may now click this menu line to lock the sub-menu. The right arrow image is replaced by a padlock image. If the user's mouse moves away from the menu area, the locked sub-menu remains visible. This resolves the usability issue of needing to keep the cursor lined up on the menu line as the mouse is moved toward the sub-menu to further select the desired option.

The user may now do one of the following:

- Click on or mouse over the desired sub-menu line to further open the next level and ultimately click the desired option.

- Click on a different menu line to lock that sub-menu instead.

- Click the ESC key or click on an area of the page outside the menu to close the menu.

- For menu lines that support Search and Add options, the Search option now appears before the Add. This is an effort to use the menu line and item metadata configuration to drive the display. The base product menu lines always configure the search menu item first, followed by the add menu item. The menu rendering now follows that.

Note: If your implementation has custom menu lines with multiple menu items where the add is configured as the first menu item and search as the second, then the menu rendering will reflect that.

- In the 4.2.x code line, the add option was rendered as an image (configured on the menu item). In 4.3.0.0, the menu rendering changed to use the word Add and an image is no longer used, however, the internal code still used the presence of the image reference in the menu item to signal which of the menu items is the ‘add’. Because the image itself is not necessary, the code has been enhanced to cater for no image configuration. In this case, the system assumes that when a menu line has two menu items, the first menu item represents the search and the second represents the add.

Note: For backward compatibility, the system will continue to look for an image and assume that the menu item with the image is the add. If your implementation has custom menu lines with two menu items, where the add is first (but still refers to an image), no changes are needed. (However, note that in this case, the add will display before the search option.) If you wish to remove the image (that is no longer needed), be sure that the search menu item is the first in the sequence.

Menu Configuration Enhancements

In this release, the Label Long on the Menu maintenance object has been suppressed from the user interface. This field is not used by the system.

In previous releases, the Description on the Menu maintenance object was only enabled for the Main and Admin menu types and was used to build the menu bar prior to version 4.3.0.0. In this release, the description is now available for all menu types and may be used to provide information about the menu. The menu search has also been enhanced to search by the description and to return the description in the results.

Toolbar History Enhancements

In this release, when a user navigates to a portal that is configured to display its information string as part of the page title (via the FK reference on the portal options), that detail is also visible in the History drop-down in the application toolbar.

This functionality is only available for portal based pages. It is not available for navigating to fixed pages. Also note that the current product standard is not to configure all-in-one portals to reference the information string.

Component Install/Deploy

In previous releases, installation and management of individual components of the product was complex. In this release the installation has now been altered to identify the roles supported by the installation to optimize the configuration and management of each installation. In this release, the online, integration and batch roles are supported to optimize the components available for configuration and deployment. An environment identifier has also been introduced to group disparate installations, even across machines, into a single managed environment. The roles for an installation are typically determined at installation time, but this enhancement allows change of roles after installation without the need for re-installation.

Online Help Enhancements

Oracle Help for the Web

In this release, implementations using WebLogic will see a new help implementation using Oracle Help for the Web (OHW). Besides a slightly different look and feel for the table of contents and the topics, OHW provides the following capabilities:

- Full text search - If there is a term that you want to find help about, you can use the full text search to find topics that reference that term.

- Combined index - In previous releases, if an implementation included multiple products in the stack, each with its own help set that was included, the index was separated. A user needed to first select the product and then search for the index term. With OHW, the index terms are combined for all products providing their separate help topics, increasing usability.

- Various usability controls such as paging through topics.

- The ability to provide feedback to the documentation team through a feedback form

Oracle Help for the Web is not available in WebSphere. Clients using WebSphere will continue to see the Classic online Help available in previous releases.

Oracle Utilities Application Framework Help Included in Edge Product Help

In previous releases, the online Help that is specific to the Framework product was installed separately from online Help provided by each edge product. The table of contents for the help was visible side by side. In the Classic help view, the index entries were kept separate as well. Starting with this release, the edge products will incorporate the help for Oracle Utilities Application Framework into its build of the help.

The following provides additional details:

- For the business process chapters, the Framework topics User Interface Standard Features, To Do Processing and Reports are incorporated into the outline of the edge product help in a location appropriate for that product's help. For a business user, this removes the distinction of what functionality is provided by the Framework layer and what functionality is provided by the edge product.

- The business process chapters for Batch Processing and External Messages have been moved to the corresponding chapters in the Public Sector Revenue Management Administrative User Guide.

- In the Public Sector Revenue Management Administrative User Guide, the full set of Framework chapters are included, followed by the full set of chapters associated with this product.

Security Enhancements

In this release, the following enhancements have been made to the application security functionality.

Enhance User BO Used for External System Integration

In this release, changes have been made to the business object that is used to create Users from Oracle Identity Management (OIM) to support a template user.

In previous releases, in order to define a user from OIM, an implementation needed to define a Generic Technology Connector (GTC) to map information from OIM to the product. The implementation could choose to:

- Expose the information to the OIM administrative user to define the information when creating the application users. For example, for this new user, specify their Home Page or valid User Groups.

- Define standard values in the mapping file so that the OIM administrative user doesn't need to specify them for every user (for example the Language or the Time Zone).

In this release, the product provides the ability to use a template user in the application with appropriate configuration for users of that type. In OIM, the Generic Technology Connector (GTC) can be defined with the bare minimum needed to create a valid application user (such as their Name, Email Address and User ID) along with a template user from which all the other configuration data can be copied. This allows an implementation to define template users for standard roles. For example, in Public Sector Revenue Management, template users can be defined for Call Center Users, Billing Users, Collection Users, System Administrators, etc. Each template user can define the appropriate User Groups, Home Page, Portal Preferences, To Do Roles, etc for users in that role.

The F1-IDMUser business object (User for External System Integration) now has a preprocessing algorithm that looks for a template user (defined as a characteristic). It retrieves the configuration from the template user. It creates the new user with a combination of the information passed in from OIM (such as name, User ID, Email Address) and the information from the template user.

Separately Secure Change to a User's User Groups

The ability to change the Enable/Disable flag on the user record requires special security. However in previous releases, all other attributes of a user could be modified by anyone with security for the Change access mode, including the user group configuration.

In this release a new access mode (Administrator) has been introduced to the User application service allowing implementations to separately secure the ability to change a user's user groups.

Note: For backward compatibility, all user groups that have security for the Change access mode will be updated to also have security for the new System Administrator access mode. Implementations can then decide if they would like to take advantage of the new capability to limit which user groups should allow changes to the user's user group information.

Configuration Tool Enhancements

In this release, the following enhancements have been made to configuration tool functionality.

Schema Editor Enhancements

The following enhancements have been made in the schema editor for defining elements for a business object:

Enhancement to Map XML Element Definition

In previous releases, the schema editor's Map XML Field provided a search to find the appropriate field within the MO to use for the mapping. In this release, the field has been changed to a dropdown given the typically small number of CLOB or XML data type fields in a given MO.

Simple Field

In this release, a new schema editor element type Simple Field has been introduced to help simplify the steps needed to create an element that is mapped using Map XML. This can be thought of as a type of wizard for a specific type of Field element. It exposes a subset of configuration available for the Field element type. In the Database Mapping section, only the Map XML Field element is exposed.

Note that this is only available for the schema editor on Business Object because that is the only place where the maintenance object is known. For other schema editors on other pages, for example the Data Area schema editor, the Field element type must be selected to define this type of element.

Scripting Enhancements

The XQuery processor for scripting engines 2 and 3 has been upgraded. It now supports the functions 'matches', 'replace' and 'tokenize'. In addition, it is able to reuse more XPath expressions than before. As a result, implementations can reduce the XQuery LRU cache size in the spl properties file (com.oracle.XPath.LRUSize). The adjustment depends on your specific implementation. A rough recommendation is to reduce the cache size by about one-third.

Batch Enhancements

Batch Parameter Security

In this release, a new security flag has been added to the batch control parameter collection to indicate if there should be some security applied to the value of the parameter. The values of the security flag are Encrypt and None. The default is None. The configuration of the parameter value's security must be set on the batch control.

If the parameter value's security is set to Encrypt:

- Any default value set on the Batch Control will be stored in the database as encrypted.

- When the batch job is submitted using Batch Job Submission, the value will be shown encrypted.

- In the log generated for the batch job, the parameter value will be written with asterisks.

Note: All existing base product owned batch controls have been updated to set the parameter to None to maintain backward compatibility. The configuration of any base owned batch control may be changed by an implementation. The recommendation for the F1-LDAP (LDAP Import) batch control is to configure the 'password' parameter value to Encrypt.

System Health Check

In this release, a new service has been provided to assess the health of the system. The current implementation of this service is to execute the batch control - level of service algorithms. It is possible that in the future additional health check types may be supported.

The service can return an overall status based on the details of the health check (for example, based on the details of the level of service algorithm results).

- 200 indicates that everything is normal /healthy.

- 203 indicates that a non-critical function is degraded.

- 500 indicates that one or more critical functions is degraded.

- The health check service maps the following results returned by the level of service algorithms:

- If at least one algorithm returns a value of Error, an overall status of 500 is returned.

- If no algorithm returns a value of Error and at least one returns a value of Warning, an overall status of 203 is returned.

- If all algorithms return a value of Normal, an overall status of 200 is returned.

An Inbound Web Service F1-HealthCheck has also been provided allowing external systems to use a web service to retrieve this information.

In addition, the product provides a Health Check portal that shows the details of the health check. The output of each batch control's level of service algorithm is displayed.

To Do Enhancements

This section describes To Do related enhancements.

Allow Additional Sort Keys on Manual To Dos

In previous releases, the product allowed for a To Do Post Processing algorithm to populate custom sort keys. However, in the case the standard sort keys for a manual To Do (User ID, User Name and Subject) were not populated by the system.

In this release, the product ensures that the standard sort keys of User ID, User Name and Subject are populated on a manual To Do Entry even when custom sort keys are also populated. The To Do Type must define the standard sort keys for the manual To Do entry (as described in the Online Help).

Note: This functionality was originally implemented as a hot fix to the 4.2.0.2.0 code line via bug 20886978.

Miscellaneous Enhancements

Attachment Creation Enhancement

In previous releases, the procedure for creating an attachment was two steps: first choose the appropriate business object based on the type of attachment and enter a description; then upload the attachment.

In this release, the attachment creation has been streamlined to follow a more typical attachment dialog. Now when a user wants to create an attachment, first the user selects the file to upload. The system then determines the business object and prompts the user for the description (and any other fields that may get captured depending on your specific product). The uploaded attachment is then saved.

Note:
If your implementation has created customized dialogs to create an attachment and call the base BPA F1-AttchMain (Attachment Maintenance), some minor changes are required to your custom BPAs to align the script's data areas with the F1-AttchMain.

In addition, if your implementation includes a custom BPA for uploading attachments and invokes the base UI Map F1-AttachmentUploadPopup following the pattern of the base BPA F1-AtchUplod the custom BPA will need to change how it invokes the Attachment Upload map to reflect the changes in the FW Attachment Upload BPA. The script step was changed from an Invoke Map step type to an Edit Data step type. It sets the target area as Page Area rather than Pop-Up Window and caters for the new Cancel action. Please contact Customer Support if you need more information.

Extendable Lookup Enhancements

Characteristics Added

In this release a standard characteristics collection has been added to Extendable Lookup. Extendable lookups may now be designed to capture additional information that may then be searchable by an algorithm or other internal process.

New CLOB Column Added

As previously delivered, the extendable lookup MO includes a standard CLOB column (BO_DATA_AREA) that is configured to be customizable. It means that if a product supplied an extendable lookup BO that defined additional information for each lookup value and supplied base values for the lookup with that additional information populated, an implementation could change the values of the additional information.

In this release, a new CLOB column has been added to the extendable lookup that is configured to not allow customization (BASE_BO_DATA_AREA). This allows product teams to define an extendable lookup BO that delivers base values and includes additional information that an implementation may not change.

For example, imagine a product defines a Contact Type extendable lookup that captures the addition information Priority and Allow Extension. In addition, imagine that the product supplied base values for the lookup and included delivered values for Priority and Allow Extension.

Code

Description

Allow Extension

Priority

Owner

C1-PHONE

Phone

Y

50

C1

C1-FAX

Fax

N

50

C1

C1-EMAIL

Email

N

10

C1

The design dictates that an implementation is allowed to change the Priority of the base record, but not the Allow Extension value. The design of the business object would look like this:

<lookupValue mdField="CONTACT_TYPE" mapField="F1_EXT_LOOKUP_VALUE"/>
<description mapField="DESCR"/>
<owner mapField="OWNER_FLG" dataType="lookup" lookup="OWNER_FLG"/>
...
<allowExtension mdField="ALLOW_EXT_SW" mapXML="BASE_BO_DATA_AREA"/>
<priority mdField="PRIORITY" mapXML="BO_DATA_AREA"/>

The Priority element is mapped to the customizable CLOB and the Allow Extension element is mapped to the non-customizable CLOB.

The following points should be noted about this functionality:

- An implementation may change the value of additional fields mapped to the customizable CLOB field (in the above example Priority). When upgrading to the next release of the product, the overridden value of Priority will be retained.

- An implementation may not change the value of additional fields mapped to the noncustomizable CLOB field (in the above example Allow Extension). A user will receive an error when attempting to change the value via the application. If the value is changed in some other way, when upgrading to the next release of the product, the product's value for the elements will be restored.

Note: At this time the error issued to a user attempting to change an element mapped to the non-customizable CLOB will reference the label of the physical column rather than the label of the element defined in the BO. Using the above example, the user will be told that you cannot change the value of Base BO Data Area rather than being told that you cannot change the value of Allow Extension.

- If allowed by the extendable lookup, an implementation may add new extendable lookup values and may define the values of all additional fields as necessary. (In the example, values for Priority and Allow Extension may be defined as appropriate.) Upgrade Note: As part of this enhancement, the base lookup values for the Schema - Element Types (F1-SchemaNodes) extendable lookup have been updated to define the values of the Property Control element in the noncustomizable column. This element may not be modifiable by implementations.

Override Description Visible in Extendable Lookup List

Extendable lookup supports an override description. In previous releases, if the override description was populated, it wasn't shown in the extendable lookup list zone. In this release, this has been fixed. The override description is now visible in the extendable lookup list zone.

Add Action Moved to Page Actions Area

In the previous release of the product, the Page Actions area was introduced and many portals adjusted their user interface to define the Add action in the page action area rather than as a hyperlink in the zone header. Extendable Lookup was not included in that update. In this release, the Add action for the extended lookup is now visible in the page actions area.

Validation Added to Several Base Extendable Lookups

In this release, several framework-owned extendable lookup business objects were enhanced to include a validation algorithm to issue an error if an implementation attempts to add a new lookup value. The functionality related to the extendable lookups does not support custom lookup values.

This was true in previous releases as well, but there was no validation preventing custom records from being added. (Any custom records that may have been added were simply ignored). In this release, the explicit validation has been included to avoid confusion.

The following table highlights the list of extendable lookups that do not allow custom lookup values.

Extendable Lookup Business Object

Description

F1-BooleanValues

Generic Boolean Values

F1-SchemaActionValues

Schema - Action Values

F1-SchemaBoolTrue

Schema - Boolean True

F1-SchemaBooleanValues

Schema - Boolean Values

F1-SchemaDataTypes

Schema - Field Element Data Types

F1-SchemaDefaultSysVariables

Schema - Valid System Variables

F1-SchemaDefaultTypes

Schema - Default Key

F1-SchemaDispNoneKey

Schema - Conditionally Hide Key

F1-SchemaDispNoneOperator

Schema - Condition Operator

F1-SchemaElementSuppress

Schema - Suppress Element

F1-SchemaElementVisibleOn

Schema - Element Visibility Control

F1-SchemaFlatFieldRowValues

Schema - Flattened Field Row Values

F1-SchemaFlatRowType

Schema - Flattened Row Types

F1-SchemaListOrderBy

Schema - List Order By Setting

F1-SchemaNodes

Schema - Element Types

F1-SchemaPageActions

Schema - Page Actions

F1-SchemaProtectKey

Schema - Protect Key

F1-SchemaSearchBy

Schema - Search By

F1-SchemaSectColumns

Schema - Section Column Display

F1-SchemaSelectKey

Schema - Dropdown Select Key

F1-SchemaXMLNameSpaces

Schema - XML Namespaces

Manual Transition of Sync Request

In a previous release, logic was added to support the ability for a user to manually transition a sync request that is currently in a state with a deferred monitor.

In this release, the action button that appears has been changed from Process Sync to Process Now.

Support Currency Symbol on Number Fields

Elements defined for unit rates typically capture amounts that have a large number of decimal places. The display of these amounts should include a currency symbol. These types of elements cannot be defined as money data types, because the amounts capture in money data types are validated against their currency's decimal configuration.

In previous releases, to display the currency symbol for these types of fields, special logic was required and automatic UI rendering was not possible. In this release, schemas may now define a currency reference for number data types. Automatic UI rendering will include the currency symbol of the referenced currency. The system ignores the currency decimal configuration.

Refer to the Schema Tips on the business object, business service, data area and service script pages for more information.

Web Service Enhancements

This section provides information about web service oriented enhancements.

Support XAI Service Deployment via Inbound Web Services

For implementations using XAI inbound services for external messages, the product recommends moving to the inbound web service mechanism, which uses the J2EE Web Application Server to communicate with the product rather than the XAI servlet.

In this release, the product supplies an interim solution for XAI inbound services that use the Core Adapter. These are XAI inbound services that reference an underlying page service in the product. For these services, converting them to use inbound web services requires a business service to be created for the underlying page service (if one doesn’t already exist). However, the resulting schema produces for a business service differs from the Request and Response schemas for the analogous XAI inbound service (which are created using the Schema Editor). This requires a change to the integration to cater for the deferent schema.
Moving all incoming messages over to use IWS instead of XAI is the product recommendation.
However, to aid in implementations that have many integrations in place using the XAI inbound services that use the Core Adapter (or any adapter whose message class is BASEADA), the product provides the ability to deploy these types of XAI inbound services to the J2EE Web Application Server along with the Inbound Web Services.

To take advantage of this capability, you must define a feature configuration option. Under the External Messages feature configuration type, the Support XAI Services via IWS is used to indicate if this feature is supported. Setting the value to true turns on the feature.

Note: Refer to "Support XAI Service Deployment via Inbound Web Services" topic in the External Messages chapter of the Public Sector Revenue Management Administrative User Guide for more information.

MDB in Inbound Web Service

In the last few releases, the Message Driven Bean (MDB) was included in the online server and interfacing into XAI. In an effort to isolate messaging traffic from online traffic for capacity management, the MDB has been moved to the same server as Inbound Web Services to establish an effort to create an integration server. The MDB has been updates to use IWS within the same server. The existing MDB will be supported in this transition.

Known Issues

Known Issues in This Release of PSRM

This section describes known issues in Public Sector Revenue Management (PSRM) Release 2.5.0.0.0, as well as known issues in required or related products that may impact PSRM functionality. Patches for these issues will be released at a later date.

Note: Some issues are isolated to a particular browser. They are listed in a special section accordingly. Issues that exist regardless of the browser are grouped by functional area.

Browser-Specific Issues

- In the Chrome browser, removing an overpayment from a refund control results in the error message "Overpayment Process ID is missing." [Bug 21277076]

- In the Arabic language, various incorrect behavior occurs on the Bill Type UI in IE and Firefox, including subsection headers being truncated, record action buttons not aligned to the right and not ordered from right to left, and the vertical scrollbar being on the right instead of on the left. [Bug 21497609]

Forms

- Opening an OPA decision report from the Tax Form Log brings up a blank window instead of showing the OPA decision report. [Bug 20704548]

- Some form lines that are not allowed to be changed based on the status of the form are editable. As such, that the user is able to change them but get an error upon save. [Bug 21505774)]

- In form type configuration, when defining a new form line in a recurring section (either limited or unlimited) the user is able to select a Related Form Field for that form line. That option should be disabled for lines in a recurring section. It is important to note that regardless of the UI behavior, the system will not allow lines under a recurring section to reference Related Form Fields, so this is mainly a cosmetic issue. [Bug 22273841]

- On a form where the form has deactivated sections/groups (i.e. the form type has sections or groups with logical deletion control set to enabled), the "Deactivated" label is not displayed. Additionally, the deactivated sections or groups are not shaded differently compared to non-deactivated sections or groups. [Bug 22698268]

Form Rules

- In the Rule Details section of the Conditionally Require Sections and Groups form rule (C1-CheckCondRequiredSectionGroup), required sections are excluded from the Section Name dropdown, preventing the user from setting groups under those sections from being conditionally-required. [Bug 21543164]

- In the Rule Variables section of the Conditionally Require Sections and Groups form rule (C1-CheckCondRequiredSectionGroup), the Form Line dropdown may not show the proper list based on the Rule Variable Type. While the list of applicable values may be different for each rule variable type, the list is retrieved only once -- on the first form line dropdown opened for the same form section. It is then reused for all other variables using the same form section regardless of rule variable type. [Bug 21543180]

- In a Calculation Line type of variable in a calculation rule eligibility criteria, the Calculation Line Category Value is not displayed on the display page. However, it is shown and editable on the maintenance page. [Bug 22644038]

- On a limited recurring section with a defined maximum of one (1) occurrence and for which logical deletion is allowed, multiple of such sections can be entered on the form without resulting in the expected over-the-limit validation error. [Bug 22108399]

- Validation of a form that has time and/or date-time form lines and whose form type has a Form Rule - Apply Rule algorithm based on the algorithm type Validate Form Using OPA Rulebase (C1-OPAVLAPRL) results in an "A java exception was thrown during OPA processing" error. [Bug 22721543]

Payments

- The Payment Event Upload - Process Payments (C1-PEPL2) batch process does not process payment event upload staging records in status "Audit" with multiple payments. [Bug 19456729]

- When deleting a payment from an unbalanced payment event, a "Concurrency Error" message can appear even though the payment has actually been deleted. When this happens, confirm that the payment was actually deleted by trying to retrieve the payment before proceeding. [Bug 22651996]

- In the Payment/Tender Search, the first row of the result set is hidden and cannot be selected. A possible workaround if there are multiple rows in the result is to sort the result differently such that the original first row entry shows up as the second or later row. [Bug 22668436]

User Interface

- There are various cosmetic-only UI issues such as misaligned labels, misaligned entry fields, etc., on various pages in the system. [Bugs 22578749, 22260018, 22543411, 22558063, 22570899, 22523387, 22298342, 22514899, 22272866, 22536923, 22310599, 22508612, 22493759, 22546533, 22578788, 22522832, 22558799]

- On the Tax Form page, there are no keyboard shortcuts for the action buttons. The workaround is to tab to the buttons and then press the Enter key. [Bug 22651046]

Geographic Data Validation

- Using the following for geographic data validation programs results in a "The server has encountered a problem" error:

- CIPZGTLX - Geo Val (Lat/Long) format validation

- CIPZGTTX - Geo Val (TRSQ) format validation

These are being deprecated.

In their place, use the Geographic Type - Value Format Rule algorithm type "Latitude/Longitude Format" (CIGEOTY-LL). [Bug 22652193]

OPA

- Generating the data area for a web service adapter for an OPA 10.4.4.21 rulebase (the supported OPA version for this release) results in the error, "Error reading Oracle Policy Automation rulebase zip". The workaround is to simply remove the Byte Order Mark (BOM) character from the rulebase XML. One way to do this is to open the file in an editor that allows specifying file encoding (e.g., NotePad++), change the encoding to one without BOM, then saving it. [Bug 19033157]

Workflow Management

- On the Case Type search page, selecting a case type from the search result set results in the error message, "System Error. Please see logs for more details." [Bug 22696034]

Audit

- Updates to BOs through BO Post Processing algorithms are not captured in audits. [Bug 12595973]

Application Viewer Generation

- Executing the Application Viewer - Extract Table Data (F1-AVTBL) and Application Viewer - Extract To Do Types (F1-AVTD) generation jobs results in NullPointerExeptions. [Bug 22651996]

Documaker Integration

- Currently, displaying customer contact/letter using Documaker integration does not work. [Bug 22606033]

Services

- Inbound Web Services, Web Service Annotation, and Web Service Annotation Types can be saved without a description. The impact is that without a description, these entities cannot be selected from the search as they will not have a hyperlink. Ensuring that all entries have descriptions will help avoid this issue. [Bug 22350066]

System Data

Some test data prefixed with "CM" were incorrectly shipped as part of base system data. This data will later be converted to become CM-owned and implementations can safely delete them if they choose to. The data is listed below. [Bug 21861417]

- CI_MD_FLD where FLD_NAME is:

- CM_AAREFUN_LINEITE_TOTALEX_0

- CM-INPUTLN01

- CM-INPUTLN02

- CM-INPUTLN03

- CM-OUTPUTLN01

- CM-OUTPUTLN02

- CM-OUTPUTLN03

- CI_SCR where SCR_CD is:

- CM-PVRCONCSS

- CM-PVRECHOSS

- F1_SCHEMA where SCHEMA_NAME is:

- C1-CRQPre - remove reference to schema element:

<includeBO name="ZZJI-CheckCondReqdSectionGrp2"/>

- SSiebelCreatePersonRequest

- SiebelCreatePersonResponse

- SR-FormRuleOPARequest

- SR-FormRuleOPAResponse

- F1_DATA_AREA where DATA_AREA_CD is:

- SSiebelCreatePersonRequest

- SiebelCreatePersonResponse

- SR-FormRuleOPARequest

- SR-FormRuleOPAResponse

- F1_BUS_OBJ_CD where BUS_OBJ_CD is

- CM-PersonIndividual

- CI_MD_ATT_TY where AT_NAME is

- zz6094543

- zzTest123

- CI_MD_PRG_COM where PROG_COM_ID is

- CMPQCMSGG

- CMPQPOPUP

General Development

- Displaying an object based on a BO whose data area was extended and where the extension has a start and an end section for UI hints results in an "Error 500 -- Internal Server Error". Note that this only affects CM objects, as the base product does not have data area extensions. [Bug 19366007]

Known Issues in OUAF 4.3.0.1 Not Fixed in This Release

The following table lists bug fixes released for previous versions of Oracle Utilities Application Framework that have not been included in this release. These fixes are planned for a future date for the current release using the listed bug numbers:

Original Bug

OriginalVersion

Description

4.3 Bug Fix

16418652

2.2.0

Printing zone outputs in portrait instead of landscape

21125562

20570324

4.2.0.1.0

Search window will not launch when ie 9 browser zoom set to 150% magnification

20570329

20402091

4.2.0.2.0

Back button 2x "forgets" selected query in query option list

21057709

20886978

4.2.0.2.0

Manual to do sort key defaulting not firing when post processing algorithm is plugged in

21647035

20914088

4.2.0.2.0

Label font color changed spacing displayed in Chrome

21903486

21209873

4.2.0.2.0

Query zones with filter UI Maps do not restore input filters with defaults configured

21210495

21104664

4.2.0.3.0

Label font color changed?spacing displayed in Chrome

21903486

21104765

4.2.0.3.0

Data grid shows extra column in Chrome

21294297

21243926

4.2.0.3.0

Filter values disappear on navigating back/forward in Chrome

21265682

21260161

4.2.0.3.0

Billable charge screen hangs on pricing info tab in Chrome

21287396

21304345

4.2.0.3.0

Link issue on account collection summary in Chrome

21339872

21308694

4.2.0.3.0

Label font color changed spacing displayed in Chrome

21308984

21355708

4.2.0.3.0

Orahandledependentdatetime function is not working for date time fields in list

21441766

Deprecation Notices

Deprecated Functionality in This Release

The following platforms and functionality are not supported by this version of Public Sector Revenue Management:

- Configlab: This has been superseded by the Configuration Migration Assistant (CMA) functionality that was available in previous versions of Public Sector Revenue Management.

- Archiving Engine (COBOL-based): This has been superseded by the Information Lifecycle Management (ILM) functionality that that was available in previous versions of Public Sector Revenue Management.

- COBOL-based Oracle Utilities Analytics extract programs: These have been superseded by new Extract – Load – Transform (ETL) modules based on Oracle GoldenGate/Oracle Data Integrator. Public Sector Revenue Management implementations using the COBOL-based modules must upgrade to Oracle Utilities Analytics version 2.5.1 and use the new ETL modules.

Deprecated Functionality Planned for Future Releases

The following functionality is planned to be deprecated in a future product version release:

- XAI Inbound Services: This has already been superseded by the Inbound Web Services functionality that that was available in previous versions of Public Sector Revenue Management.

For more information on migrating from XAI to IWS, refer to Migrating from XAI to IWS Oracle Utilities Application Framework (Doc ID 1644914.1) on My Oracle Support.

Demo Data Information

This application delivers a demo database based on the application versions provided with the release, including Oracle Utilities Application Framework. Demo data provides sample configuration and data for key application features. Please refer to the Database Administrator’s Guide for more information about installing the demo database, or contact Oracle Support.