LOV constraining without State Model

View previous topic View next topic Go down

LOV constraining without State Model

Post  Admin on Thu Jan 06, 2011 8:32 pm

User has a requirement that Status can be selected in a certain sequence. For eg, When a record is created, status is defaulted to "New".
From 'New' > Stat1 or Stat2
From Stat1 > Stat11, Stat12, Stat13
From Stat2 > Sta21, Stat11
From Stat11 > Stat3
etc.

Condition: State Model can not be used, Only Configuration and No Scripting. You should not use extra column

Is it possible to do this ? If Yes then How and if No then why ?
avatar
Admin
Admin

Posts : 21
Join date : 2010-02-25

View user profile http://siebelwithmunav.dodiscussion.com

Back to top Go down

Re: LOV constraining without State Model

Post  Admin on Thu Jan 06, 2011 8:34 pm

First of all, make sure that Picklist on the status field is based on PickList Hierarchical BC having Parent as one of the field. If not, then change the picklist BC to PickList Hierarchical.

Create a calculated field “StatusCalc” with calculated value as [Status] where Status is name of field.

In the Status field > Expand Pick Map > Add a row >
Field: StatusCalc, Constrain: TRUE, Picklist Field: Parent, Sequence: 1

In the ‘Validation’ property of Status field > [Status] IS NOT NULL and ‘Predefault’ property > New. This is to make sure that use never changes the value to blank as from blank user can not select any other value.

Go to Administration – Data > List of Values > query for Status Picklist >

Create new values:
Stat1 - Choose Parent as New
Stat2 - Choose Parent as New
Stat11, Stat12, Stat13 – Choose Parent as Stat1 for these three.
Sta21, Stat11 – Choose Parent as Stat2
Stat3 – Choose Parent as Stat11

-Munavvar
avatar
Admin
Admin

Posts : 21
Join date : 2010-02-25

View user profile http://siebelwithmunav.dodiscussion.com

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum