Entity Links Should Have Different SQL Behavior/statement For Search And Editable Forms (Doc ID 2151802.1)

Last updated on MARCH 18, 2019

Applies to:

Goal

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.

Example:

For a "ToponymicalAddress" Specification Place from the 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.
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.