Rules and Behaviors - Expression data deleted when clicking the Save and Close button on the Rules and Behaviors > Rule Summary Rule Information page.

(Doc ID 2103692.1)

Last updated on SEPTEMBER 25, 2017

Applies to:

Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.

Symptoms

MetaSolv Solution version 6.2.1

Actual Behavior

The Expression data that defines the condition(s) that must be met for the rule behavior(s) to initiate is deleted when clicking the 'Save and Close' button on the Rules and Behaviors > Rule Summary Rule Information page even if there were no changes to the Name, Description or Active Indicator fields.  The images below demonstrate the behavior.  Note the Rule Description was changed, but not necessary.



Expected Behavior

The Expression and Behaviors data should only be deleted when the Rules and Behaviors Rule Type is changed and indicated by the following message displayed in the GUI; "The Rule Type field has changed. Continuuing will result in all expression and behavior information being lost. Would you like to continue?".

 

Recreation Steps

The issue can be reproduced at will with the following steps:

1. Application Setup

2. Work Management Setup

3. Rules and Behaviors

4. Select one of the active rules

5. Note the information in the Expression section

6. Click the Rule Information section's Edit link

7. Click the 'Save and Close' button

NOTE: No changes to Rule information are necessary.  Clicking the 'Save and Close' button alone results in the undesired behavior.

8. Note the information in the Expression section has been deleted

 

Business Impact

Due to this issue, Rules and Behaviors expression data can be lost and must be manually recreated.  Additionally, Task Behaviors associated to a Rule having no expression condition(s) are applied to every order type defined by its Rule Type (example: PSR Product Service Request).  This results in lost productivity from the unnecessary task completion work.

 

Changes

Customers upgrading from 6.0 to 6.2 would observe the behavior.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms