************************************************************************************

Oracle Insurance Rules Palette V9.3.1.0 ReadMe

************************************************************************************

Summary

* Release Date: March 1, 2011
* Platform: Windows
* Release Type: Maintenance

************************************************************************************ 

Overview

This ReadMe file contains important information about this release including installation instructions and known issues.

The documentation for Oracle Insurance Rules Palette and all other Oracle Insurance products is available from the Oracle Technologies Network site: 

http://www.oracle.com/technetwork/documentation/insurance-097481.html

Scroll to the bottom of the Oracle Insurance page and select Oracle Insurance Policy Administration 9.3.1 library E21044_01.

************************************************************************************ 

Prerequisites

There are two components that must be installed before the Rules Palette: Policy Administration (OIPA) and the Web Application Utility.  The Web Application Utility is needed to establish the environment properties for the Rules Palette and therefore must be installed after the Policy Administration application.  The Web Application Utility is inside the Rules Palette Media Pack in the PaletteConfig folder.

After the Policy Administration application and the Web Application Utility have been installed you can install the Rules Palette.

Follow the installation instructions on the Oracle Technology Network at http://www.oracle.com/technology/documentation/insurance.html.  Scroll down the OTN index page under Applications and click Oracle Insurance.  Then scroll to the bottom of the screen and select Oracle Insurance Policy Administration Library and open the E21044-01 library for the 9.3.1.0 release.
.


Rules Palette Executable file:
*OIRP_9.3.1.0/bin/asgraphicruleside.exe

Execution Environment:
*Java

Java Virtual Machine:	
*Java HotSpot(TM) Client VM 1.5.0_11-b03

Operating System:	
*Windows


************************************************************************************ 

System Requirements

Computer Hardware: 
*Intel CPU 2GHz, 2GB RAM, 512MB disk space, 1280x800 resolution display	

************************************************************************************ 

Media Package Contents

Rules Palette Application Files
*OIRP_9.3.1.0

Rules Palette Executable file:		
* OIRP_9.3.1.0/bin/asgraphicruleside.exe

Web Application Utility Files
*PaletteConfig

Web Application Utility Properties files
*PaletteConfig\PaletteWebApplication.properties

Web Application Utility Deployable file
*PaletteConfig\PaletteConfig.war

************************************************************************************ 

Installation Instructions

The Installation Guide is located on the Oracle Technology Network.  
http://www.oracle.com/technology/documentation/insurance.html.  Scroll down the OTN index page under Applications and click Oracle Insurance.  Then scroll to the bottom of the screen and select Oracle Insurance Policy Administration Library and open the E21044_01 library for the 9.3.1.0 release.   Open the OIPA Installation Guide.  

************************************************************************************ 

Known Issues and Limitations

General

Database Testing
- The databases used to test this Palette release were Oracle 11g, DB2 9.1, SQL 2005 (WebSphere on DB2/SQL, WebSphere 6.1.0.31/WebLogic 11h on Oracle).
- WebLogic users must deploy the PaletteConfig.war file in an exploded mode on a Weblogic server.   Any other method will not provide the desired results.
- If using a database server with both SQL 2000 and SQL 2005 installed, the user cannot connect to the 2005 instance with the palette as it currently exists.  In this situation, the SQLServer2005 database is not currently included as a possible database type.  The user will need to manually update the properties file created by the Rules Palette.

Web Application Utility
- The Web Application Utility can support only one environment.  For each unique environment needed, a separate Web Application Utility needs to be installed.  This prevents the user from being able to choose different environments with only one installation of the utility. 
- The Web Application Utility has no validation in place for user names and will allow duplicate user names.  User names must be unique.

Rules
- If a user creates a new rule and fails to check it in immediately, then logs off and answers Yes to the prompts for the check-in, then the rule is not always checked-in and therefore may be lost.  The user is instructed to check-in new rules before attempting to log off an environment.

Versioning
- Version numbers are not incremented consistently in the Files section of the Admin Explorer.
- Version History nodes exist on both the Main and Global Explorers for overrides.  When a rule is modified on one of the Explorers, the version node is created on that Explorer.  No version node is created on the other Explorer.  The user should check both Version History nodes when a version is questioned.

-----------------------------------------------------------------------------------------------------------
Admin Explorer

Chart of Accounts
- Updates made to the EntryDescription field of a ChartOfAccountsEntry are not being saved to the database.  When checking-in the entry, the display indicates that the changes are saved; however, after viewing the AsChartOfAccountsEntry table it is revealed that they are not saved.  The user will need to update the database directly.
- If an entry type is changed from a MathVariable or Disbursement type to the "ByFund" or "TotalOfFunds" type when editing a Chart of Accounts entry, the AccountingAmount field is disabled instead of set to a blank.  The user will need to change the MathVariable name or DisbursementAmount value directly in the XML Source pane.
- The Entry type is not being reset to blank if it is switched from a fund type to another type.  The user will need to make sure the correct entry type is on the XML.
- When selecting the Back button on Step Two of the COA Editor, the transaction field is reset and the user will need to re-select the transaction.

Code Name
- New code names on the Admin Explorer tab are not saved at check-in if the actual code values are not present.  The user should enter code values to prevent data from being lost.
- If the user clicks the Delete checkbox on a row and then clicks the delete button, the row of data is not removed and an error message displays.  In order to delete a row, the user must click on the row to highlight it and then select the Delete button.
- The AsCodeCalendar editor is not writing to AsCalendar and is throwing an exception when no corresponding data exists in AsCalendar for the existing AsCodeCalendar Code values.  If the exception is given, the workaround is to select Date Offset field values for those CodeValues without a record in AsCalendar.

Country
- The Delete check field is not enabled when a new row is added in the Countries editor. The user is advised to check-in the editor, check it back out and then delete the unwanted new row.

Currency
-The Rules Palette does not allow the Currency Code to be blank at the Company and Plan level.  When Plan level currency is null, Company level currency is applied to the policy.  When Company level currency is null then the System default currency code from OIPA properties file is applied.  The user will need to null the currency code via the database if a blank is needed in the Company or Plan level currency. 

Exposed Computation
- During modification of the exposed computation rule, if the XSD Data in the XSD pane is deleted and the rule is checked-in, then the XSD Data should be deleted from the Palette on check-in.  This data is deleted on check-in but reappears when the user logs-out and then back into the application.  The work around is to delete the XSD Data from the XSDData column in the database.
- When an Exposed Computation rule is created, the Palette should write the main tags as <ExposedComputation></ExposedComputation>. Currently the tags are being written as the name of the rule.   The user will need to manually change the tags to <ExposedComputation></ExposedComputation> on the XML Source pane of the rule.

Files
- Revert Modifications on Files is not checking-in correctly.  The user should manually remove modifications before checking-in the file.

Map Groups
- The existing map value is lost if the datatype is changed in the Map Editor.  The user should re-enter the map value before saving.
- After entering a new map group, if the user enters Map Criteria and selects the Add button instead of the Create button, an exception is thrown.  The user is cautioned to only use the Create button.
- The Currency Code field on Map Groups does not correctly display the currency code selection and always defaults to the first option, 'AUD'.  The correct currency code is written to the database so users should review the database to verify the code being used.  It is advised that any updates made to Map Groups be made directly in the database.
- The delete check field is disabled when a new MapValue row is added.  The user must check-in and check-out again to allow the delete check box to function.
- The Map Values Add button may not be visible to some users due to the screen resolution chosen.  Until a vertical scroll bar is added, users may need to change screen resolution to see the button.

Rate Groups
- When using the Add Rates button, a date format of dd/mm/yyyy must be used otherwise an exception will occur.
- When Rate Group modifications are reverted, the changes aren't reflected immediately in the Rules Palette but they are correct in the database.
- When adding a rate entry to a Rate Group, an exception is seen if the rate is left blank.  The user should enter a rate.  If an exception is encountered, the user must close out the exception and enter the rate.  
- The user is unable to filter rates based on rate criteria in the Rules Palette when rate groups are checked-in.  This happens when the user does not have the appropriate security privileges.  The user must coordinate with another user who has the proper security rights.
- Rate Groups must be deleted from the database.  They cannot be deleted through the Rules Palette.
- When a rate group is created, criteria number columns that are unused can never contain a value.  If the user attempts to add a value to a cell under one of these unused columns then an exception will occur. 
- For the Rate table type Ultimate, the Select Period field on Step Three of the Rate Wizard should be pre-populated and disabled.  Currently, the system leaves this field enabled and a user is allowed to changed the Period.  If this is changed from the original pre-populated value, then the results will not be accurate.

Requirements
- An invalid format is accepted in the value field of the Criteria Row using the Requirements Editor.  An error message is displayed but the details are automatically checked-in, which is not the desired action.  The user must check-out the Requirement again and adjust it to a valid format.

System Date
- A current existing System Date entry cannot be modified.  Any updates to the actual date or indicators (Current Indicator, Month End Indicator, Year End Indicator and the Quarter End Indicator ) must be done directly in the database or simply delete the incorrect entry and re-enter the details.
- Existing System Date entries cannot be edited using the System Date editor in the Rules Palette.  New System Dates cannot be added using the System Date editor for a new Calendar code.  The database must be updated directly.
------------------------------------------------------------------------------------------------------------------------------------
Allocations
- The Rules Palette is writing a default value of "Yes" for AllocationFrom and Allocation tags.  The default value should not be assigned automatically and should be set to blank.  The user should update the XML Source pane directly to correct this.
- The MethodCodes option incorrectly appears under the configuration section when the Allocation component is selected. The MethodCodes attribute option should only appear under the AllocationFrom and AllocationTo component. The end result is the Attribute tag is now included within the Allocation tag instead of the AllocationFrom or AllocationTo tag.  If MethodCodes are used, the user will need to make a correction to the XML on the XML Source pane or enter configuration directly into the XML Source pane.
- If a user fails to add Allocation methods for the Allocations added on the Allocations pane in the corresponding Allocation screen plan override, then an exception is thrown when adding funds on the Allocation pane in the Plan Data Editor.
------------------------------------------------------------------------------------------------------------------------------------
Business Rules
- When an identifier field is added to the Fields pane and the Parts Field Properties are selected, the Parts fields are not reset after adding to the tree. The user can click the add button not knowing that the same part (with duplicate values) will be added numerous times.  The XML should be checked to ensure desired results.  
- Deleting certain rule types when the rule has no version history causes a stack trace when the user attempts to delete the rule. 
- The version number is not updated when a business rule's General pane changes (Type, Long Name, Keywords, Comments, and Error Message).  The only time the version number is incremented is if XML changes are made.  The database is correctly updated with changed data but reflects the original version.
- An error with Upload Schema exists that allows the Fields and Events visual editing panes to be added to the Screen rule editors.   The RoleScreen and CompanyScreen, which already have visual editing, are not affected when Upload Schema is run, but the other Screen rules are affected.
- Values entered on the Business Rule General pane in the LongName, Keywords, Comments, and Error Message are not saving to the database if a Non-IVS database is used. The user will need to update values directly to the database.
- The Type Field on the General pane of a business rule is incorrectly enabled. The user is able to change the rule type and check-in the rule. The database is also updated with the new rule type.  The user should not change the rule type after a rule is created.  Instead, the rule should be deleted and then re-added with the correct type.
- The Inquiry Screen does not include a General pane. The General pane displays the version number.   The work around would be to view the version number in the database in the IVSVersion table. 
- When MultiSuspense, Suspense, or Withholding are added to a financial transaction in the New Transaction Wizard, default values are written to the XML. If the default values are not the desired value, then they can be changed via the General pane.  If the user elects to add MultiSuspense, Suspense, or Withholding after the transaction is created via Edit Transaction General, no default values are written. Values will need to be selected on the General pane.
- State override records are not automatically deleted from the AsBusinessRules table when the global business rule they fall under is deleted.  Override records are automatically deleted from AsBusinessRules for Company, Plan, Transaction and Requirement overrides.  The user is directed to delete the record directly from the database.
- The Finish button is disabled upon initial entry to the Edit Company wizard and is not automatically enabled when the currency code is changed.  The user should re-select the same effective date on the wizard to force the Finish button to be enabled if changes need to be made.  This issue is seen only on the first attempt to Edit a company while in the same log-in session. 
- If AsCompanyField values are present when a CompanyScreen is deleted, the values remain in the AsCompanyField record.  If the CompanyScreen rule is recreated with new fields, then on check-out of the CompanyData editor, the previous fields are removed from the database and the new fields are added. Otherwise, the records will remain in AsCompanyField unless they are deleted directly from the database.
- Data is not saved correctly when entering dates manually or blanking them out in the 'Date' type field of the CompanyData editor.  The user must select the dates using the calendar.  The only method to successfully blank out a previously entered date is to delete and re-add the Data field on the Company screen.  Check-out the Company Data and check it back in again without entering a value in the Date field. 
- The option to CopyBook an entire Fields section is not yet available for the Roles screen.  The user should add the CopyBook directly on the XML Source pane.
- When a state override of a global CopyBook is created, an exception is seen on check-in. 
The user needs to click OK on the exception message and check-in again. The override checks in the second time.
- The Comment button on field Copybooks (without select tags) is duplicating fields and XML comment tags each time the Comment button is pressed.  The user will need to remove the duplications on the XML Source pane.
- The option to add External Keys does not work when using Functions on the Roles screen. An error message is shown stating that the rule must be checked-out when it already is.  The work around is to add the External Key configuration on the XML Source pane.
- The Required option displayed on the Field Properties window is not operational and should not be used.  This applies to all business rules, transactions, segments, etc.
- When the node for a rule is expanded on the Global Explorer and a new plan is then created on the Main Explorer, the node on the Global Explorer does not reflect the new plan addition until the user logs out and back in again. 
- In order to remove a specific date value from a configured date field on the PlanScreen business rule, the user would typically make the update via the Plan Data editor.  However, this method does not function as the value is not correctly removed and the previous value is kept. The user should remove the field through the PlanScreen business rule and then re-add the field as a blank value.
- Data is not saved correctly when dates are entered manually or blanked out in the Date type field of the Plan Data editor.  The user must select the dates using the calendar.  The only method to successfully blank out a previously entered date is to delete and re-add the Date field on the Plan screen.  
- Plan field/Plan data values are lost sporadically.  If this happens, the user will need to re-enter the values in the Plan Data editor.
- An exception is thrown when attempting to delete a functional call from a Calculate business rule.  The user will need to delete the function call from the XML.
- When creating overrides for business rules through the Global Explorer, the newly created override should have the same General pane properties as the Global rule. However, the data is not being transferred to the override. 
- While using the visual editor for the RoleCodes pane of the Policy screen, options selected for  <AllowZeroPercent> or <AllowNoPercent> should affect how RolePercent can be used on the screen but it does not.  Proper care should be taken when entering valid details through the visual editor.   
- New role codes are not always saved when they are added on the Role Codes pane of the Policy screen.   The user will need to validate that they are added by reviewing the XML or by adding them directly to the XML Source pane.
- Events configuration is not saved on several screen rules including the RoleScreen ruleand the PolicyScreen rule as well as segments and transactions.  The workaround is to go to the XML Source pane immediately after adding the Events configuration on the Events XMLData pane. This allows the Events XML to be saved. An alternative would be to return to the Events pane and re-add the configuration then check-in immediately.  The Events configuration will save on the second attempt.
- Selecting the Events pane for the first time on the PolicyScreen rule gives a sporadic exception.   The user must clear the cache and log back in to be able to successfully select the Events pane.
- When a PlanScreen rule is created, field values are saved to AsPlanField via the CompanyData editor.  If the PlanScreen rule is deleted, the field values remain in the AsPlanField even though the PlanData editor shows the message, "No fields found in the PlanScreen."  Workaround: If the PlanScreen rule is recreated with new fields, then on check-out of the PlanData editor, the previous fields are removed from the database and the new fields are added. Otherwise, the records will remain in AsPlanField unless they are deleted directly from the database.
- On the Eligible Txns pane editor, if a PolicyStatus CodeValue is added using the Lookup feature, then the Name field will become updated with the correct associated value. Also, if the Name field is added using the Lookup feature, then the Code field is updated with the correct associated value.  If the value in either of these fields is entered manually, then the other corresponding field is not loaded with a corresponding value. Likewise, if the value in either of these fields is modified by manually entering a value, then the other field retains the original value. If these field values come out of sync in this way and then the Lookup button is selected next to the Name field, then a sporadic stack trace is given.  Workaround:   If the user manually enters the value in one field, then the value in the other field needs to be updated by the user as well, either by using the Lookup feature or manually adding the value.
- When the user edits the Query field in an Identifier field's properties, an exception is immediately received. The edit to correctly configure the query should be done via the XML Source pane.
- Batch Screen version numbers are incremented unnecessarily on check-out and check-in when no updates are made.

-----------------------------------------------------------------------------------------------------------
Data Dictionary
- The user is not able to search by Category on the Math pane of transactions and business rules.  Search should be performed using the  Term field or the Description field.
- When Compliance is changed, the user must log-off and log-on again for the changes to take effect.
- When using the Data Dictionary search through the SearchPalette window for the first time, a rule or transaction must be checked-out AND the Fields pane must be open. If both of these conditions are not met, then an exception occurs. After a search is successfully performed the first time, the user can use the Data Dictionary Search in the SearchPalette window with no restrictions. 
- Data Dictionary retains the original Data Dictionary information when the user logs out of one database environment and logs into another. The user must clear the Cache to reset the Data Dictionary when changing environments.

------------------------------------------------------------------------------------------------------------
Debugger
- Debugging is only fully supported for transactions.
- In DB2, the compiler is run automatically before initializing the debugger and therefore all errors are caught and fixed before the debugger is run.  In SQL the compile is not done automatically.  Transactions and rules should be compiled and error free before attempting to run the debugger.  
- The transaction debugger runs through the best matched CopyBook, unless there is only a Company level and Global level CopyBook available. In this case, it runs through the Global instead of the Company level.  The end result is the Debugger pane does not always pick up the correct copybook.
- When running the debugger, there is no indication that the debugger has completed debugging.  If the last item in a transaction or segment is a MathIf or MathLoop where the condition is not met, then the debugger stops.  This can be confusing to the user because it appears that there are additional MathVariables to check.
- When using the debugger, arrays and objects are displayed as addresses rather than values.  Until a fix is completed, the user will not be able to debug if access to arrays and objects is needed.

-----------------------------------------------------------------------------------------------------------
Error Handling
- The compiler is not fully capturing all of the transaction compile errors.  The user will need to re-compile after fixing each error for accurate results.
- When compiling a transaction that has an error within a math loop, clicking on the error does not pinpoint the statement that caused the error in the XML.
- If a Compilation error is fixed while a rule is checked-out, then the error remains displayed upon check-in.  
- Deleting a newly added error message with a duplicate error number deletes both the existing and newly added messages.  The user must then re-add the original error message.

-----------------------------------------------------------------------------------------------------------
Functions
- Deleting a CopyBook from within a function causes an exception.  The user must delete the CopyBook directly from the XML Source pane.
- The Debug pane should not be present on functions.  At this time, functions cannot be debugged outside of transactions.

-----------------------------------------------------------------------------------------------------------
Localization Editor
- The Translation Value field in the Filter option of the Localization editor is 
not working properly.  If a user tries to filter by the translation value, then 
nothing happens.  If a user tries to filter on another value and the translation 
value, then records are returned based only on the other value.  The work 
around is to query the AsTranslation table in the database.

-----------------------------------------------------------------------------------------------------------
Math Pane
- When adding a RateArray on the Math pane, the attributes STARTINDEX and ENDINDEX are automatically created.  The attribute STARTINDEX should be replaced with INDEX via the XML Source pane for it to work correctly.
- While using visual editing, the source variable drop down list is empty when adding MathVariable Type=CollectionValue.  Workaround:  Edit the MathVariable in the XML Source pane rather than with visual editing.
- MathVariable TYPE=CollectionValue is not being created with a 'DefaultValue' attribute and no engine errors are displayed.  MathVariable TYPE=Collection is being created with a 'DefaultValue' attribute and it should not.  Until this is fixed, the user must make corrections directly in the XML Source pane.
- Buttons on the Math pane are not working properly (Up, Down, Move In and Move Out).
- The Value written to the XML Source for the SOURCEARRAY attribute should be the value that is selected in the SourceArray field on the Math pane (the MathLoop name) not the SegmentField field on the Math pane.  
After moving to the XML Source pane and back to the Math pane, the SourceArray value should stay populated on the Math pane and the SegmentGUID field should remain disabled. If the SourceArray value is removed from the Math pane, it should be removed from the XML, but is not.  When a value is selected for the SegmentName filter, this should not be written to the XML, but it is.  As there are issues with Segment field and Segment type MathLoop, it is recommended that the XML Source pane be validated to ensure the XML is created as desired.
- For MathVariable TYPE=OBJECTLOOP, when the table name is selected from the SelectObject field for the OBJECTNAME attribute, it is written to XML with an 'AS' prefix in the object name.  The 'AS' will need to be removed through the XML Source pane.
- A null pointer results from using the Comment button on a field of MathVariable TYPE=Object.  Math Variables should be commented out from the XML Source pane.   
- The VALUATION type MathVariable is not supported but is listed on the drag and drop list of math variables.  This variable type should not be used.
- When using AutoComplete with an Activity prefix, fields configured in attached CopyBook's math section or fields on the transaction math section are not included.  The user should enter them directly in the Value field.
- AutoComplete for Expression Field math variables do not include ALL fields from the transaction Fields pane and all fields and math variables configured in attached CopyBooks.  The user should enter those values directly in the Expression field.
- When entering details into the prefix field of a Field type math variable, a colon should be placed after the prefix name.  If the user does not enter a colon, then the screen will display the details under the Value field. This happens when the user clicks off the Math pane and then back again.  The user is advised to review the XML to ensure a colon follows the prefix and then the value follows the colon.
- The Prefix combo box on the Math pane for Field type math variables does not yet contain the Valuation option.  If needed, the user should type in the Valuation option.
- The only type of array that is supported is "Array".   Other options are displayed but are not valid (StringArray, NumericArray, IntegerArray, and DateArray).
- When a Function Call MathVariable is added to a CalculateGeneral rule, an entire transaction CopyBook, or a Function, then the parameter value fields are not pre-populated with the math variable names from the rule.  The user will have to enter values directly in the XML Source pane.
- On the Math pane of transactions, "MINOF" and "MAXOF" are possible METHODs for AggregateFunction.  The Base system does not recognize these and processing will not work as desired if they are selected. If they are corrected on the XML Source pane to "MIN" and "MAX", respectively, they both work without issue.
– If the "Math-IF" is the first math variable to be added to the CalculateGeneral Math pane, then an exception is seen.  The user should avoid having a Math-If as the first statement in this rule.
– AggregateFunction attributes do not display correctly on the Math pane after check-in. The work-around is to drag a new AggregateFunction onto the Math pane and select the Method of Exist or IndexOf. After doing this, and if a previously saved AggregateFunction with these methods is selected, all of the attribute fields will be displayed. 
– The PROCEDURENAME and the Parameters/Parameter elements and NAME attribute are written to the XML with empty quotes before any value is selected from the StoredProcedure field on the Math pane.  After a StoredProcedure value is selected, the XML is written as expected.
– After adding a math variable on the PolicyValues Math pane and then deleting it and attempting to move to another pane, an exception is seen.  If the user deletes the lone math variable and then attempt to add another without moving to another pane, than multiple <MathVariables/> tags are written to the XML.   The user must correct the XML directly on the XML Source pane.

-----------------------------------------------------------------------------------------------------------
Requirement Grid
– If while working on a new grid a user moves to another editor, when returning to the grid, the buttons on the Age/Amount, Requirements and Conditions panes will be disabled.  Buttons are re-enabled when the grid is checked-in and out again.
– On Requirement Grid Conditions, the Undelete button temporarily removes the delete status from the row.  Once a Condition row is given the Delete status, the only way to prevent the row from being Deleted is to use Revert Modifications.
– When a user selects a new requirement row on the Age/Amount Bands pane and then selects another Age/Amount row that already has an associated Requirement, the Condition pane buttons will be incorrectly disabled.  The workaround is to add or select another requirement and then reselect the first requirement.
– The Add, Delete, and Revert buttons on the Requirement Grid Version History panes are enabled but should NOT as these will affect data.  Future fixes will disable these buttons.
– On Requirement Grid, when the user selects the "Revert to Version" option, the current version editor is not consistently populated with data from the version to which it is being reverted. To ensure the correct version displays, the user should execute "Revert to Version" when the Version History pane is open. The correct data is displayed after check-in of the grid.
– If a user does Revert Modifications after Revert to Version on a Requirement Grid, the current version editor does not change back to display all the data from the last checked-in version.  The Requirement Grid data changes back, but the Age/Amount Bands, Requirements, and Conditions do not.  After the user does a check-out/check-in of the grid, the display is corrected.
– A variety of intermittent issues have been seen when Revert to Version is performed on Requirement Grids. The issues have been observed when the Version History pane of the version to which the grid is being reverted to is open. The issues include Rules Palette freezing (which requires a forced shut down), data from current and prior versions becoming combined (instead of overwritten), and program exceptions.

------------------------------------------------------------------------------------------------------------
Release Management
- Release Management does not include Company and Plan migrations, AsFile migrations, Inquiry Screen migrations or Requirements Definition migrations.  If rules need to be migrated for a new company (in destination environment), Insert statements need to be used to create Company/Plans in the destination environment, taking care that the same GUIDs are used for Company/Plan as created in source environment.
– Release Management for Batch screen migration is supported in this release.
– Full Functionality to handle failed migrations is not yet implemented. The user is advised to make backups of data so the original dataset can be restored if the migration fails to perform properly.
- An exception occurs when attempting to deploy a release package that contains configuration under newly created Company/Plan if the Company/Plan do not exist in the destination environment.  Since release management does not support migrations of Companies/Plans yet, the user is advised to insert Company/Plan details in the destination environment, ensuring Company/Plan GUIDs match before attempting a rules migration.
– When release management is turned on and the user attempts to check-out from the ConfigPackage node to make updates, an error results. The user must make any subsequent changes using the check-out feature under the Global Explorer tab or the Main Explorer tab and NOT the ConfigPackage node.
– When a user tries to delete a Non-Palette item from a Configuration Package, a system exception results and no confirmation of the deletion is displayed. The user must exit Rules Palette and restart it in order for the deletion to complete.
– If the user creates a configuration package from the explorer with a configuration package name that already exists in that environment, a system exception results. To avoid this problem, the user should give a new name to the configuration package that doesn't exist in the database.
– Security currently does not restrict a user from checking out, creating, and deleting rules when release management is turned on in the entry environment.
- When adding a transaction to a configuration package, the new item is not populated in the Config Package transaction node if that node has already been opened during the current session. Since the list is populated upon first expansion of the node during each session, any changes made before the first expansion are shown and any changes made after are not shown.
– When Release Management is turned on, users should avoid right-clicking within a configuration package as this function is not supported.
– When a transaction is included in a configuration package and then subsequently checked out and back in again within the Main Explorer Company node, the XML shown under the Admin Explorer configuration package node does not reflect the most recent changes made to the XML.  When migrated, the most recent version of the XML is correctly migrated, but the display under the Admin Explorer is misleading.  Workaround:  Ensure all updates are made via the Admin Explorer or logoff and on again to have the display reflect the update.
– When only a few rules are included in a configuration package, the user is not given any indication that the package has been deployed. The only method of confirming is for the user to right click on the node and see the option for "Deploy package"  appear in the target.
- Instead of a warning, an exception is seen when a user tries to create a duplicate Configuration package.  The user should not create duplicate Configuration Packages.
– The Rules Palette does not prevent a user from creating a Migration Set with a name that is already in use. The user should avoid using existing Migration Set names when creating Migration sets.
– If a user attempts to check-out a transaction or segment via the Config Package node to make changes, a stack trace is thrown.  A user may double-click within the Config Package node and view the different panes in a read-only mode. If updates to transactions or segments are needed, the user must navigate to the rule outside of the Config Package node and make the modifications.
- When Release Management settings are changed in an environment, these changes don't take effect until that application is shut down and a new session is started.   A user cannot proceed with new settings until after a re-start.
– A user does not have the ability to revert an entire configuration package.  The user must manually revert to the version prior to his or her changes and then manually remove the item from the configuration package.
– A sporadic stack trace is thrown when attempting to check-in new transactions after turning off Release Management in a SQL environment.  The user can work around this issue by logging off and on again and then creating the transaction followed by check-in.
– Clicking on the Attached Rules node of a transaction within a configuration package causes an exception. Workaround:  Expand the Attached rules node from directly under the transaction node under the plan.
- An exception occurs when a user clicks on the Attached Rules node of a transaction within a Configuration Package.  The workaround is to expand the Attached Rules node from directly under the Plan's transaction node.
					
-----------------------------------------------------------------------------------------------------------
Segments
– The Client field datatype is not present on the Fields pane of a segment in Rules Palette. Since the field is supported on this screen in OIPA code, the workaround is to add the field XML directly on the XML Source pane.

-----------------------------------------------------------------------------------------------------------
Security
– If the Security Group editor is open when a new transaction is added, check-out of the Security Group is not updated with the new transaction.  Workaround:  Move to another editor and then return to the Security Group OR  check-out the Security Group again OR use the Refresh right-click option on Security Groups.
- If Release Management is turned on, a user who does not have Release Management privileges (specifically Configuration Package privileges), should not be able to create, check-out or delete a rule.  Until sufficient security is in place, users without these rights should not attempt to execute these actions.
- For the debugger to correctly function, SQL statements must be run for authorization records to be generated when a new company or security group is added or deleted.  Currently, there is no editor to support this in the Rules Palette.  
- If a user attempts to delete (without first saving) a new Rules Palette security role after just adding it, an exception is seen. The user must click Save on a role before deleting it in order to have it function correctly.
- The initial attempt to add a new security group does not create the new security group.  The user must re-attempt for it to be created successfully.

-----------------------------------------------------------------------------------------------------------
Transactions
– Extremely large transactions throw an error when compile is attempted.
– When reverting a transaction to a previous version and then selecting revert modifications to return back to the original XML, the XML displayed is not correct. The data saved is correct, but the user is required to refresh the transaction in order for the XML to display correctly.
– When a transaction is checked-out on the Global Explorer after creating a new Global business rule and then an override of that rule, the system will terminate. The Rules Palette should be closed and re-opened to avoid this issue.
– After checking out a CopyBooked transaction, the system will display a message informing the user that transaction sections cannot be edited. The user should click OK and continue to edit the transaction sections.  Updates should not be made.
– The NAME and FUND fields available for the MoneyType element are populated incorrectly with only the transaction's MathVariable names.  They should also be populated with the transaction field names of the appropriate datatype.   The user will need to add the field name for these attributes directly on the XML Source pane.
– On an Assignment section CopyBook, the MoneyType NAME and FUND fields don't become enabled because the fields and math are not included in the section CopyBook.  The user will need to enter the MoneyType NAME and FUND attributes and values on the XML Source pane.
- When state, transaction and plan overrides are present for a Copybook, deleting the transaction override or plan override by selecting the delete rule option does not reflect the deletion on the Palette UI.  However, the database is correctly updated.  This issue occurs only when all plan,transaction and state overrides are present and is not observed when only one of these overrides is present.  To correct the UI, the user can either selecting the delete rule option again or refresh the Business Rules node.


– The save icon is not enabled when a modification is made to an Assignment type on the Assignment pane.  The user must either move to another pane in order to use the Save icon or check-in the transaction.
– When an Assignment type is added on the Assignment pane of a transaction, the system incorrectly sets the MoneyType element and NAME attribute to a default value of "NewMoneyType." Only the Assignment type should be written.  The user should update the XML Source pane. 
– When adding an attached rule to a transaction on the Main Explorer, the user can right-click on the transaction XML node and select EditAttachedRules to attach an existing rule. However, when removing the attached rule, the EditAttachedRules option will only remove the rule from the EditAttachedRules list and the TransactionBusinessRulePacket; it will NOT update the list of rules on the Attached node under the transaction. The only way to remove this would be to navigate to the Global Explorer pane and delete the rule. The deleted rules will be displayed until the user refreshes the Main Explorer.
– Attaching a newly created Attached Rule before its global version has been checked-in does not add the rule to the Transaction's Attached Rules, but does add the rule to TransactionBusinessRulePacket. Users should make it a point to check in the global first before attaching the rule to a transaction.
– There is no validation to ensure type is selected when the user adds a transaction to EligibleTransactionsByPolicyStatus. Because there is no validation, the user may think they have added the transaction successfully when they have not. Without the type being populated, processing will not occur correctly as it will not appear in OIPA.
– When using a transaction that has Money fields, Decimal fields, and Currency math variables, spawning another transaction with the same field types results in discrepancies.  When the combo box for the Money field is expanded, the Decimal field is not available. (incorrect).   When the combo for the Decimal field is expanded, the Money field is not available (incorrect).  If a Spawn "To" Field is of the Decimal type, then Decimal and Money Type fields, as well as Decimal type MathVariables, should be available in the Spawn field "From" column.  The work around is to configure the fieldnames directly on the XML Source pane.
– If a Suspense block is selected for a transaction and no values are entered, the XML is not updated with the Suspense tag and selections are lost.  The user must fill in all fields before clicking off the Spawn pane so that changes are not lost, or, the user must make updates directly to the XML. 
– When the TransactionBusinessRulePacket is checked out and a rule is attached to a transaction, the newly attached rule is not added to the TransactionBusinessRulePacket.
- The save icon is not enabled when a modification is made to an Assignment type on the Assignment pane.  The user either needs to move to another pane in order to use the Save icon or check-in the transaction.
– When MultiSuspense is added to a transaction by checking the MultiSuspense checkbox on the New Transaction editor, the FIELD attribute is written to the XML with a default value of FIELDNAME.  In addition, when Suspense is added to a transaction by checking the Suspense checkbox on the New Transaction editor, a value of FIELDNAME is written to the XML. The XML being written in these cases is incorrect.  The user should add a valid FieldName from the combo box after fields have been entered in the new activity.
– Sometimes a change of Assignment Type is not saved upon check-in. The user is advised to re-check that the correct assignment is saved after check-in.
– Sometimes the Assignment pane is blank when moving from the Assignment pane to the Math or Fields pane and then back. To get the proper display, the user must select another pane, such as Spawns or XML Source pane, and then return to the Assignment pane.

-----------------------------------------------------------------------------------------------------------
Usability Issues
– Sometimes the user will see a Null Pointer error when logging in.  The user should attempt to log-on again.
– When creating a new environment, only alphabetic characters are permitted in the name; special characters are not permitted.
– If a user mistakenly chooses an incorrect configuration server port with one database and then goes back and changes to the correct configuration server port, the Environment Creation Wizard does not refresh any details on page 2 of the wizard.  The user will need to close down the wizard and re-enter environment details.
– Synchronization/Refresh issues occur between the Global and the Main Explorer.  If a user is switching between these two panes, the refresh option should be used to ensure each pane reflects the most recent node structure as well as the most recent version of the rule, transaction, segment, etc. A refresh option should be used following any addition or deletion of rules.
– The Revert Changes option is erroneously available before check-in of newly created rules, transactions and administration items.  An exception is seen if this option is selected before a rule is checked in at least once.
– Events Pane displays on the Company, Plan, and Fund screens but is not applicable.
– The Interface node under the Business Rules category, seen on both the Main and Global explorer, still displays but is no longer valid. This node should not be used.
– When navigating between Explorers, the panel selector is not updated correctly.
– At times, the Plan screen displays data in Scientific notation.  The user can update the field and the correct display will be shown when saved.
– Select in Explorer is not functioning consistently for Administration Items.  The selected rule is not highlighted as expected.
– Select in Explorer is not functioning with the Company Data editor. The user may locate the CompanyData editor manually in the Explorer pane.
– The system will allow the user to enter rule and transaction names with spaces.  Spaces are not supported in OIPA so the user should not include spaces in names.
– An invalid message is given when deleting a rule that has XML added but never checked in.  The user should select "Discard changes" before deleting a rule in such a condition.
– Upon check-in of a rule with empty tags and a line break in between, invalid XML is being inserted "<?xml version>".   The user needs to check-out and in again to correct.
– When a rule is checked out and changes are made in the Math Pane, the Undo and Redo icons in Palette toolbar are disabled. The user will need to revert changes back manually instead of relying on Undo and Redo options on the toolbar.
– On the Business Rule Override Wizard, the Transaction Field is not disabled when creating a State level override as it should.  The user should not attempt to select items from the drop down menu.
– Right-click actions Cut, Copy, Paste, and Find don't work on the Events, Math, Actions, Files, XML Source, or Exposed Computation panes.
– Toolbar icons for Cut, Copy, and  Paste don't work on the Events pane.
– The Save and Save All buttons function inconsistently.
– After editing a Primary Company name, the new Primary Company name should be seen in the Edit Company Wizard of its Subsidiary Company but is not. The database for the Primary Company and Subsidiary Company is updated correctly, but the user needs to log off and then back on again to see the changes displayed correctly on the screen.
– The system reports an exception when a user deletes a plan-level "Whole Transaction" CopyBook. The rule is deleted from the database. 
– When a CopyBook field is added on the Fields pane, the Field type is disabled and should not be in the FieldProperties window.  Workaround:  The user should remove the copybook field, and drag-and-drop the new field type that is desired.
– When a Field type is changed to a new type, the new field type properties are not loaded until the user performs an additional mouse click.
– If a Field Type is changed to MultiField from another type on the Fields Property window, the system reports an error.  Workaround:  Remove the unwanted Field Type and then drag the MultiField onto the Fields pane.
– The system reports an exception after deleting a math variable on the Math pane of a Calculate General rule and then using the "Undo" toolbar feature or hitting Ctrl + z.  Workaround:  Drag a new math variable to recreate the one that was deleted.
– The MathLoop name is not displaying in the Math pane.
– The system reports an exception when the user left-clicks while inside Component list on the Mappings panel of the Calculate General rule. 
– The Auto Complete feature on the Math pane (Ctrl + Enter) displays a scroll bar but the user must use the scroll wheel on the mouse otherwise the Auto Complete pane disappears.
– Not all array names are populated in the SourceArray box of a new array on the Math pane.  The user must enter data on the XML Source pane.
– On a segment in read-only mode (checked in), the Calculate button on the Buttons pane appear enabled. Any updates are not kept while in read-only mode so the user should not attempt updates.
– The Spawn editor's quick search pane will not display the current transaction being edited.  For example, if an Anniversary needs to spawn the next Anniversary, the user must go into the XML and manually type in the transaction name rather than use the quick search.
– When a Requirement Definition is deleted, business rules overridden by the Requirement Definition should also be deleted.  Instead, the business rules remain and indicate "Bad GUID" on the node.  The user should ignore these overrides.
– Checking in a second override of a business rule before checking in the first override does not allow the second override to show in the Global Explorer.  Both are overrides of the same rule.  Check-in of the first override should be completed before a second one is initiated.
– On the ValuesScreen editor, several elements are not displaying the default fund immediately when the element is dropped onto the screen.  The elements and sub-elements are FundDetails (Exclude Fund), FundDetails (Include Fund), DepositDetails (Exclude Fund), DepositDetails (Include Fund).  They should display the first fund listed in the fund drop down list.  Workaround:  Use the XML Source pane.
– When creating a new Fund, the length of the Fund name is 200 characters.
– After deleting an OIPA user in the Rules Palette, the user is deleted from the database, but a null pointer exception is seen. After hitting the OK button on the error message, the Rules Palette performs as normal and the user is deleted in the database.
– The Palette will allow the creation of Function overrides.  Function overrides are not supported in the base product.  The user should not create Function overrides.  
– The MixedMethod option is available on the Allocation visual editing pane but should not be used.  It is not a supported attribute in the Allocation screen. 
– Resolve Rule Action fails when a Copybook is in the XML of the Segment screen, Batch screen, EligibleTransactionsByPolicyStatus, Segments, or Function.  The user must open the CopyBook directly to see content.
– The Resolve Rule right-click option is available on Error Catalog, Market Maker, Countries, System Date, and Rate group editors.  The user should not select this option.
– In Release Management, when checking in a rule or deleting an existing rule, the "Add to CP" window appears with two options (select an existing package or include in an existing one). When the option to select an existing package is chosen, the new package name entry field is still enabled, but should not be used.  This may be confusing to the user as it may seem as if an entry is needed.


************************************************************************************ 

Oracle Customer Support

If you have any questions about the installation or use of our products, please visit the My Oracle Support website: https://support.oracle.com, or call (800) 223-1711.

Copyright  2009, 2011, Oracle and/or its affiliates. All rights reserved.

Copyright Notes:
Jep is a trademark of Singular Systems.




