Release Notes for Omni-Payer™ Version 1.6.x > Omni-Payer™ Management Central

Omni-Payer™ Management Central

Topics:

This section provides release notes that are applicable for Omni-Payer™ Management Central (OPMC) in Version 1.6.x.

For more information on installing and using OPMC, see the following documentation:

New Features and Updates

Topics:

This section lists and describes new features and updates for OPMC in Version 1.6.x.

Version 1.6.0

  • Changes to maintain compatibility with Omni-Payer Version 1.6.0.
  • Implemented optional removal of clear text passwords for WSO2 Admin, database connections, and SMTP server by enabling password encryption.
  • Corrected two stage MCO operations including scenarios where a data steward resolves a ticket, the ticket is reassigned to a data supervisor, and the supervisor approves or rejects the remediation.
  • Several minor bug fixes and correction to actions that previously resulted in sporadic Error 500 occurrences.
  • Other minor bug fixes.

Version 1.6.1

  • International character support for double byte and UTF-8 formats in RemediationServices.
  • Authorization policies improvement to accommodate complex assignment requirements.
  • ReasonCode/ReasonDescription field protection throughout the ticket lifecycle for enhanced tracking.
  • ActivityToday panel re-engineered to reflect the states dynamically for improved usability.
  • Option to embed components within the WebFOCUS Portal.
  • Usability enhancements for WSO2 policies.
  • MData performance enhancements.
  • Customer fixes:
    • 160701047 - Option to embed components within the WebFOCUS Portal.
    • 160707085 - 400 Error handling enhancement.
    • 160628032 - Assigning and reassigning of cases for data steward.

Known Issues and Considerations

This section describes known issues and considerations for OPMC in Version 1.6.x.

Cleansing (When Adding a Comment to a Field)

Note: As released in RemediationService Version 1.3.0 - 0624.

When a user wants to add a comment on a specific (non-empty) field, the following workaround is required to prevent the replacement of data with empty values:

  1. Select the field to which a comment is to be added.
  2. Note the value of the attribute to which the comment is being added.
  3. Enter (type) the comment.
  4. Click the check mark.
  5. In the edited column (now blank), enter the original value of the attribute on the Instance Record (the value noted in Step 2).
  6. Click the check mark.
  7. Click the drop-down, select Resolve Direct, and then click Submit.
  8. Refresh the page.

    The new comment and value are persisted and can be displayed.

Automatic Transfer of Roles in WSO2 Administration

Note: This process should not be required and should not be performed under normal circumstances.

If the administrator adds a new user ID to the WSO2 PRIMARY domain, and that user ID already exists in an LDAP domain, then all of the existing Roles of the LDAP user are automatically transferred and enabled to the PRIMARY/user ID profile. Before updating the new user ID, examine, confirm, and then edit the Roles (Authorizations) as required that you are about to grant to this duplicate user ID.

Upgrading From Omni-Payer™ Version 1.6.0 to Version 1.6.1

Topics:

This section describes the process to upgrade from an existing installation of Omni-Payer™ Version 1.6.0 to Version 1.6.1.

From a high-level, upgrading Omni-Payer™ Version 1.6.0 to Version 1.6.1 requires the following steps, which are each described in more detail in this section.

  1. Updating the WSO2 Identity Server (IS) policies.
  2. Replacing the workflow subdirectory.
  3. Updating the WAR files.
  4. Manually updating MData.

Step 1: Updating the WSO2 IS Policies

To update the WSO2 IS policies:

  1. From Policy View, delete the following policies if they already exist:
    • Authorize-user-dashboards-policy
    • Authorize-user-reesignissue-policy
    • Authorize-user-usercanacceptassign-policy
    • Component-access-manuitem-policy
  2. From Policy Administration, delete the following policies if they already exist:
    • Authorize-user-dashboards-policy
    • Authorize-user-reesignissue-policy
    • Authorize-user-usercanacceptassign-policy
    • Component-access-manuitem-policy
  3. From Policy Administration:
    1. Click Add New Entitlement Policy.
    2. Click Import Existing Policy.
    3. Import the following policies from the install folder:
      • Authorize-user-dashboards-policy
      • Authorize-user-reassignissue-policy
      • Authorize-user-usercanacceptassign-policy
      • Component-access-menuitem-policy
  4. After importing the policies, click Publish to My PDP for each policy that was imported.
  5. From Policy View, click Enable for each policy that was published to My PDP.
  6. Stop and start the WSO2 IS server.

Step 2: Replacing the Workflow Subdirectory.

To replace the workflow subdirectory:

  1. Open the omnigen_home directory.
  2. Navigate to the \workflow subdirectory.
  3. Rename the existing \workflow subdirectory (for example, \workflow_160).
  4. Copy the new \workflow subdirectory from the Omni-Payer™ Version 1.6.1 installation.

Step 3: Updating the WAR Files.

To update the WAR files:

  1. Copy the new (1.6.1) version of the opmc.war file to the \webapps subdirectory.
  2. Copy the new (1.6.1) version of the RemediationService.war file to the \webapps subdirectory.
  3. Copy the new (1.6.1) version of the OmniDomain.war file to the \webapps subdirectory.

Step 4: Manually Updating MData.

To manually update MData:

  1. Implement the attribute name correction (from issueFiterSectionsCount to issueFilterSectionsCount).
    1. From the Administration section, click the Settings tab.
    2. Navigate to the existing issueFiterSectionsCount attribute and delete this entry.
    3. Configure a new entry for the issueFilterSectionsCount attribute, as shown in the following image.
  2. Navigate to the Wftickets table and click Edit.
    1. Navigate to My Cases Filter View.

      Exclude the id field if it is currently included.

      Exclude the idUseAssignedr field if it is currently included.

    2. Navigate to All Cases Filter View.

      Exclude the id field if it is currently included.

  3. Navigate to the Wfcases table and click Edit.
    1. Edit the My Cases Filter View and All Cases Filter View to include only the currentState, caseType, and documentName fields. In addition, the idUser field must also be included in the All Cases Filter View.

      All other fields should be removed.