on 02-13-2021 5:57 PM
Hi
As earlier was able to write straight case one is to one combination, on one unique Business scenario need insights in writing multiple conditions vs restrictions.
Vignesh V
**SPEC VALIDATION OLD** [WORKING]
OBJECTS:
CAR IS_A (300) SKEY'1ABC'WHERE VAR1=WE1;VAR2=WE2.
CONDITION:
CAR.TOP='9V' AND CAR.SIDE='1A' OR CAR.DECK='OPEN'
RESTRICTION:
VAR1<>'20',VAR2<>'09'
==============================================================================================
**SPEC VALIDATION NEW** [EXPECTED]
OBJECTS:
CAR IS_A (300) SKEY'1ABC'WHERE VAR1=WE1;VAR2=WE2.
CONDITION:
CAR.TOP='9V' AND CAR.SIDE='1A' OR CAR.DECK='OPEN' ==> CONDITION 1
CAR.TOP in (8V,10V) ==> CONDITION 2
RESTRICTION:
VAR1<>'20',VAR2<>'09'===> RESTRICTIONS FOR CONDITION 1
VAR1<> '09' ===> RESTRICITONS FOR CONDITION 2
Hello vigneshveerasamy,
The way you have written the [expected] logic, those are two separate constraints. The conditions are different and the restrictions are different. It is very common to have multiple constraint objects under a single constraint net.
With that said, if you find yourself trying to maintain too many objects you probably need to re-work your logic. You may also want to consider using a variant table in your restrictions section and try to reduce or eliminate your conditions. TOP | SIDE | DECK | VAR1 | VAR2
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi indie7 ritesh.dube
Thanks for support - Multiple specification constrains handled with variant table concept.
But still exploring.
Vignesh V
vigneshveerasamy,
My limited understanding with constraint say restriction you are applying here is applied to whole conditions , so if you have specific restrictions for individual conditions you need to have separate dependency.
Thanks
RD
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi RD,
Thank you on insights.
Currently proceeded with single objected=> single cluster condition=>single restriction ===> one dependency net.
On additional validation one more is created and mapped for the Dependency as a whole.
Why I raised on single dependency net to handle multiple clusters to reduce end user instances towards
multiple dependency net codification in system.
******Still exploring & RnD this area******
Thank you.
Vignesh V
User | Count |
---|---|
109 | |
15 | |
10 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.