This content has been marked as final. Show 6 replies
any responses please?
I am not aware of any way to get this type of information regarding rule performance. If there is a way, I'd be interested to know as well.
Have you tried posting to the configsig user group forum? You might get more visibility from a wider set of users. You can find the forum at: http://configsig.com/
You can check that by querying the data from the following table
To understand the number of lce lines created for a rule, we need to look
for occurance of a rule's reason_id in lce_text...
a) First find the reason_id for rule in question.
b) Then use it query below... in sql developer Run as script for
select lce_text from cz_lce_texts where lce_header_id in (
select lce_header_id from cz_lce_headers where devl_project_id
=<DEVL_PROJECT_ID OF MODEL> and deleted_flag='0')
and lce_text like '%REASON_ID%'
some times,the way you write the rules may lead to Cartesian product of the result which will have an impact on the Runtime.
You can write the rule and check the cz_lce_texts for that model. If the rule results the Cartesian product
Thanks for your help.
thanks for the query. It was helpful
Above query is good to analyse details.1 person found this helpful
Just to give some idea....
Configurator understands basic rules only like Implies, Excludes etc.
Whatever rule you write based on loop iteration, results in individual rule for Configurator Engine, they are all made simple rules like Implies/Excludes during login generation. So your number rules will grow even if you are writing one rule using iterator.