Entity Links Should Have Different SQL Behavior/statement For Search And Editable Forms
Last updated on SEPTEMBER 16, 2016
Applies to:Oracle Communications Unified Inventory Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Client has raised the point of having different behavior for all Drop-Down Characteristics (for simple but especially for Entity Links).
Example: When the user is editing or creating a Place/Logical Device/etc, he would like for an Entity Link/Drop-down Characteristic only specific values in the list because he would like to avoid having the user set up specific values. Specific values should be set only via a Ruleset. This does not mean however the user shouldn't be allowed to query by all the possible fields taken by that Characteristic. I hope this makes sense through the below example:
For a "ToponymicalAddress" Specification Place from our MAD 2 Model: Id_ZoningResolution ("Status Zonare") takes following values during Edit/Create: "No subject of Zoning", "Pending for Zoning". A ruleset auto-populates also the value "POP set" in certain conditions on that Place.
When the user is querying by Id_ZoningResolution he would like to use also the "POP set" value as a search criteria. Currently UIM does not support that and client would like to enhance this behavior.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms