Siebel Business Process & Functionality (MOSC)

MOSC Banner

Controlling attribute values using constraint rules

edited Dec 16, 2016 12:14AM in Siebel Business Process & Functionality (MOSC) 3 commentsAnswered
Hi. Apologies if this or anything similar has been posted before. I'd like to find out if anyone has successfully used constraint rules to restrict the attribute values that are shown. I'm particularly interested in dependencies across attributes from different components. To illustrate, let's say for example,

Component A's Attribute X has the following values: 1,2,3,4,5

Component B's Attribute Y has the following values: 1.1, 1.2, 1.3, 2.1, 2.2, 2.3

If the value chosen in Attribute X is 1, the selection for Attribute Y would then be limited to 1.1, 1.2, 1.3 only.

Thanks in advance. If not feasible, keen to hear workarounds or alternative (or creative) approaches apart from maybe scripting.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center