Question
Anamata
ES
Last activity: 1 Jul 2020 9:20 EDT
Proposition Property not appearing in the Decision Data
Hello
In the Decision data I have a proposition property that is not shown while exporting the decision data into csv or xls file.
It seems something with the UI?
Can you indicate me what to do? We need to populate lots of propositions and it is easier exporting - importing it...
Thanks!
***Edited by Moderator: Pallavi to update platform capability tags***
Pegasystems Inc.
IN
Hi,
Can I get a bit of a context? From the tag, I'm assuming you are trying this on Pega platform version 7.3.1 and CDH 7.31? Kindly confirm.
Also, the steps to reproduce alongwith a screenshot or two could help.
Thanks
Girish
Anamata
ES
Yes,
We have a decision data with a lot of propositions. We we click the proposition it should appear all the proposition properties (properties), that we need to fill with values, like L1, V3, ticking the Active, preceeding day = 3, etc.
Amongst all these proposition properties there is one that is not appearing. It is invisible basically. The property that is invisible is called: pyActiveProposition.
This pyActiveProposition appears in the Form (second tab from the Decision Data), but not in the first tab.
While exporting all the decision data into a csv. file, we see the column of pyActiveProposition in the csv file, but when we fill this column, save the file, and import the file in the Decision Data. It gives an error saying: pyActiveProposition is not found.
I have been told that I need to add a property in the Historty - Custom Field for pyActiveProposition proposition Property in order to fix it. But this property is in the baseclass.
Please help!
Updated: 1 Jul 2020 5:52 EDT
Pegasystems Inc.
IN
I hope you actually mean the property pyIsPropositionActive when you say pyActiveProposition? If yes, then this behavior is not expected.
pyIsPropositionActive is a Pega managed property; so you do not have to add the custom field in the History tab of the property rule form.
Can you please raise an incident so that either our customer support team or the SME team can take a closer look? In fact, I tried this in a platform 7.3.1 system with Pega Marketing 7.31 installed and I was not able to replicate the issue.
Thanks
Girish