Release Notes for Oracle Health Insurance Enterprise Policy Administration Release 3.21.1.0.0
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Release 3.21.1.0.0.
Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 3.21.1.x is only compatible with other Oracle Health Insurance applications release version 3.21.1.x unless explicitly stated otherwise. |
In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases. |
Enhancements
ID | Summary | Description | Included in Patch |
---|---|---|---|
NXT-18299 |
JET: Page Access Functions |
For JET pages, menu access is based on the function codes, and explicit resource level access is needed to be able to view/edit data. Example: Granting view access to function code FN0002, will enable menu item for message configuration. Now, for a user to search and view messages, explicit access must be granted to 'get' (view) messages resource. Explicit get (view) access must also be granted to all its sub resources. In the case of 'update' grants, all the linked resources must also have 'get' access for LOVs to work. With this enhancement, access to all the api/ip resources needed to operate the JET UI page will be granted implicitly by the system. This implicit api/ip access grant will follow the authorization level of the function access grant. For example, view only access grant to FN0002, will grant only GET access to generic resource /messages. Access to special operations like submitting a policy or a group client would require explicit authorizations to api/ip. The api/ip access that must be explicitly granted is specified in the user access section of the security guide. |
|
NXT-20012 |
HTTP Query API response only includes requested fields |
Before this release, HTTP API resources allowed for payload content customization through the expand and fields accept header parameter, however still some defaults were always included. |
|
NXT-20013 |
Allow traversing of more levels for referenced fields for Generic HTTP APIs |
Before this release, in HTTP API, only two levels of references from any resource level were allowed. All details were allowed at any level but the references were only allowed up until 2 levels. This restriction was put in place for not having memory pressures. It is seen from customer feedback and JET implementation that it can be restrictive sometimes, example being: claim→person→addressList→countryRegion→country→code. Since person is a reference from claim, it is only possible to go to addressList but not further. Allowing for more levels can still cause memory pressures if done for the entire object graph. The solution is to lift restrictions on certain references:
|
|
NXT-20490 |
Reporting views: Base view generator + specific IP |
The base view generator is now included into the OHI applications itself and can be triggered from the Base View Generation IP. This new base view generator is going to replace the existing (script based) view generator which is now deprecated and will be removed in a future release. |
|
NXT-20411 |
Configuration Migration: Flex Code Groups |
Flex Code Group is now available as a top level item in the configuration migration tool. |
|
NXT-20854 |
Improvements for Logging to the Database |
For logging to the database using the OHI Database Appender, the following capabilities are added:
|
|
NXT-20935 |
Display application version and enviroment tag in JET UI |
With this enhancement, the environment tag is added to application title. In addition, environment tag and application version are also added to the about dialog. The system property ohi.environment.identifier needs to be set in order to display the environment name in the application. |
|
NXT-21006 |
Add alternate user identifier and OAuth2-specific mapping to that user identifier based on OAuth token issuer; JWK Set token validation (RFC 7517) is now using OpenID Connect |
Some systems identify a user by a technical unique identifier that is not suitable to be displayed in user interface pages. With this enhancement, it is possible to use the User Provisioning IP to specify an alternate, unique user identifier (alternateUserIdentifier attribute), next to the existing loginName, for uniquely identifying and resolving users. This enhancement also allows configuration to map a specific claim in an OAuth2 access token to the OHI User based on the issuer of the token. Configuration for RFC 7517 token validation is now based on OpenID Connect. The properties for it have changed. The option to specify a local key store containing a set of public key certificates was removed. The easiest way to use JWK Set based token validation is to use the OpenID Discovery URI via system property "ohi.oauth.idp.uri" in combination with system property "ohi.oauth.jwk.set.validation.audience". Alternatively, set the following system properties if OpenID Discovery cannot be used:
For obtaining an Access Token using OpenID Connect, specification of the clientId and secret combination was changed.
|
|
NXT-21113 |
CMT : Floorplan |
Entity floorplan and floorplan tag details are added to the list of entities that are part of configuration migration. |
|
NXT-21203 |
Provider Identifiers |
This enhancement focuses on extending the ability to store one or multiple identifiers on a provider. These are used to identify the provider when processing claims and enrollment. |
|
NXT-21120 |
Additional Dynamic Fields for OHI Messages table |
The number of dynamic fields available on the OHI Messages table was too small. With this enhancement, the number of dynamic fields on OHI Messages table are extended to support the requirements. |
|
NXT-21306 |
Introduce the possibility to have aliases in fields/expand list |
With this enhancement, it is possible to use aliases in fields/expand section in Generic HTTP APIs. |
|
NXT-21384 |
Prevent CMT migration between different major versions |
Preventing Configuration Migration between a source and target environment that are not on the same major release. |
|
NXT-21397 |
Ability to confirm JET UI configuration before handover |
When a user with access to following API/IPs, logs in to JET UI, he ends up in the landing page without any menus (only the application banner & Sign Out are shown) to indicate successful login. API/IP access * User Information IP * Current Properties IP |
|
NXT-21831 |
CMT: Order of dynamic logic import |
Before this release, in CMT, the dynamic logic were imported in a random order (because they all have the same execution rank). With the introduction of two new signatures "Extension" and "Reusable Code", it is important and also possible that the dynamic logic are imported in an order to prevent look up failures while importing. With this enhancement, dynamic logic will now be imported in the following order of signatures: |
|
OIG-1366 |
Dynamic Logic Hooks/Extensions |
This enhancement make it possible to extend dynamic logic delivered as part of configuration by customers to provide their specific changes/extensions. This is enabled by introducing a new signature 'Extension' for all such extensions with a reference to the base dynamic logic that it is extending. At runtime, the application finds out all the extensions and invokes them. |
3.20.3.0.4 |
OIG-1369 |
Switching Off Delete by Omission for country packs |
This feature switches off the Delete by Omission functionality and allows to import the parent without deleting children in the Target Environment when importing CMT from Source Environment. This is done to support situations where the configuration is delivered and it only contains parent records, and the corresponding children are customer specific. |
|
OIG-1434 |
Dynamic Logic Framework should allow to use package statement in the logic |
Before this release the dynamic logic framework assumes all scripts to be written in a default package ohi.dynamiclogic. This is done to apply the security restrictions and to allow for logging only in scripts defined in the aforementioned package. This causes problems with reusability, as every logic that requires to use the reusable code, needs to append ohi.dynamiclogic before importing it. This makes it difficult to manage and test these groovy logic in isolation. On top of that, dynamic logic framework does not play well, if the package statement is explicitly included as ohi.dynamiclogic, as it appends another ohi.dynamiclogic in front of it. With this enhancement, it is possible to declare packages in the script and the framework will work with the package defined. It is however important, that the packages defined should start with ohi.dynamiclogic, otherwise security restrictions will be enforced. |
3.20.3.0.2 |
OIG-1445 |
Create Rest Service to generate objects and download them as zip |
Introduction of the Objects Integration Point to download the objects as a zip. This Objects Integration Point also introduces the capability to generate dynamic fields and records as just a plain key-value pair, to avoid having to regenerate these after every introduction of dynamic data. |
|
OIG-746 |
Build CMT Selective Migration Capabilities |
This enhancement allows for creating selective migration sets for CMT. With this enhancement, a new IP is introduced to create a selective payload and will also be utilised by JET UI to build the selective migration capabilities. However, this release does not contain JET UI screens |
|
POL-4478 |
SampleApplyPaymentRegistration API |
For the online portal for AU customers, they require the ability to calculate the impact on Date Paid To when an amount of money could be paid in the future. With this enhancement, it will be possible to send in sample registrations. The system will consider the impact of the sample payment and determine the new date paid to. A new integration point Sample Process and Apply Registrations to Periods is introduced. |
|
POL-4558 |
HTTP API - Policy toedit() HTTP Operation |
This enhancement introduces the ability to change the policy status from Approved, Cancelled or Pended back to Edit status through a new HTTP API operation toEdit. |
|
POL-5081 |
Configurable Address Types |
This enhancements makes the address type a configurable domain for relations. |
|
POL-5630 |
Schedule Definition Page |
This enhancement introduces JET UI page to define and manage schedule definitions. |
|
POL-5743 |
JET: Policies Page - Operations |
With this enhancement policy level operations are added to JET policy page. These operations include : 1) End Policy |
|
POL-5744 |
JET: Policies Page - New Policy |
With this enhancement possibility to create a new policy is added to JET UI. This enhancement also introduced a new view to see the "full" object without having to navigate to the detailed object page. This view is enabled for the policy page and group page. |
|
POL-5929 |
JET: Reference data - Agent, Broker and Bank pages |
Pages to maintain Brokers, Agents, and Banks are added to the application JET user interface |
|
POL-5979 |
JET : Edit Policy |
With this enhancement ability to "edit " policies is introduced. This includes the possibility to bring the approved or pended policy to edit status, change group account, change products, and update other policy settings. |
|
POL-5998 |
Parameter Domain Value Effective Dates |
This enhancement introduces time validity on parameter domain values to enable the validation of certain parameter values during given period in time. |
|
POL-6005 |
Unsend Financial Message |
This feature enables users to recover from a situation where the payload of the financial message is incorrect due to configuration errors and won’t be accepted by the destination as a result. The unsend financial message process brings the financial transactions in financial message back to a state that allows them to be reprocessed |
|
POL-6009 |
JET: Page - Collection Method and Capitation Contract |
UI Pages to maintain collection methods and capitation contracts are added to policy application |
|
POL-6169 |
Procedural Rounding |
This enhancement adds logic that calculates the last calculation period in a span (e.g. calendar month) as the net difference between the total (1) span period premium and the (2) sum of all calculated periods in that span prior to the last period. This calculation ensures that the summed premium for all separate calculation periods adds up to the exact span premium, regardless of how the periods are broken down and whether the respective premiums end in odd or even numbers. With this enhancements two attributes are added to policy calculation period, pcp span start date and pcp span end date. Generate Policy Calculation Period is modified to set PCP span start date and end dates to policy calculation period start and end date before any split a) by the system or b) within dynamic logic. PCPs are (re) generated through a number of operations/activities. The concept of pcp span dates applies irrespective of the operation/activity through which the PCPs are generated. {color} Additional step is added to Calculate Premium process to reconcile the last pcp split.
|
3.20.3.0.3 |
POL-6174 |
Extend Create Mutation IP to take Output Definition |
This enhancement focuses on extending the Create Mutation for a Policy IP to create mutations of type output. |
|
POL-6176 |
Include unpaid periods in regular billing cycle |
AU premium billing requires that if a period is not paid i.e. payment is missed, then that period should get recalculated with the next month’s premium bill run. For this purpose, the AU premium calculation activity is modified to recalculate all the missed periods. Missed periods are the ones having their pay date before the calculation input date and after the date paid to. |
|
POL-6178 |
Non-prorated Adjustment Functions |
This enhancement introduces the ability to control whether the amount that results from a function adjustment rule is automatically prorated or not, through configuration. |
3.20.2.0.5, 3.20.3.0.1 |
POL-6006 |
Preparation for upgrade to JET 9.0.0 |
JET Audit should be done and the critical/major issues needs to be fixed. Migration from knockout ojModule bindings to <oj-Module> JET custom component |
|
POL-6201 |
Policy In Data File Set Import |
This enhancement focuses on creating and updating a policy and its attached data from a single payload. It also supports batch interface since the volumes of these updates can become quite significant. |
|
POL-6203 |
Upgrade to JET 9.0.0 version |
Application upgrade to JET version 9.0.0 is done as part of this enhancement. FileUpload component changes, removal of deprecated public scss and OHI source is migrated to 9.0.0 |
|
POL-6481 |
Support for code generation in person and organization pages |
With this enhancement, the mandatory field validation on the client-side can be switched off for the properties that are required by API by setting property level attribute mandatory to false. Note, setting mandatory to false only suppresses client-side validations. This feature makes it possible to leave the code for the person and organization blank, so that it is set by code generation dynamic logic. |
|
POL-6508 |
Cancelling Policies with Non-Invoiced Financial Transaction Details |
Request for including the 'Calculate on Cancellation' Indicator in the Policy Integration Point. |
3.19.3.0.4, 3.20.2.0.5, 3.20.3.0.1 |
POL-6791 |
Scope on Surcharge on Premium Schedule Type |
Before this release, when a surcharge rule is set up to apply to the base premium (this is the SCHEDULE DEFINITION entity) then the percentage or function gets applied to the sum of the different premium schedules. This enhancement makes it possible for a more granular approach that enables the user to specify a premium schedule of type X so that the surcharge rule only takes in premium from schedules of type X as its input. |
3.20.3.0.4 |
POL-6794 |
Configurable Gender Types |
This enhancement creates the possibility to capture a person’s gender identity. Gender identity is a separate configurable entity. |
|
POL-6797 |
Dynamic Logic Framework should allow for reusable groovy classes to be created and used |
With this enhancement, dynamic logic framework allows for coding reusable classes to be reused as structures in other groovy scripts. This enhancement also introduces a new signature name for coding such reusable classes/scripts. The name of the signature is "Reusable Code" and does not have any specific bindings. |
3.20.3.0.2 |
POL-6845 |
Make Validation Rules, Callout Rules and Pend Rules top level migratable |
Before this release, Validation Rules, Callout Rules and Pend Rules were config migrated as part of process steps and rule steps. From this release Validation Rules, Callout Rules and Pend Rules can be migrated as separate top level items. |
|
POL-6869 |
Group Client Representative |
This enhancement adds a reference to an insurer’s representative to the group client. The group client representative is a person in the OHI relation model |
|
POL-6887 |
Re-structure Add-ons |
With this enhancement, the following entities are marked deprecated Add-on Premium Schedule Add-on Premium Schedule Line Group Account Product Overrides OHI recommends the use of Premium Schedules to calculate premiums for add-ons. A Condition can be attached to the schedule definition to check for the presence of an add-on on the policy, this way premium scheduled gets applied only when an add-on is present on the policy. In the subsequent release, an alternative setup will be introduced to link the premium schedules to add-ons. This will remove the need for condition dynamic logic. |
|
POL-7024 |
Jet UI group setup default page to show sub-groupclients based on system property |
Sub clients or group client hierarchy is not applicable to all customers. The customers that do not use hierarchy would like to hide the sub-client object navigation link. With this enhancement, the object navigation link is shown based on the system property settings. Setting the system property ohi.ui.showSubClientLink to true or false will toggle the display of the sub-client object navigation link. |
|
POL-7055 |
Jet UI: Better visuals for the 3 dots at group client screen |
The three dots icon in the view and edit page which is added to pages to denote additional possible actions is replaced with the "Action" button. |
Upgrade Steps for Installation
To perform the upgrade, perform the following steps:
-
Perform any pre-upgrade steps.
-
Stop all the managed nodes running the .existing version of the application.
-
Perform any pre-undeploy steps.
-
Undeploy the existing version of the application.
-
Back up the database.
-
Perform any post-undeploy steps.
-
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
-
Change Installation Configuration: In
<OHI_ROOT>/util/install
, make a copy ofohi_install.cfg.template
and name itohi_install.cfg
. -
Edit
ohi_install.cfg
to contain your specific database connection data and other configuration settings. The settings are explained in the file itself. -
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
-
Run the Upgrade script:
-
Open a command window and browse to
<OHI_ROOT>/util/install
. -
Run the upgrade by executing
./ohi-update.sh .
-
-
Make the required changes to the ohi properties file
-
Perform any post-upgrade steps
-
Start WebLogic application server
-
Deploy the Application
-
Perform any post-deploy steps
Additional Upgrade Steps for Installation
The following phases are defined:
|
To create a new read-only user that has access to the new Base Views run the following SQL script as a DBA user
grant connect, create synonym to ohi_policies_bvg_vws_user identified by &give_users_password;
Install the database patch for "Bug 30806757 - ORA-8103 when inserting into a new partition with is json constraint in place (Doc ID 30806757.8)". If that is not done and the "logging to the database" feature is enabled then this results in the following error: "Problem appending events for Log Type application|dylo java.sql.BatchUpdateException: ORA-08103: object no longer exists".
Configuration Properties
Ref | Action | Subject | Description |
---|---|---|---|
NXT-20490 |
Added |
ohi.baseview.generation.worker.count |
The number of worker threads to start for a base view generation process |
NXT-20854 |
Modified |
ohi.incident.datafileset.retentionperiod |
The property ohi.incidents.datafileset.retentionperiod is renamed to ohi.incident.datafileset.retentionperiod |
NXT-20854 |
Modified |
ohi.incident.target |
The property ohi.incidents.target is renamed to ohi.incident.target |
NXT-21006 |
Added |
ohi.oauth.openidconnect.accesstoken.client_id |
Client ID of the OpenID Connect client that has to be present to acquire an access token. |
NXT-21006 |
Added |
ohi.oauth.openidconnect.accesstoken.credential |
Credential associated with the OpenID Connect client that has to be present to acquire an access token. |
NXT-21006 |
Added |
ohi.oauth.openidconnect.accesstoken.validation.clockskew |
Defines the maximum acceptable clock skew (in seconds) for validating timestamps of ID tokens that are issued by an OpenID Provider. |
NXT-21006 |
Added |
ohi.oauth.token.issuers |
Comma-separated string of possible token issuers |
NXT-21006 |
Added |
ohi.oauth.token.issuer.{0}.user.claim |
Issuer-specific user claim |
NXT-21006 |
Added |
ohi.oauth.token.issuer.{0} |
Specific issuer identifier |
NXT-21006 |
Added |
ohi.oauth.jwk.set.validation.audience |
Client Id or audience claim for token validation. |
NXT-21006 |
Added |
ohi.oauth.jwk.set.validation.issuer |
Issuer for token validation. |
NXT-21006 |
Added |
ohi.oauth.jwk.set.validation.jws.signing.algorithm |
Signing algorithm used by the Authorization Server. |
NXT-21006 |
Removed |
ohi.oauth.jws.verification.key.selection.key_id |
|
NXT-21006 |
Removed |
ohi.oauth.jws.verification.key.selection.jws_algorithm |
|
NXT-21006 |
Removed |
ohi.oauth.jws.verification.key.selection.public_keys_only |
|
NXT-21006 |
Removed |
ohi.oauth.token.introspection.endpoint.client_secret |
|
NXT-21006 |
Removed |
ohi.oauth.jws.verification.key.selection.signing_keys_only |
|
NXT-21006 |
Removed |
ohi.oauth.jwk.publickey.keyid.source |
|
NXT-21006 |
Removed |
ohi.oauth.jwk.keystore.name |
|
POL-6201 |
Added |
ohi.service.POLICY_IMPORT.client.authentication |
If the notification endpoint is configured on the specific: POLICY_IMPORT, all other related properties like media type, authentication, etc. are also fetched based on POLICY_IMPORT, or else defaults are used. Similarly, if the endpoint for the notification is configured without the specific code, then all other properties are fetched on a generic use case code 'ActivityNotificationClient'. Please see section Outbound RESTful Service Invocations in Integration Guide for the process and more properties. |
POL-6201 |
Added |
ohi.policyimport.filereader.chunk.size |
A separate processing activity is spawned for processing a chunk or batch of policies of the specified size |
POL-6201 |
Added |
ohi.activityprocessing.notification.endpoint.POLICY_IMPORT |
A notification message can be sent out to a pre-configured endpoint. The notification endpoint can be configured on 'ohi.activityprocessing.notification.endpoint.POLICY_IMPORT' or to a more generic endpoint: ohi.activityprocessing.notification.endpoint. |
POL-6359 |
Added |
ohi.ui.logout.url |
The URL used by Oracle JET to actively logout a user (session). |
POL-6766 |
Added |
ohi.logging.phi.min.retentionperiod |
Minimal number of days for retaining PHI log events. |
POL-6766 |
Added |
ohi.logging.fileset.max.timespan |
Maximum time in days between start and end time for bundling log events in a file set. |
POL-7024 |
Added |
ohi.ui.showSubClientLink |
This property is used to show or hide sub-client object navigation link |
Web Services
Ref | Action | Subject | Description |
---|---|---|---|
NXT-20490 |
Added |
Base View Generation Integration Point |
New Integration Point |
NXT-21006 |
Modified |
Provisioning Integration Point |
Added alternateUserIdentifier: an alternate identifier, next to the loginName, for uniquely identifying a user |
NXT-21203 |
Modified |
Provider Integration Point, Claims Integration Point & Policy Integration Point |
This enhancement focuses on extending the ability to store one or multiple provider identifiers on a provider. |
OIG-1445 |
Added |
Objects Integration Point |
New Integration Point |
OIG-746 |
Added |
Configuration Migration Integration Point |
New Integration Point (part of Dataexchange) |
POL-4478 |
Added |
Sample Process and Apply Registrations Integration Point |
New Integration Point |
POL-4558 |
Added |
Edit Policy Integration Point |
New Integration Point |
POL-5081 |
Modified |
Relation IP and API |
Added new attribute addressTypeCode |
POL-6201 |
Added |
Write Policies Long Running Operation |
Data file set import option to handle multiple policies in one go |
POL-6201 |
Modified |
Policy In Integration Point |
Now includes attached data in its payload |
POL-6508 |
Modified |
Policy In Integration Point |
Included 'calculateOnCancellation' property in the IP |
POL-6747 |
Modified |
Quote Integration Point |
An optional query parameter "billingCycle" is added. |
POL-6794 |
Modified |
Relations IP and API |
new attribute genderIdentityCode |
POL-6869 |
Modified |
Group Client Integration Point |
Included 'representativePersonCode' attribute in the IP. |
Data Conversion
Ref | Action | Subject | Description |
---|---|---|---|
POL-5081 |
Table change event rule fields updated |
Change event rules on address that are using field 'type' are updated to 'addressType'. This is applicable for Policies application only. |
|
POL-5081 |
Address |
The foreign key reference to Address Type is set with the following values: |
|
POL-5998 |
Parameter Domain Value Start Date |
The new start date is copied from the earliest relevant time period. If none exists the date defaults to 2000-01-01 |
|
POL-6169 |
Policy Calculation Periods |
For all the existing policy calculation periods, if there exists a contract period that spans over policy calculation period start date and end date then the contract start and end date are copied to policy calculation period span dates otherwise the policy calculation period start and end dates are copied to policy calculation period span start date and policy calculation period span end date respectively. |
Dynamic Logic
Ref | Action | Subject | Description |
---|---|---|---|
OIG-1366 |
Added |
Dynamic Logic Signature |
Introduced a new signature with name "Extension" |
POL-5081 |
Modified |
Dynamic logic using address.type |
'type' attribute of Address is replaced by 'addressType'. Accessing type attribute on address is deprecated and will not be supported in a future release. |
POL-6797 |
Added |
Dynamic Logic Signature |
Introduced a new signature with name "Reusable Code" |
UI Changes
Ref | Action | Subject | Description |
---|---|---|---|
NXT-20490 |
Added |
Record Definitions page |
New indicator PII? |
NXT-20490 |
Added |
Tables page |
New indicator PII? |
NXT-21113 |
Modified |
Config Migration Sets (ADF) |
Added option to select floorplan while creating a migration set |
NXT-21113 |
Modified |
Floorplans page |
Added floorplantagdetails tab |
OIG-1366 |
Modified |
Dynamic Logic Page |
Added Base dynamic logic. This is done for both UI (ADF and Jet) where applicable. |
POL-5630 |
Added |
PO0004 Schedule Definitons |
Schedule Definitions page added with 5 floorplans |
POL-5743 |
Modified |
Policies page |
End Policy, End Enrollment, Change Products, Change Group, Generate Fee/Output and other operations added |
POL-5744 |
Modified |
Policies page |
A new view for the recursive page will be available to the users i.e. expanded view. This view will allow the user to access all the sub-pages on a single page i.e. all the recursive pages will be loaded as part of the main page. With this enhancement the users will have the ability to create complex objects like policies on a single page rather than navigating to recursive pages and back. |
POL-5744 |
Modified |
Policies page |
Added the custom JET properties for Policy enrollment product namely, enrollmentProductJET, addOnJET, parameterAliasJET, parametersUnitsJET, parametersAmountJET, parametersPercentageJET and parametersDaysJET which can be configured in the floorplan in context of policy enrollment product to get enrollmentProduct/GroupAccountProduct and their respective addOn and parameterAlias. |
POL-5929 |
Added |
Agents, Brokers, Banks |
Added Agents, Brokers and Banks pages |
POL-5979 |
Modified |
Policies page |
Create, Edit, Delete functionality introduced in policies page. Refresh, Cancel policy and toEdit policy operations added |
POL-6009 |
Added |
Collection Methods, Capitation Contracts |
Added Collection method and Capitation contract pages |
POL-6178 |
Modified |
Adjustment Rules Page, Surcharge Rules Page, Setup Enrollment Product |
Add Not Prorated option for adjustment rules and surcharge rules |
POL-6794 |
Added |
Gender Identities, Address Types |
Added Gender Identities, Address Types |
POL-6794 |
Modified |
Persons, Organizations |
Added Gender Identities and address types lovs in persons and organizations page |
POL-6845 |
Modified |
Configuration Migration Sets |
Validation Rules, Callout Rules and Pend Rules are top level migratable in CMT page |
POL-7024 |
Modified |
Group Clients |
SubClients link is shown or hidden based on system property ohi.ui.showSubClientLink |
Deprecated items (to be removed in future release)
Ref | Action | Subject | Description |
---|---|---|---|
NXT-20490 |
Reporting Views |
The reporting views as generated by the runnable jar are now deprecated. |
|
POL-5081 |
Dynamic logic using address.type and generic API on address |
'type' attribute of Address is replaced by 'addressType' |
|
POL-6201 |
getAttachedData pre defined method |
The pre defined method getAttachedData() on Policy object (this was not documented in the guide before, but was visible in "View Objects" page) is deprecated. Please use getAttachedPolicyData() method (or attachedPolicyData property) on Policy object instead. |
|
POL-6887 |
Add-ons |
The following entities are marked deprecated Add-on Premium Schedule OHI recommends the use of Premium Schedules to calculate premiums for add-ons. A Condition can be attached to the schedule definition to check for the presence of an add-on on the policy, this way premium scheduled gets applied only when an add-on is present on the policy. In the subsequent release, an alternative setup will be introduced to link the premium schedules to add-ons. This will remove the need for condition dynamic logic. |
Breaking Changes
Ref | Action | Subject | Description |
---|---|---|---|
NXT-20854 |
Modified |
ohi.incident.datafileset.retentionperiod |
The property ohi.incidents.datafileset.retentionperiod is renamed to ohi.incident.datafileset.retentionperiod |
NXT-20854 |
Modified |
ohi.incident.target |
The property ohi.incidents.target is renamed to ohi.incident.target |
NXT-21384 |
Removed |
Migration behaviour |
Migration between different major versions wont be possible anymore. |
POL-5081 |
Modified |
Generic API search on address.type |
This should be replaced by address.addressType.code |
POL-5998 |
Added |
Group Client IP/Generic API |
Start date of parameter domain value is mandatory |
POL-7051 |
Modified |
Generate Policy Calculation Periods |
Generated Policy Calculation Periods which are split by the ohi.policies.calculate.calculationperiods.splitoncalendarmonth now keep the reference date from before the split. |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
31026326 |
3-22595519361 |
POL-5160 |
Sort Dynamic Records not working |
|
Description: |
Not able to sort dynamic records. |
|||
Resolution: |
Dynamic Records can be sorted from the floorplan configuration. |
|||
31332343 |
3-23028770758 |
POL-5522 |
Group account product adjustment list sort is not working |
|
Description: |
Group account product adjustment list sort is not working The floor plan for group account product, has a tab for adjustment. This tab is supposed to be ordered by sequence, schedule definition and start date. But the order does not work. The EXPECTED result / functionality: The order should be applied using the system specific floorplan and/or custom ones. |
|||
Resolution: |
Group account product adjustment list sort is now working as expected. |
|||
31605031 |
POL-5936 |
Display:Never property is not working while configuring floorplans |
||
Description: |
When the display was set to never for a field, still able to see the field in create/edit pages but it doesn’t show up in view mode. If the display is set to never then it should not be visible in create/edit mode either. |
|||
Resolution: |
Display property when given "never" will not be shown in UI in create, view and edit modes. |
|||
31899037 |
3-24004133661 |
POL-6269 |
Data Dynamic Records not visible in 'Update Attached Data' screen. |
|
Description: |
The Dynamic records on the 'Update Attached Data' screen were not visible on the 'Update Attached Data' screen. They were visible only after clicking on the Collapse Bar. |
|||
Resolution: |
Data Dynamic Records are now available in 'Update Attached Data' screen. |
|||
31569361 |
POL-5683 |
Sorting arrow icon(asc/desc) is not displaying for Sort Component. |
||
Description: |
Sort functionality is working but sorting arrow icon(asc/desc) is not displaying for Sort By drop down component |
|||
Resolution: |
Changes were made to CSS to show the sorting arrow icon. |
|||
31569609 |
POL-5827 |
Data is being cleared off when Save and Next is perfomed in Group Setup pages |
||
Description: |
When user click on "Save and Next" button, pre-populated data is not getting loaded in group setup pages. |
|||
Resolution: |
Now 'Save and Next' button will retain the group client detail in create Sub Clients and create Group Account page while navigating from View Edit Group Client page. |
|||
32008365 |
POL-5904 |
Syntax error message is thrown, when user try to apply the json data in the collapse mode |
||
Description: |
Syntax error message is thrown when user tries to 'apply' changes by collapsing the JSON rows in the Payload field of floorplans page |
|||
Resolution: |
User can successfully 'apply' changes even by collapsing the JSON rows in the Payload field of floorplans page |
|||
31605063 |
POL-5937 |
Not able to save data for dynamic records if it have mandatory fields. |
||
Description: |
User is not able to save the page after filling the mandatory record, when an empty row is added on tab out of the multi-value dynamic records. |
|||
Resolution: |
Now user is able to save the page successfully after filling the mandatory record when an empty row is added on tab out of the Multivalue dynamic records. |
|||
31605084 |
POL-5938 |
Remove option on dynamic record should delete the latest created dynamic record |
||
Description: |
Remove option on dynamic record is deleting the first row instead of the newly created dynamic record in group client page. |
|||
Resolution: |
Now the dynamic record on the Group Client page which was created last is removed instead the first one on selection of remove option. |
|||
31642228 |
POL-5990 |
Resource needs to be removed from quick search for floorplans page |
||
Description: |
Need to remove resource as a search criteria from JET floorplans page. Floorplan seed data should have a reference to resource. |
|||
Resolution: |
Resource is removed from quicksearch in Floorplan page. |
|||
31914350 |
POL-6309 |
Running an example calculation with an incorrect year throws a technical error in the UI |
||
Description: |
When running an example calculation in the UI and entering an outlier date (01/01/20212) the application shows the following error in the UI: GEN-PROC-ERR: An error occurred in processing the request |
|||
Resolution: |
Running example calculation with an incorrect year throws the correct OHI exception now. |
|||
31978132 |
POL-6359 |
Generic JET UI bug: unable to specify a logout URL |
||
Description: |
User is not able to specify the logout URL. |
|||
Resolution: |
Now two new properties, "ohi.ui.logout.url" and "ohi.ui.webgate.logout.url" have been introduced. If "ohi.ui.logout.url" is set then its value will be used by default. Otherwise depending on the authentication method either "ohi.security.oauth.logout" or "ohi.ui.webgate.logout.url" will be used. The former will be used if its either "OAuth" or "OpenId", whereas the latter will be used if its "WebGate". |
|||
31977686 |
3-24100051731 |
POL-6387 |
Group account or enrollment products are not loaded in premium bill allocations tab, when an extra space is added at the end of group client code. |
|
Description: |
Group Account or Enrollment Products field values were not getting loaded under Premium bill allocations Tab if any extra spaces are added at the end of Group Client code. |
|||
Resolution: |
Group account and enrollment products field values are loaded even when extra spaces are added at the end of group client code. |
|||
32014151 |
POL-6461 |
All tab data is getting cleared off on entering invalid data |
||
Description: |
On entering one/more rows of data with an invalid entry all tab data is cleared off instead of showing error and highlighting the invalid field as expected. |
|||
Resolution: |
Now even on adding multiple rows in a given tab page, the field with error is highlighted and error is shown without the tabs being removed. |
|||
32016170 |
3-24224226281 |
POL-6467 |
Predefined method setGroupClientStatus() not available on group client details |
|
Description: |
Predefined method setGroupClientStatus() is not available on group client details. As a result, when a new group account product is loaded into OHI for an existing group, the status of the group cannot be set the CHANGED. This is needed in order to signal the member accounting representative that the billing accounts should be manually reviewed. The same holds true for predefined method addGroupClientEvent() |
|||
Resolution: |
Methods on the group client are now available from change event dynamic logic on the group client details. |
|||
32040831 |
3-24102792951 |
POL-6496 |
Premium Bill Allocation for Group Account disappears when the screen is reopened |
|
Description: |
Data entered in tab Premium Bill Allocation for Group Account disappears when the screen is reopened. |
|||
Resolution: |
Data entered in tab Premium Bill Allocation for Group Account shows as expected when the screen is reopened. |
|||
32071898 |
POL-6536 |
The link generated for functiondynamiclogic in the metadata of adjustment rules API is not working |
||
Description: |
The link generated for functiondynamiclogic in the metadata of adjustment rules API is not working |
|||
Resolution: |
The link for sub-resources returned by the metadata for adjustment rules API is fixed now |
|||
31984248 |
3-24129263161 |
POL-6394 |
Schedule definition indicator 'Fatal if not found' not working for adjustment |
|
Description: |
Message POL-FL-CAPR-022 did not occur if Indicator 'Fatal If Not Found' is set to 'Y 'and adjustment rule does not exist for the retrieved adjustment type. |
|||
Resolution: |
If the indicator 'fatal if not found' is set to true and adjustment rule does not exist for the retrieved adjustment type, the message POL-FL-CAPR-022 will now be raised. |
|||
31984820 |
POL-6397 |
Process and Apply Registrations to Periods operation is not working properly when there is a positive and negative registration present in the system with same payDate and same amount |
||
Description: |
Process and Apply Registrations to Periods operation was not setting correct Date Paid To when there was a positive and negative registration present in the system with same payDate and same amount |
|||
Resolution: |
Process and Apply Registrations to Periods operation, Run Calculation and Produce Invoice for a Policy operation (AU Localization, when system property indicates that the registrations should be applied to the periods), Run Calculation and Produce Sample Invoice for a Policy operation (AU Localization, when system property indicates that the registrations should be applied to the periods) and Apply Registrations to Periods long running operation now work as expected in the following scenario:
|
|||
32012424 |
3-23808997781 |
POL-6457 |
Override on group account adjustment not getting applied correctly |
|
Description: |
When "Reference Date Field Name" was specified on schedule definition (of type Adjustment/Group Adjustment), the adjustment override (if configured) was not getting applied correctly. |
|||
Resolution: |
When "Reference Date Field Name" is specified on schedule definition (of type Adjustment/Group Adjustment), the adjustment override (if configured) is now applied correctly. |
|||
32014185 |
POL-6460 |
Unable to navigate to view-edit page after performing edit operation |
||
Description: |
When Edit action was performed on any HRR page, the changes were saved, but the page did not display the Confirmation message and did not get re-directed to View mode again |
|||
Resolution: |
When Edit action is performed on any HRR page and the changes are saved, the page displays the Confirmation message and gets re-directed to View mode again |
|||
32014536 |
POL-6464 |
AU: Run calculation and produce invoice for a group account - process registration is executed for all policies |
||
Description: |
This activity selects all applicable policies instead of processing the policies belonging to the group account this activity is started for. |
|||
Resolution: |
The activity Run Calculation and Produce Invoice for a Group Account (AU) was picking up new, applicable, registrations of all policies: this has now been changed to: 1) only pick up registrations that belong policies to that group account (i.e. do not end before the look back date parameter). 2) uncorrelated new registrations are not picked up any more. This will only be verified when the process registrations activity is run. Also, in that activity, only uncorrelated new registrations of type PAYMENT are checked and new registrations without correlation id will be included. |
|||
32073602 |
3-24368499541 |
POL-6542 |
Dynamic Logic exception: Restricted method invocation |
|
Description: |
When accessing the object returned by the JSON slurper, the application raises an exception. |
|||
Resolution: |
The new version of Groovy packaged with the application returns a Lazymap object from the JSON slurper. Access from Dynamic Logic to objects of this type was not permitted, this has now been changed. |
|||
32107632 |
3-24407466171 |
POL-6628 |
JET UI: Boilerplate text are missing for group clients messages. |
|
Description: |
Boilerplate text related to group client messages page is not getting displayed. |
|||
Resolution: |
Now boilerplate text related to Group client messages are translated and proper texts are now visible in the application. |
|||
32109099 |
3-24387668271 |
POL-6631 |
AddParameterValue and AddPolicyAddOn methods are not shown for PolicyEnrollmentProduct in View Objects page |
|
Description: |
PolicyEnrollmentProduct dynamic logic uses addParameterValue and AddPolicyAddOn method. It already works fine in the UI. However, when someone searches for these methods in OHI View Objects page, these can not be found. |
|||
Resolution: |
AddParameterValue and AddPolicyAddOn are both added to the list of methods of a PolicyEnrollmentProduct in the View Objects page. |
|||
32128599 |
POL-6647 |
Relation formatted name is not rendered correctly in UI pages, when configured in combination of prefix, provider title and Person title. |
||
Description: |
Relation formatted name is not rendered correctly in UI pages, when configured in combination of prefix, provider title and Person title. |
|||
Resolution: |
Now Relation formatted name is rendered correctly in UI pages, when it is configured in combination of prefix, provider title and Person title. |
|||
32137306 |
3-24377974061 |
POL-6715 |
Group Account "CALCULATE_PRODUCE_INVOICE" activity , should contain links to Data file in the activity notification. |
|
Description: |
Group Account "CALCULATE_PRODUCE_INVOICE" activity , do not have the links for data file in activity notification. |
|||
Resolution: |
Data file links are now available in "Run Calculation and Produce Invoice for a Group Account" activity notification when the activity is completed. |
|||
32139470 |
3-24424977911 |
POL-6716 |
OHI policies throwing 500 error for changeeventrules endpoint with expand all |
|
Description: |
When attempting to expand the header of the changeeventrules endpoint, the HTTP error 500 occurs. |
|||
Resolution: |
The changeeventrules endpoint will now expand all fields instead of throwing a Null Pointer Exception. |
|||
32150213 |
3-24500949741 |
POL-6743 |
Exception occurred when user selects value to the column level multivalue flex code. |
|
Description: |
When the user selects a value from the LOV for a multivalued flex code column, null pointer exception was thrown and error page was displayed. |
|||
Resolution: |
A value can now be selected from the LOV for a multivalued flex code column. |
|||
32102289 |
POL-6583 |
OUTGOING NOTIFICATIONS DOES NOT CONTAIN CORRELATIONID COMING IN THE REQUEST HEADER OF LONG RUNNING PROCESS |
||
Description: |
Outgoing Notifications does not contain correlationId coming in the request header of Long Running operations like applyregistrations and processregistrations long running operation. |
|||
Resolution: |
The correlationId passed in the request header will now be sent in the outgoing notifications of long running operations apply registration and process registrations. |
|||
32107909 |
3-24068646251 |
POL-6630 |
Some Business validation errors not handled correctly in UI leading to unexpected exception |
|
Description: |
When some business validation occurs, UI throws exception and was not handled. So it navigates to the standard error page instead of displaying validation message |
|||
Resolution: |
Business validation messages are shown properly and user is not redirected to standard error page. The message 'The server is unable to respond' does not show anymore for business rule violations |
|||
32480984 |
POL-6632 |
Authorization is not working in processandapplyregistrations operation when the policy is restricted by a data access group restriction |
||
Description: |
If the access to a policy is restricted by a data access group restriction, then to perform processandapplyregistrations operation on that policy also a grant for that data access group restriction must be provided with the Update flag set. But this is not working. |
|||
Resolution: |
Authorization is now working in processandapplyregistrations operation when the policy is restricted by a data access group restriction. |
|||
32464115 |
POL-6747 |
Quote IP returns incorrect calculation date with policy calculation periods |
||
Description: |
|
|||
Resolution: |
The optional "billingCycle" query parameter is now added to Quote IP, so it works just like example calculation: if not specified, then no billing cycle is used. Also collection method code is included now. Changes on Quote IP and example calculation with respect to PCP generation:
|
|||
32157299 |
3-24491372481 |
POL-6748 |
CALCULATE_PRODUCE_INVOICE activity completes successfully, but the notification received on premium/commission end point has status as "Failure" |
|
Description: |
Even though the "Run Calculation and Produce Invoice for a Group Account" activity completes successfully, the notification received on premium/commission end point has "Failure" status. |
|||
Resolution: |
In the following use cases, the status in the data file notification now correctly reflects the status of the activity:
With this bug fix, the order of the links in the data file notification has changed. |
|||
32165073 |
3-24498375181 |
POL-6769 |
THE CHILD ACTIVITY GENERATE_FIN_MSG_XML OF "RUN CALCULATION AND PRODUCE INVOICE FOR A GROUP ACCOUNT" ACTIVITY SHOWS BOTH PREMIUM AND COMMISSION DATA FILE SET CODES IN UI. |
|
Description: |
In "Run Calculation and Produce Invoice for a Group Account" activity, two different financial transaction sets are created (one for premium and one for commission). So, two different child activities GENERATE_FIN_MSG_XML are created. The child activity for premium adds an activity message (ACT-FL-DAFI-001) with the code the data file set containing financial messages of premium and the child activity for commission adds an activity message (ACT-FL-DAFI-001) with the code the data file set containing financial messages of commission. However, in the ADF UI, both the child activities (GENERATE_FIN_MSG_XML) show both the messages. |
|||
Resolution: |
now the generate financial message activity (premium) will show message related to data file for premium and generate financial message activity (commission) will show message related to data file for commission. |
|||
32175178 |
POL-6786 |
Group Hierarchy tree view is not rendered, when we have group client and group account having similar IDs |
||
Description: |
There is chance of having group clients and group accounts with similar IDs in the application, as ID is unique only to that particular entity. Since ID is used as the keyAttribute for nodes in tree view, system failed to render if there were group clients and group accounts with similar IDs. |
|||
Resolution: |
User will now be able to view and access group hierarchy tree view in all possible scenarios, even when group clients and group accounts have similar ids. |
|||
32203361 |
POL-6838 |
Unable to add and open billing accounts in Group Clients page |
||
Description: |
User is unable to add billing accounts after creating a new group client. It gives exception and user is also not able to open billing accounts |
|||
Resolution: |
User is now able to add billing account after creating new Group Client. |
|||
32262179 |
POL-6908 |
GENERATE_FIN_MSG_FLAT_FILE activity doesn’t send data file notification |
||
Description: |
GENERATE_FIN_MSG_FLAT_FILE activity doesn’t send data file notification |
|||
Resolution: |
The activity "Generate Financial Message (Flat File)" now correctly sends data file notification. |
|||
32542897 |
POL-6909 |
Fee and produce invoice notification does not have link to datafiles |
||
Description: |
Fee and produce invoice notification does not have links to data files |
|||
Resolution: |
Added the links to download the data files in the notification of fee and produce invoice activity |
|||
32173705 |
POL-6779 |
Parameter Domains details page is not displayed based upon the condition under Enrollment Products Page |
||
Description: |
Parameter Domains details page is not displayed based upon the selected condition under enrollment Products page of Enrollment sub-menu in configuration menu. |
|||
Resolution: |
Parameter Domains condition under Parameter Domains tab of Enrollment products has been removed as it is no longer required. |
|||
32265155 |
POL-6982 |
Relation identifiers not included in data replication |
||
Description: |
Relation identifiers need to be included in the replication of person data from Policies. |
|||
Resolution: |
Relation identifiers are included in the replication of person data from Policies. |
|||
32342962 |
3-24690688341 |
POL-7074 |
Calculate premium activity fails to select valid collection setting when multiple collection settings with collection method exist |
|
Description: |
Calculate premium activity fails to select valid collection setting when multiple collection settings with collection method exist. The issue happens when there are negative offsets on calculationDate. |
|||
Resolution: |
Calculate premium activity now selects a valid collection setting when multiple collection settings with collection method exist. |
|||
32344210 |
3-24455989661 |
POL-7080 |
Sample invoice API is not setting the pay date of the PCPs generated as part of its process to system date. |
|
Description: |
The pay date of all PCPs generated by sample invoice API must be set to system date automatically. |
|||
Resolution: |
The pay date is now correctly set for all PCPs generated by sample invoice API. |
|||
32462421 |
POL-6917 |
An error occurs when user tries to save the LOV value without selecting from the search results |
||
Description: |
The error occurs when user tries to save the LOV value without selecting from the search results. If the user doesn’t select any value, the value does not get saved. |
|||
Resolution: |
If the user wants to select a value from an LOV, then they must enter the complete value of the LOV and press Enter key. This will pick the first value from the search results of LOV. |
|||
32319347 |
POL-7051 |
Reference date of Policy Calculation Periods is set incorrectly when PCP is split due to splitoncalendarmonth property set to true |
||
Description: |
When Policy Calculation Periods are generated and split because of the ohi.policies.calculate.calculationperiods.splitoncalendarmonth property, the reference date was set to start date of each split PCP. |
|||
Resolution: |
When Policy Calculation Periods are split due to the ohi.policies.calculate.calculationperiods.splitoncalendarmonth property, the reference date is now copied from PCP before split. |
|||
32260104 |
3-24691193221 |
POL-6975 |
If indicator 'Fatal if no line found' enabled for surcharge, error POL-FL-CAPR-021 is showing when it should not show |
|
Description: |
The message POL-FL-CAPR-021 for no matches on surcharges is shown when indicator 'Fatal If No Line Found' is enabled on schedule definition, even if there are matches. This could happen when surcharge of both types of evaluation ('OnPremium', 'AfterAdjustment') were valid for a period and one of them had this indicator enabled. The cause was selecting and evaluation of all surcharges, regardless of type of evaluation. So when premium was calculated for step 'Surcharge on premium', surcharge definitions with evaluation type 'After Adjustment' were included also. |
|||
Resolution: |
The premium calculation is adjusted for surcharges: only select surcharges that are applicable for the step. So for step 'Surcharge on premium', only surcharges with evaluation type 'On Premium' are included in selection. And for step 'After adjustment', only surcharges with evaluation type 'After Adjustment' are selected. |
|||
32311146 |
3-24762710318 |
POL-7042 |
After updating/patching the application, the disabled seeded floor plans are enabled again |
|
Description: |
It is allowed to disable the seeded floor plans (through the application). However, after upgrading/patching the application, the changes made to the enabled indicator are reverted. |
|||
Resolution: |
The changes made to enabled indicator of seeded floor plans are now preserved after upgrading/patching the application. |
|||
32312638 |
3-24777871611 |
POL-7045 |
Default sort is not working correctly under billing accounts tab in group client page |
|
Description: |
When user clicks on billing accounts the corresponding billing account details are not populated correctly in group client pages. |
|||
Resolution: |
Now user is able to get the billing account details correctly based upon the selection. |
|||
32316141 |
3-24704227441 |
POL-7053 |
JET UI - Policies details page show different enrollment start date |
|
Description: |
When the timezone is in GMT(negative) values, Policies details page show different enrollment start date in JET UI. |
|||
Resolution: |
The start date field in Policies page Enrollment section shows the date in sync with DB/ADF screen values |
|||
32334682 |
3-24738743651 |
POL-7068 |
Dynamic records not exported in excel |
|
Description: |
When user tries to export Dynamic column value using export excel option from Adjustment types section, Dynamic column values are not displayed. This issue exists in Premium Scheduled lines screen as well. |
|||
Resolution: |
Dynamic record columns will now be listed in excel. |
|||
32344774 |
3-24806255191 |
POL-7082 |
Percentage based adjustment is not applied to a base premium of zero |
|
Description: |
When the base premium is configured as zero and if two adjustments are configured - the first adjustment (with sequence 1) with amount and the second adjustment (with sequence 2) with percentage, then the second adjustment is not applied (on base premium + amount from the first adjustment). |
|||
Resolution: |
Percentage based adjustment is now correctly applied to a base premium of zero. |
|||
32463982 |
POL-7290 |
Getting exceptions while running SampleInvoice IP or Invoice IP if trace logging is enabled |
||
Description: |
NPE was thrown while running SampleInvoice IP or Invoice IP if trace logging is enabled for calculatePremium packages |
|||
Resolution: |
When trace is enabled for calculatepremium package(s), these exceptions no longer occur when premium is calculated (with calculate premium activity, example calculation etc.) |
|||
32465220 |
3-24868305941 |
POL-7297 |
APPLY_REGISTRATIONS activity and processandapplyregistrations operation doesn’t work properly during policy edit |
|
Description: |
When a new enrollment is added, a policy event with effective date as start date of policy enrollment product is not getting handled by apply reg activity and process and apply reg operation. After edit of the newly added policy enrollment product then running apply reg and process and apply reg operation, there are 2 issues.
|
|||
Resolution: |
The lookBackDate in processandapplyregistrations operation is now correctly set, so the Date Paid To is not moved up. |
|||
32468880 |
POL-7302 |
Task is stuck in 'PROCESSING' status if the node leaves the cluster |
||
Description: |
When the node processing a task leaves the cluster or if the node is stopped while the task is being processed, then the task remains in 'PROCESSING' status. The other nodes in the cluster should recover/re-queue that task. |
|||
Resolution: |
When a node leaves the cluster, then the tasks that are currently being processed by that node are now recovered by the other node(s) in the cluster. |
|||
32485751 |
3-25008194831 |
POL-7342 |
BP |
Create time valid dynamic records for policy enrollments without start date |
Description: |
The dynamic record related business validations were not done for policy enrollments. |
|||
Resolution: |
The business rule validations related to policy enrollments will now be triggered and correct error message will be sent e.g. GEN-DYNA-010 for start date |
|||
32488127 |
POL-7355 |
Unable to query policy enrollments on person.relationIdentifierList.identifier |
||
Description: |
Generic HTTP API search on <child>.relation(+)relationIdentifierList.identifier.like("123â€) gave error: For example on policyenrollments: api/generic/policyenrollments?q=person.relationIdentifierList.identifier.like("123â€) |
|||
Resolution: |
When a search is done on a relation child, like policy enrollments, addresses, using relationIdentifierList, this search is now properly executed. |
|||
32491018 |
3-25130257641 |
POL-7362 |
Label objects displays the field value when it should not display |
|
Description: |
Configure labels in floorplan without any values. It should not be displayed in UI |
|||
Resolution: |
Labels for which no values are present in floorplans will not be displayed under labels section. |
|||
32508924 |
3-25179866201 |
POL-7408 |
BP |
NullPointerException when original PCP is segmented due to a change which results in two discounts within same month |
Description: |
If the PCP is segmented on a time valid flex code dynamic field, which is used as a dimension on adjustments, then the run example calculation returns a NullPointerException which is not expected. |
|||
Resolution: |
The NullPointerException will not be raised any more. |
|||
32518989 |
3-25196339551 |
POL-7433 |
BP |
Input amount of non-prorated adjustment function in the last PCP is incorrect |
Description: |
When system is configured with two adjustments of different types (one being % adjustment and other being non prorated function adjustment scoped on one of the premium schedule) and having the same sequence, then input amount of non-prorated adjustment function in the last PCP is incorrect. |
|||
Resolution: |
The correct input amount is passed to the non-prorated function dynamic logic now. |
|||
32523871 |
POL-7436 |
BP |
Reference sheet import element datatype is not registered in all the nodes of cluster |
|
Description: |
Reference sheet Import element datatype is not registered in all the nodes of cluster. |
|||
Resolution: |
Reference sheet lines are now being imported successfully in multi-nodes cluster setup. |
|||
32535752 |
POL-7480 |
Premium calculation activity fails when partial add-on is configured on policy enrollment product |
||
Description: |
Premium calculation activity fails for the last policy calculation period split when partial add-on is configured on policy enrollment product. |
|||
Resolution: |
The NullPointerException is not raised any more. |
|||
32477354 |
POL-7316 |
CMT process hangs if interrupted and does not allow running any new CMT process |
||
Description: |
When CMT fails, the job was stuck within the database which prevented the user from running another CMT. |
|||
Resolution: |
The resolution was mostly done on transactional grounds of the cleanup services. Post the resolution, if CMT process is interrupted due to any reason, it can be started again. |
|||
32454121 |
3-24415907166 |
POL-7282 |
Error while adding Adjustments in Enrollment Products screen |
|
Description: |
When a adjustment having amount type schedule dimension is added to the existing adjustments of the enrollment product, the page gets navigated to previous screen while saving the record |
|||
Resolution: |
Adjustment type can be selected and save successfully. |
|||
32477342 |
POL-7317 |
Adjustment Rules API and Premium Schedule Lines API are returning incorrect location header |
||
Description: |
Adjustment Rules API and Premium Schedule Lines API were returning incorrect location header |
|||
Resolution: |
Adjustment Rules API and Premium Schedule Lines API are now returning correct location header with id of AdjustmentRule/PremiumScheduleLine that is created |
|||
32453643 |
3-25013086391 |
POL-7279 |
NullPointerException when accessing new entity’s attributes in "Change Event Rule (Effective Date)" dynamic logic |
|
Description: |
When PATCH operation is used on policies API to add a new dynamic field and if a change event rule is configured that monitors for an update on the dynamic field, NullPointerException is thrown when accessing the new entities (like bind variable newPolicy) attributes (like code) in "Change Event Rule (Effective Date)" dynamic logic. |
|||
Resolution: |
It is now possible to add a new dynamic field/record using PATCH and have a reference to all attributes on the new entity (like newPolicy when applicable) in "Change Event Rule (Effective Date)" dynamic logic. |
Issues that were backported in previous Release / Patch
BugDB | Internal | Summary | Backport | BugDB | SR |
---|---|---|---|---|---|
31605063 |
POL-5937 |
Not able to save data for dynamic records if it have mandatory fields. |
3.20.3.0.2 |
32043259 |
|
31605084 |
POL-5938 |
Remove option on dynamic record should delete the latest created dynamic record |
3.20.3.0.2 |
32029520 |
|
31978132 |
POL-6359 |
Generic JET UI bug: unable to specify a logout URL |
3.20.2.0.4 |
31953227 |
|
31984248 |
POL-6394 |
Schedule definition indicator 'Fatal if not found' not working for adjustment |
3.20.3.0.1 |
31984340 |
3-24129263161 |
32012424 |
POL-6457 |
Override on group account adjustment not getting applied correctly |
3.20.3.0.1 |
32038063 |
3-23808997781 |
32014185 |
POL-6460 |
Unable to navigate to view-edit page after performing edit operation |
3.20.3.0.1 |
32018031 |
|
32014151 |
POL-6461 |
All tab data is getting cleared off on entering invalid data |
3.20.3.0.2 |
32018001 |
|
32016170 |
POL-6467 |
Predefined method setGroupClientStatus() not available on group client details |
3.20.3.0.1 |
32016178 |
3-24224226281 |
32073602 |
POL-6542 |
Dynamic Logic exception: Restricted method invocation |
3.20.3.0.1 |
32073611 |
3-24368499541 |
32107632 |
POL-6628 |
JET UI: Boilerplate text are missing for group clients messages. |
3.20.3.0.1 |
32107670 |
3-24407466171 |
32107909 |
POL-6630 |
Some Business validation errors not handled correctly in UI leading to unexpected exception |
3.20.3.0.2 |
32113625 |
3-24068646251 |
32107909 |
POL-6630 |
Some Business validation errors not handled correctly in UI leading to unexpected exception |
3.20.2.0.6 |
32113631 |
3-24068646251 |
32137306 |
POL-6715 |
Group Account "CALCULATE_PRODUCE_INVOICE" activity , should contain links to Data file in the activity notification. |
3.20.3.0.2 |
32142921 |
3-24377974061 |
32137306 |
POL-6715 |
Group Account "CALCULATE_PRODUCE_INVOICE" activity , should contain links to Data file in the activity notification. |
3.20.2.0.6 |
32142904 |
3-24377974061 |
32139470 |
POL-6716 |
OHI policies throwing 500 error for changeeventrules endpoint with expand all |
3.20.3.0.1 |
32139494 |
3-24424977911 |
32150213 |
POL-6743 |
Exception occurred when user selects value to the column level multivalue flex code. |
3.20.2.0.6 |
32150222 |
3-24500949741 |
32150213 |
POL-6743 |
Exception occurred when user selects value to the column level multivalue flex code. |
3.20.3.0.2 |
32150219 |
3-24500949741 |
32157299 |
POL-6748 |
CALCULATE_PRODUCE_INVOICE activity completes successfully, but the notification received on premium/commission end point has status as "Failure" |
3.20.3.0.2 |
32164935 |
3-24491372481 |
32157299 |
POL-6748 |
CALCULATE_PRODUCE_INVOICE activity completes successfully, but the notification received on premium/commission end point has status as "Failure" |
3.20.2.0.6 |
32164979 |
3-24491372481 |
32165073 |
POL-6769 |
THE CHILD ACTIVITY GENERATE_FIN_MSG_XML OF "RUN CALCULATION AND PRODUCE INVOICE FOR A GROUP ACCOUNT" ACTIVITY SHOWS BOTH PREMIUM AND COMMISSION DATA FILE SET CODES IN UI. |
3.20.3.0.2 |
32170121 |
3-24498375181 |
32165073 |
POL-6769 |
THE CHILD ACTIVITY GENERATE_FIN_MSG_XML OF "RUN CALCULATION AND PRODUCE INVOICE FOR A GROUP ACCOUNT" ACTIVITY SHOWS BOTH PREMIUM AND COMMISSION DATA FILE SET CODES IN UI. |
3.20.2.0.6 |
32170146 |
3-24498375181 |
32175178 |
POL-6786 |
Group Hierarchy tree view is not rendered, when we have group client and group account having similar IDs |
3.20.3.0.2 |
32250908 |
|
32262179 |
POL-6908 |
GENERATE_FIN_MSG_FLAT_FILE activity doesn’t send data file notification |
3.20.3.0.2 |
32257783 |
|
32262179 |
POL-6908 |
GENERATE_FIN_MSG_FLAT_FILE activity doesn’t send data file notification |
3.20.2.0.7 |
32257797 |
|
32462421 |
POL-6917 |
An error occurs when user tries to save the LOV value without selecting from the search results |
3.20.3.0.4 |
32251691 |
|
32316141 |
POL-7053 |
JET UI - Policies details page show different enrollment start date |
3.20.3.0.3 |
32323892 |
3-24704227441 |
32342962 |
POL-7074 |
Calculate premium activity fails to select valid collection setting when multiple collection settings with collection method exist |
3.20.3.0.3 |
32343015 |
3-24690688341 |
32342962 |
POL-7074 |
Calculate premium activity fails to select valid collection setting when multiple collection settings with collection method exist |
3.20.2.0.8 |
32343080 |
3-24690688341 |
32344210 |
POL-7080 |
Sample invoice API is not setting the pay date of the PCPs generated as part of its process to system date. |
3.20.2.0.8 |
32344254 |
3-24455989661 |
32344210 |
POL-7080 |
Sample invoice API is not setting the pay date of the PCPs generated as part of its process to system date. |
3.20.3.0.3 |
32344226 |
3-24455989661 |
32344774 |
POL-7082 |
Percentage based adjustment is not applied to a base premium of zero |
3.20.2.0.8 |
32353927 |
3-24806255191 |
32344774 |
POL-7082 |
Percentage based adjustment is not applied to a base premium of zero |
3.20.3.0.4 |
32355762 |
3-24806255191 |
32453643 |
POL-7279 |
NullPointerException when accessing new entity’s attributes in "Change Event Rule (Effective Date)" dynamic logic |
3.20.3.0.4 |
32453673 |
3-25013086391 |
32463982 |
POL-7290 |
Getting exceptions while running SampleInvoice IP or Invoice IP if trace logging is enabled |
3.20.3.0.4 |
32463996 |
|
32465220 |
POL-7297 |
APPLY_REGISTRATIONS activity and processandapplyregistrations operation doesn’t work properly during policy edit |
3.20.3.0.4 |
32465266 |
3-24868305941 |
32468880 |
POL-7302 |
Task is stuck in 'PROCESSING' status if the node leaves the cluster |
3.20.3.0.4 |
32468894 |
3-24901222791 |
32477342 |
POL-7317 |
Adjustment Rules API and Premium Schedule Lines API are returning incorrect location header |
3.20.3.0.4 |
32477351 |
|
32488127 |
POL-7355 |
Unable to query policy enrollments on person.relationIdentifierList.identifier |
3.20.3.0.4 |
32488144 |
Known Issues
BugDB | SR | Internal | Summary |
---|---|---|---|
24345001 |
POL-1140 |
ACCESS: When 200% zoom is applied, vertical scroll is not available |
|
Description: |
Vertical scroll is not available when 200% zoom is applied |
||
24345062 |
POL-1143 |
ACCESS: The Close tab 'X' icon is not accessible while doing keyboard testing |
|
Description: |
The Close tab 'X' icon is not accessible while doing keyboard testing |
||
24345143 |
POL-1153 |
ACCESS: Initial focus should be on the first menu item (top left) |
|
Description: |
On the home page, if the user clicks tab from the Url, the focus should shift to the top left (first menu item) of the application. |
||
24763164 |
POL-1292 |
ACCESS: Alt Text for Add Row is missing in Enrollment Products tab |
|
Description: |
Alt Text associated with the image 'Add Row' is missing for Enrollment Products tab in Setup Group Account |
||
25155957 |
POL-1381 |
ACCESS: All the read only fields are labelled as edit in view only sections |
|
Description: |
In the view only section,all the column value labels contain text 'edit'. |
||
25173763 |
POL-1393 |
ACCESS: Documentation testing - Rows without headers |
|
Description: |
Table summary is missing as there are rows without headers. |
||
25173741 |
POL-1394 |
ACCESS: Documentation testing - No Alt text foufn for the images |
|
Description: |
ALT text is missing for all the images in the document. |
||
25173787 |
POL-1395 |
ACCESS: Jump to line functionality of JAWS does not work in the application |
|
Description: |
Jump to line functionality of JAWS to enable user to navigate to specific line/attribute based on it unique number doesn’t work in screen reader mode. |
||
25173869 |
POL-1396 |
ACCESS: CTRL+INS+I - List Items shortcut does not work in the application |
|
Description: |
Shortcut to display a list of policies does not work. |
||
25180978 |
POL-1407 |
ACCESS: Document testing - Graphic images are not detected by JAWS |
|
Description: |
JAWS doesn’t identify the images due to missing labels |
||
25180997 |
POL-1408 |
ACCESS: Document testing - The page address link is read as page title |
|
Description: |
Instead of the application name, address link of the page is read as page title |
||
25182941 |
POL-1413 |
ACCESS: Error messages are not accessible and not read in Screen Reader mode |
|
Description: |
Error messages are not accessible and not read in Screen Reader mode |
||
29033394 |
POL-3416 |
UI : Page freezes when the splitter of the detail table is resized with touch screen featured enabled |
|
Description: |
In pages where there are splitters e.g.: Premium Schedule page, the page freezes when the splitter position is moved up/down in Chrome. |
||
29021620 |
POL-3512 |
ACCESS: System error 'Ensures headings have discernible text' in the 'policies search' page |
|
Description: |
System error 'Ensures headings have discernible text' in the 'policies search' page. |
||
30950008 |
POL-3762 |
In contract period based calculation, the reconciliation is not performed on the level of the distributed result for distributed surcharges |
|
Description: |
In contract period based calculation, the reconciliation is not performed on the level of the distributed result for distributed surcharges |
||
29945042 |
POL-4173 |
ACCESS: No documenation to define Accessibility and compatibility features |
|
Description: |
JET provides info that should be included in the accessibility chapter of any product built with it, there should be documentation to define Accessibility and Compatibility Features. |
||
30055390 |
POL-4283 |
ACCESS: Advanced Search box is not accessible in Firefox browser |
|
Description: |
Advanced Search Box is not accessible in Firefox browser. It works fine in Chrome Browser. |
||
31386237 |
POL-5526 |
ACCESS: Save status messages are not conveyed through screen reader |
|
Description: |
Assistive technology (JAWS) does not convey the information of the status messages. |
||
31386285 |
POL-5532 |
ACCESS: Additional information displayed on hovering over links is not accessible. |
|
Description: |
Additional information displayed by hovering over links is not accessible. |
||
31386299 |
POL-5533 |
ACCESS: Not able to access menu items with 300% zoom |
|
Description: |
Not able to access menu items with 300% zoom |
||
31390487 |
POL-5575 |
ACCESS: Id attribute value should be unique on search page |
|
Description: |
Id attribute value should be unique on search page |
||
31390490 |
POL-5586 |
ACCESS: Landmarks must have a unique role or role/label/title combination |
|
Description: |
Landmarks must have a unique role or role/label/title combination |
||
31390497 |
POL-5587 |
ACCESS: Not able to access gear icon with LOV using keyboard on create group client page |
|
Description: |
This issue is present when accessing any LOV through keyboard. |
||
31488557 |
POL-5701 |
ACCESS: Application does not support portrait mode |
|
Description: |
Only landscape mode is supported currently. |
||
31817255 |
POL-5867 |
Group Client Status - In Process step issue |
|
Description: |
When changing Group Client status from Changed to Approve, the intermediary InProcess status is displayed & page refreshes to display Approved status |
||
31667107 |
3-23278718221 |
POL-6023 |
Could not load content for jsep.min.js.map |
Description: |
SourceMappingUrl allows debugging of minified and bundled source code. This url is incorrectly generated for a third party library jsep, due to which its original source code cannot be loaded by the browser. Warning in console DevTools failed to load SourceMap: Could not load content for /js/jsep.min.js.map;: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE |
||
31677490 |
POL-6029 |
Filter Component not working when configured with String and LOV fields |
|
Description: |
Create a search Floorplan configured with Filter component with String and LOV fields. Search the results based upon the above created floorplan. Filter component should be rendered with the configured fields but it is not working as expected |
||
31713227 |
POL-6086 |
Error on the Object Detail page is not as per the specifications. |
|
Description: |
Error on the Object Detail page is not as per the specifications. Expected functionality is: "Error(s) found, changes are not saved" message should be shown at the object level and 'Show All' link should be displayed next to it. |
||
32019608 |
POL-6473 |
Unable to render custom LOV floorplan in custom floorplan based page |
|
Description: |
Custom LOVs are not rendered in Custom floorplan based pages and application gives error |
||
32071912 |
POL-6537 |
In enrollment product / group account product adjustment rules operation, when the payload contains only "id" of the dynamic logic, it seems it is ignored and only "code" works |
|
Description: |
In the enrollment product / group account product adjustment rules operation, the overrideFunctionDynamicLogic and overrideFunctionDynamicLogicNotProrated cannot be sent in id of the dynamic logic as it is ignored for IPs. Only when code is ent in, it works. |
||
32205987 |
POL-6846 |
Error message is not getting displayed, when the user doesn’t have access to the floorplan in enabled status. |
|
Description: |
Create a custom floorplan based upon the role. Log in to the application with user who didn’t have the specified role for that custom floorplan. Expected functionality is that an error message should be displayed to the user but custom floorplan is rendered. |
||
32415583 |
3-24941428911 |
POL-7232 |
Not able to display person address list in the policy enrollment floorplan |
Description: |
Not able to display person address list in the policy enrollment floorplan. Two level of references from any resource are supported. User should be able to customize any floorplan for the same. |
||
32476995 |
POL-7315 |
With clicking Next button dialog button not refreshed |
|
Description: |
In Popup dialogs, Next and previous button doesn’t work due to refresh issue. |
||
32477645 |
POL-7319 |
No base view generated for reference sheet lines |
|
Description: |
Reference sheet(line)s use a different storage structure (JSON) for the dynamic fields. The base view generator does not support that yet. So the reference sheet line columns can’t be queried using base views. |
||
32500910 |
POL-7387 |
Dynamic Logic is not validated during the process and apply registrations operation |
|
Description: |
When the system property ohi.policies.calculate.calculationperiods.dynamiclogic is set to an unknown value, the operation does not raise the POL_VL_CAPR_005 exception (unknown dynamic logic). A similar argument applies when invalid Dynamic Logic parameters are included in the payload, but in this case it throws an NullPointerException. |
||
32510826 |
POL-7397 |
Getting NPE while creating relationIdentifier by passing relation code in payload instead of relation id |
|
Description: |
When sending in the wrong payload relation/person or omitting relation/person, a null pointer exception is raised for the following entities:
For example, sending in the following payload to relationidentifiers API results in NullPointerException instead of GEN-ORA-01400 (column is mandatory for table).
|
||
32514322 |
POL-7424 |
Input amount column in calculation result lines table populates incorrect amount for few components of last PCP |
|
Description: |
Input amount column in calculation result lines table populates incorrect amount for few components of last PCP |
||
32525582 |
POL-7445 |
Usage names with a reserved SQL word results in view generation failure |
|
Description: |
A usage name like "level" (which is a SQL reserved word) results in a failure in the view generator for the table where this usage is used. |
||
32529412 |
POL-7464 |
Adjustment calculated is incorrect when combination of scoped and non scoped adjustments are configured at sequence two |
|
Description: |
Adjustment calculated is incorrect when combination of scoped and non scoped adjustments are configured at sequence two |
||
32536681 |
POL-7482 |
Registration import IP activity ends up in technical error when an invalid data file set is send in |
|
Description: |
When, for instance, an empty data file is part of the set, or no data file are part of the set, the activity ends up with status Technical Error, while it should end up with Business Error. |
||
32566946 |
POL-7511 |
Enrollment products custom property - system shows group account products instead of enrollment products. |
|
Description: |
When user try to edit policy and add end date to the group account ( group account is updated in the same transaction as the next steps are performed) and add a new enrollment/enrollment product with the start date that is after the group account end date then system shows group account products instead of enrollment products. |
||
32548976 |
POL-7528 |
Adjustment overrides page is not loading the details for enrollment product and group account product |
|
Description: |
Adjustment overrides page is not loading the details for enrollment product and group account product |
||
32557634 |
3-25277596251 |
POL-7539 |
Incidents raised from activity are not stored in data files table if ohi.incident.target is set to datafileset |
Description: |
If the property ohi.incident.target is set to datafileset and when a technical/unexpected error (eg: IndexOutOfBoundsException) occurs when executing the activity, the incident is not written to the data files table. |
||
32567212 |
POL-7572 |
Configure ohi.resource.client.timer Resource Tag construction |
|
Description: |
For gathering metrics, it must be possible to control the resource tag for an "ohi.resource.client.timer" to point to the name of the resource (and not be more specific than that). The new described property ohi.instrumentation.resourceclienttimer.segment.prefixes is not available yet |
||
32572064 |
POL-7575 |
java.lang.IndexOutOfBoundsException is raised from APPLY_REGISTRATIONS activity when multiple registrations (including refund) present with the same payDate |
|
Description: |
java.lang.IndexOutOfBoundsException is raised from APPLY_REGISTRATIONS activity when multiple registrations (including refund) present with the same payDate. This happens when:
- an exact payment was sent in and applied |
||
32572105 |
3-25277596251 |
POL-7576 |
java.util.NoSuchElementException if policy holder start date is after policy enrollment product start date |
Description: |
java.util.NoSuchElementException is raised if policy holder start date is after policy enrollment product start date in case of policy based premium. If there is no policy holder as of the reference date, the premium should be calculated for the oldest enrolled person on the policy. |
||
32573800 |
POL-7581 |
Baseview generation sometimes might result in error: ORA-01461 |
|
Description: |
Occasionally baseview generation results in error: ORA-01461. In the event that this happens, typically resubmitting the generation process resolves the problem. |
||
32573943 |
POL-7582 |
User is able to update the enabled atribute of an identifier even after not having the update access |
|
Description: |
For both provider and relation identifiers it is not possible to update the identifier itself when a user is not having update access, however it is possible to update other attributes, like enabled and/or dynamic fields/records. This should not be allowed. |
||
32574170 |
POL-7583 |
Some logfilesetspecifications stay on specified status |
|
Description: |
If no log messages are applicable for the specified logfilesetspecification, the logfilesetspecification stays on S(pecified), and no error is present. Also specifications with status S are not cleaned. The required fields of logfilesetspecifications generic resource metadata show following not required fields: errorMessage, fileSetStatus and dataFileSet. The x-oi-meaning for logType shows "null" |
||
32585341 |
POL-7590 |
Run and produce Invoice for a group account / Run Calculation and Select in Set for a Group Account activities are not replacing periods as expected |
|
Description: |
Run and produce Invoice for a group account / Run Calculation and Select in Set for a Group Account activities are not replacing periods as expected for unpaid periods. |
||
32585709 |
POL-7615 |
Attributes returned from API as readonly are not rendered as readonly fields in UI. |
|
Description: |
Attributes returned from API as readonly are not rendered as readonly fields in UI for Policy attach data page. |
||
32590381 |
POL-7637 |
Expanded view of billing allocation tab in group client page hang up by showing busy state icon in firefox. |
|
Description: |
Expanded view of billing allocation tab in group client page hang up by showing busy state icon in firefox. |
||
32591010 |
POL-7640 |
In ADF UI, Getting errors in policy creation, persons/organization pages when default address type is not configured in system. |
|
Description: |
In ADF UI, while creating a new policy if no default address types configured, system is giving error "CacheLoader returned null for key DefaultAddressType" on select address station. Also getting errors in persons/organization pages when default address type is not configured in system |
||
32592016 |
3-25196339551 |
POL-7647 |
Adjustment result amount is incorrect in the last split PCP if the adjustment with a lower sequence is not applicable in the last split PCP |
Description: |
If two adjustments (scoped on TotalPremium) are defined with different sequence, in the last split PCP, the result amount for the adjustment with a higher sequence is incorrect if the adjustment with a lower sequence is not applicable (for example, if the adjustment with a lower sequence ends one day before the start date of the last split PCP). |
||
32616411 |
3-25407851131 |
POL-7684 |
Titles are not getting saved in Persons page |
Description: |
In persons page adding, updating or removing titles is not getting reflected after 'Save' |