Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Joost Spekschoor (JSPEKSCH) Achmea LSA - Solution Architect Pega Marketing
Achmea
NL
JSPEKSCH Member since 2011 15 posts
Achmea
Posted: Aug 6, 2019
Last activity: Sep 24, 2019
Posted: 6 Aug 2019 10:50 EDT
Last activity: 24 Sep 2019 15:45 EDT
Closed
Solved

Added decision data properties not showing on auto generated form in Revision Management

Report

Hi,

In our Pega Marketing environment we are using Revision Management.

From the decision data record perspective we add custom SR-properties on the form tab in the context of a revision. This is succesfull after installing a hotfix.

Now we want to see these added SR-properties back on the automatically generated form (pyeditelement) when adding an proposition in the decision data record.

However the default pyeditelement section is shown.

How do we force a new generated form?

Kind regards,

Joost

***Edited by Moderator: Lochan to add SR tag***

Pega Marketing Low-Code App Development Decision Management Support Case Exists Support Case Created
Roselin Hanumanthaiah
Posted: 4 years ago
Posted: 7 Aug 2019 4:36 EDT
Prabhukiran Lekkalapudi (LEKKP) PEGA Manager, Software Engineering, Decisioning Operations
Pegasystems Inc.
IN
Report

Hi Joost,

What version of Pega Marketing are you using and what is the PRPC paltform version?

You have mentioned that you have installed a hotfix. Please let me know what is the hotfix number and what it is for.

Also i would like to know how you are adding the properties to the form tab. Are you selecting from the list of already available properties on the form tab or are you creating new ones from the form tab and adding them?

Thanks and regards,

Prabhu
Posted: 4 years ago
Posted: 7 Aug 2019 5:10 EDT
Matta Reddy Mannem (MANNM1) PEGA Director of Software Engineering
Pegasystems Inc.
IN
Report

Hi Joost,

Saving the rule in change request will force the re-generation of pyEditElement.

Apart from the information Prabhukiran was asking for, could you please check if the property is a Proposition Property? Please verify pyDecisioningItem custom field value from history tab of the property.

Thanks & Regards,

Matta 
Posted: 4 years ago
Posted: 7 Aug 2019 5:21 EDT
Joost Spekschoor (JSPEKSCH) Achmea LSA - Solution Architect Pega Marketing
Achmea
NL
Report

Saving the rule in change request will force the re-generation of pyEditElement.

With rule you mean Decision Data Record I guesse? This is also the behaviour I expect but this doenst happen when saving the rule.

Please verify pyDecisioningItem custom field value from history tab of the property.

When creating a SR property this setting is not set on default. We manually set this custom field on the property tab.
Posted: 4 years ago
Posted: 7 Aug 2019 5:16 EDT
Joost Spekschoor (JSPEKSCH) Achmea LSA - Solution Architect Pega Marketing
Achmea
NL
Report

What version of Pega Marketing are you using and what is the PRPC paltform version? 

731 Both

You have mentioned that you have installed a hotfix. Please let me know what is the hotfix number and what it is for.

Adding fields to the Form tab on a Decision Data rule via a Revision Management Change Request is not working. As soon as we add a field, we see a warning about the generated form, and the Save button has no further effect.

Apply HFix-54949 
This hotfix was provided in SR-D26003

Show More

What version of Pega Marketing are you using and what is the PRPC paltform version? 

731 Both

You have mentioned that you have installed a hotfix. Please let me know what is the hotfix number and what it is for.

Adding fields to the Form tab on a Decision Data rule via a Revision Management Change Request is not working. As soon as we add a field, we see a warning about the generated form, and the Save button has no further effect.

Apply HFix-54949 
This hotfix was provided in SR-D26003

Also i would like to know how you are adding the properties to the form tab. Are you selecting from the list of already available properties on the form tab or are you creating new ones from the form tab and adding them?

We tried multiple situations:

- We selected existing SR properties
- We created new SR properties in current revision
- We created new SR properties in a previous revision and imported them 
- We created SR Properties with and without the custom field pyDecisioningItem : PropositionProperty

We expect this functionality to be working with Revision managment but dont seem to get it working.


Show Less
Posted: 4 years ago
Posted: 8 Aug 2019 1:46 EDT
Prabhukiran Lekkalapudi (LEKKP) PEGA Manager, Software Engineering, Decisioning Operations
Pegasystems Inc.
IN
Report

Hi Joost,

We verified this issue in our local 7.3.1 marketing systems and were able to reproduce it. Are you facing this issue in a customer environment? If so which customer?

This issue has been fixed in 7.4 and if you are facing this issue in your local environments, will you be able to upgrade to 7.4?

If it is for a customer please raise SE so that we can deliver a hotfix.

Thanks and Regards,

Prabhu
Posted: 4 years ago
Posted: 12 Aug 2019 4:17 EDT
Alex Burt (BURTA) PEGA Principal Product Manager, Decisioning Operations
Pegasystems Inc.
GB
Report

Hi,

Joost is from Achmea.

@Joost, please raise an SR - reference this post also.  They will create an SE from that.

Thanks, Alex

 
Posted: 4 years ago
Posted: 12 Aug 2019 4:35 EDT
Joost Spekschoor (JSPEKSCH) Achmea LSA - Solution Architect Pega Marketing
Achmea
NL
Report

Hi all,

I created an SR with the following number :

SR-D37090  

Kind regards,

Joost

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice