We have created a few Entity extraction and intent detection models from prediction studio.
It was observed that a section pyEditelement was created by default and all these rules are circumstanced with a property "pyDPCircumstanceValue".
These rules have severe warnings with text - "Circumstanced property does not exist in the class of the circumstanced rule. For internal consistency, choose a circumstanced property in this rule's class or an ancestor."
All these section rules are in class : Data-NLP-EntityModels and I have checked that this property is not in class hierarchy.
What could be the solution to this problem, is it safe to withdraw these rules ?
since all these rules have severe warning the compliance score is heavily impacted.
This section is used in NLP to generate machine learning model. Can you add 'Decision management' tag to get faster response? From my experience it is safe to remove these sections but I'll let the experts comment.
Posted: 2 years ago
Posted: 16 Jul 2020 8:27 EDT
Vikas Raidhan (VikasRaidhan)
Senior Manager, Software Engineering, Customer Service Digital
This is how decision data rules have been in the platform since their inception. The property pyDPCircumstanceValue is present only in the Rule- class hierarchy because the value is set in the decision data rule. Functionally there is no loss if the property does not exist in the Data- hierarchy; but yes it does create a warning.
To add, the property pyDPCircumstanceValue has already been introduced in the Data- hierarchy in Pega 8.4 and later. So, you should no longer see the warning in the latest versions of Pega.
Finally, withdrawing the pyEditElements is not something we recommend. These sections are part of the decision data rule life-cycle and should be left alone to be managed by the system.