In this blog, I am going to explain how to hide some characteristics which are no longer relevant because of some value in other Characteristic. Though this topic has been discussed here by Ritesh Dube and working perfectly when we write the dependency at Configuration Profile level, I felt it is not working correctly when you assign the dependency to the characteristic.
My example is based on a car configuration process where the user can choose the Engine Capacity from 4 available options , but Accessories are not offered with lower end version.
Requirement is – ACCE should be invisible for Characteristic Value 800 (Engine capacity – 800 cc) but when changed to other three available Engine options, the Accessories option should re-appear.
Created two characteristics ENGINE_CAP and ACCE as below :
|ENGINE_CAP||Engine capacity||800||800 CC|
|ACCE||Accessories||ADL||Automatic Door Lock|
Additionally create a Characteristic HIDE_CHAR with reference Table-Field SCREEN_DEP-INVISIBLE as below –
Create a Procedure dependency HIDE_CHAR_DEP as below :
$SELF.HIDE_CHAR = ‘ACCE’
Assign this dependency to Value 800 characteristic ENGINE_CAP.
Now, to check the effect open CU50 – Configuration simulation –
Initially, both characteristics are appearing. Now enter 800 in Engine capacity –
Accessories characteristics has disappeared now as you can see in above picture.
This will re-appear when the Engine capacity value is changed to some other value , say 1000 –
Hope this helps.