Data Quanity and the use OSM Behaviours
(Doc ID 2608121.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Communications Order and Service Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Consider this scenario:
There are around 2500 fields created in the dictionary to support the solution
The solution has many manual tasks that extends from a base task. They are reused in different orders located in different cartridges.
There is an issue where the end user sees a great deal of information on the OSM Webui task client that they shouldn't see.
The end user should only see in each manual task the representative information based on the product being provisioned and on the type of transaction.
Additionally, there has been a rule to set a field as read only or not. The rules are based upon the type of transaction and product to indicate which field should be visible and editable.
All these rules that the customer has passed to us have been placed in a database-level table and with a DataInstance behavior we evaluate such a field to know if it should be shown or not and if it is editable or not.
The Question is: Taking into account the large number of custom fields defined and knowing that we have to put a datainstance to each of them, making a request to the database, which is the most advisable to use the datainstance to access to a database or access an xml file?
Is there any impact at the performance level (memory consumption, storage) on the use of these behaviors for each field?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document