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

 Marcelo Marote (MarceloMarote)
futureproofAI

futureproofAI
US
MarceloMarote Member since 2012 5 posts
futureproofAI
Posted: Sep 28, 2019
Last activity: Oct 2, 2019
Posted: 28 Sep 2019 10:31 EDT
Last activity: 2 Oct 2019 14:45 EDT
Closed
Solved

Deploying a modified Marketing Output Template DB

Hi guys,

We are on Pega Marketing 8.1 on Pega Cloud.

We are writing our NBA execution results to a Postgress table via the Output Template rule.

At some point we added new fields to the Output Template, but we are experiencing issues to (1) get the Postgress table updated with the new columns and (2) deploying the code to higher environments.

(1) MAKING THE CHANGES IN DEV

This is what we are doing so far, but I would like to ask if there is a better way of doing it.

  1. We made the changes to the Output Template (say adding 1 new property and its mapping)
  2. Opened a Pega SR to get the Postgress table dropped or renamed (again, since we are in PegaCloud, we are not able to drop the table ourselves)
  3. We deleted the Database Table instance
  4. We ran the NBA, which qualified some offers associated to the modified Output Template

RESULT: The Database Table and physical Postgress table are re-generated again. The NBA results are successfully written to the table. All good. But is there a better way?

(2) DEPLOYING THE CHANGES TO STAGE/PROD

Here we are having some issues. We are trying 2 approaches but none of them are working right now:

APPROACH 1 (letting Pega regenerate the Table)

Show More

Hi guys,

We are on Pega Marketing 8.1 on Pega Cloud.

We are writing our NBA execution results to a Postgress table via the Output Template rule.

At some point we added new fields to the Output Template, but we are experiencing issues to (1) get the Postgress table updated with the new columns and (2) deploying the code to higher environments.

(1) MAKING THE CHANGES IN DEV

This is what we are doing so far, but I would like to ask if there is a better way of doing it.

  1. We made the changes to the Output Template (say adding 1 new property and its mapping)
  2. Opened a Pega SR to get the Postgress table dropped or renamed (again, since we are in PegaCloud, we are not able to drop the table ourselves)
  3. We deleted the Database Table instance
  4. We ran the NBA, which qualified some offers associated to the modified Output Template

RESULT: The Database Table and physical Postgress table are re-generated again. The NBA results are successfully written to the table. All good. But is there a better way?

(2) DEPLOYING THE CHANGES TO STAGE/PROD

Here we are having some issues. We are trying 2 approaches but none of them are working right now:

APPROACH 1 (letting Pega regenerate the Table)

  1. We created a Product rule with the new code, which also contains:
    1. the modified Output Template rule
    2. the required Properties mapped in the Output Template rule
    3. the DataTableEditorReport report definition corresponding to the Data Type
  2. We deployed the Product rule
  3. Opened a Pega SR to get the Postgress table dropped or renamed (again, since we are in PegaCloud, we are not able to drop the table ourselves)
  4. Once the table has been dropped, we deleted the Database Table instance
  5. We ran the NBA, which qualified some offers associated to the modified Output Template

RESULT: Initially the Database Table and Postgress table were created, but we forgot to include the new Property in the Product rule, so the table was missing a column. We repackaged and redeployed and followed the same steps, but now nothing is being generated (the Database Table and the physical Postgress table are not being created).

APPROACH 2 (including SQL for new table as part of deployment)

  1. We created a Product rule with the new code, which also contains:
    1. the modified Output Template rule
    2. the required Properties mapped in the Output Template rule
    3. the DataTableEditorReport report definition corresponding to the Data Type
    4. AND VERY IMPORTANTLY, the Database Table instance (which will make Pega run the CREATE TABLE SQL during Package Import)
  2. Opened a Pega SR to get the Postgress table dropped or renamed (again, since we are in PegaCloud, we are not able to drop the table ourselves)
  3. Once the table has been dropped, we deployed the Product rule (which includes the CREATE TABLE SQL)
  4. We re-saved the Database Table instance
  5. We ran the NBA, which qualified some offers associated to the modified Output Template

RESULT: The Postgress table is there but NO offers are being saved to it.

Any help would be greatly appreciated.

Thank you!

Marcelo.


Show Less
To see attachments, please log in.
Pega Marketing

  • Ahmed Al Abrashee

Accepted Solution

Posted: 5 years ago
Posted: 29 Sep 2019 10:43 EDT
Marcelo Marote (MarceloMarote)
futureproofAI

futureproofAI
US

We got the Deployment working. We did the following, but is there a simpler way? Thanks!

(2) DEPLOYING THE CHANGES TO STAGE/PROD

This is what we finally did to get it working:

APPROACH 1 (letting Pega regenerate the Table)

Show More

We got the Deployment working. We did the following, but is there a simpler way? Thanks!

(2) DEPLOYING THE CHANGES TO STAGE/PROD

This is what we finally did to get it working:

APPROACH 1 (letting Pega regenerate the Table)

  1. We created a Product rule with the new code, which also contains:
    1. the modified Output Template rule
    2. the required Properties mapped in the Output Template rule
    3. the DataTableEditorReport report definition corresponding to the Data Type
    4. AND the PegaMKT-Data-Outbound-TemplateRun-DB instance automatically generated by Pega from the Output Template rule (but we are pretty sure this is not needed, since we deleted in step 7 below)
  2. We deployed the Product rule
  3. Opened a Pega SR to get the Postgress table dropped or renamed (again, since we are in PegaCloud, we are not able to drop the table ourselves)
  4. Once the table has been dropped, we deleted the Database Table instance
  5. We ran the NBA, which qualified some offers associated to the modified Output Template
  6. At this point the Database Table and Postgress table were NOT created.
  7. We deleted the PegaMKT-Data-Outbound-TemplateRun-DB instance (deployed as part of 1.d above)
  8. We checked out, saved and checked in the Output Template rule
  9. We verified that a new PegaMKT-Data-Outbound-TemplateRun-DB instance is created.
  10. We ran the NBA again, which qualified some offers associated to the modified Output Template

RESULT: The Database Table and physical Postgress table are re-generated again. The NBA results are successfully written to the table. All good. But is there a better way?


Show Less
To see attachments, please log in.
Posted: 5 years ago
Posted: 28 Sep 2019 11:21 EDT
Marcelo Marote (MarceloMarote)
futureproofAI

futureproofAI
US

Just to provide a bit more info:

The Output Template is defined to append records to:

Database ExternalMKTData
Table STRATEGYRESULTS

 

Also, the Data Type "Data Model" tab does NOT display the newly added Property. If I try to add it, Pega displays an error saying that "The instance already exists".

 

Thanks!

To see attachments, please log in.

Accepted Solution

Posted: 5 years ago
Posted: 29 Sep 2019 10:43 EDT
Marcelo Marote (MarceloMarote)
futureproofAI

futureproofAI
US

We got the Deployment working. We did the following, but is there a simpler way? Thanks!

(2) DEPLOYING THE CHANGES TO STAGE/PROD

This is what we finally did to get it working:

APPROACH 1 (letting Pega regenerate the Table)

Show More

We got the Deployment working. We did the following, but is there a simpler way? Thanks!

(2) DEPLOYING THE CHANGES TO STAGE/PROD

This is what we finally did to get it working:

APPROACH 1 (letting Pega regenerate the Table)

  1. We created a Product rule with the new code, which also contains:
    1. the modified Output Template rule
    2. the required Properties mapped in the Output Template rule
    3. the DataTableEditorReport report definition corresponding to the Data Type
    4. AND the PegaMKT-Data-Outbound-TemplateRun-DB instance automatically generated by Pega from the Output Template rule (but we are pretty sure this is not needed, since we deleted in step 7 below)
  2. We deployed the Product rule
  3. Opened a Pega SR to get the Postgress table dropped or renamed (again, since we are in PegaCloud, we are not able to drop the table ourselves)
  4. Once the table has been dropped, we deleted the Database Table instance
  5. We ran the NBA, which qualified some offers associated to the modified Output Template
  6. At this point the Database Table and Postgress table were NOT created.
  7. We deleted the PegaMKT-Data-Outbound-TemplateRun-DB instance (deployed as part of 1.d above)
  8. We checked out, saved and checked in the Output Template rule
  9. We verified that a new PegaMKT-Data-Outbound-TemplateRun-DB instance is created.
  10. We ran the NBA again, which qualified some offers associated to the modified Output Template

RESULT: The Database Table and physical Postgress table are re-generated again. The NBA results are successfully written to the table. All good. But is there a better way?


Show Less
To see attachments, please log in.
Posted: 5 years ago
Posted: 2 Oct 2019 14:45 EDT
Paul Gentile (PaulGentile_GCS)
PEGA
Principal Engineer, Technical Support, 1:1 Customer Engagement
Pegasystems Inc.
US

As Output Templates are supported with Revision Management, this would appear to be your best approach.

https://community.pega.com/knowledgebase/articles/decision-management-overview/getting-started-revision-management-customer

To see attachments, please log in.

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