Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

NBAM Output Template is not picked up following a deployment

SA-14451

Summary



NBAM Output Template rule is not being picked up after being successfully deployed to the target environment.

The NBAM Program is running in the target environment but it does not produce any Output in the table specified in the Output Template. When viewing the list of Output Templates in the target environment via the Channels - Database landing page, there is no Output Templates listed in the landing page even though several exist in the environment.

The issue is not present in the source environment where all the NBAM Program run produces an output to the table specified in the Output Template and all the Output Template rules are visible in the Channels - Database landing page.


Error Messages



Not Applicable.


Steps to Reproduce



1. Package up a ruleset version containing the Output Template.

2. Deploy package to the target environment.

3. Check the Output Template Rule exists in target environment.

4. Check the Output Template Rule shows in the Channels - Database landing page.

5. Run NBAM Program.

6. Check NBAM Program outputs to expected table.


Root Cause



A defect or configuration issue in the operating environment. when a NBAM output template rule is created and saved, there is also a record instance added to PegaMKT-Data-Outbound-TemplateRun-DB class(MKT_TEMPLATE_RUN_DB table).

This class table holds the pzInskey of the latest version of the Output Template rule in the system under TemplateInsKey property. The channels ->Database landing page fetches the list of template rules using a join with this table.

Also when the OutboundMaster Agent (responsible for populating the template destination with records) also runs the same List View as the one from the landing page, hence didnt find any records to process to final destination table of the template rule.

When migrating the template rules from one env to another using a Product rule, it is required to include instances of both Rule-Obj-Template and PegaMKT-Data-Outbound-TemplateRun-DB classes where the pzInsKey of the Rule-Obj-Template rule should be same as the TemplateInsKey of the PegaMKT-Data-Outbound-TemplateRun-DB instance.

Resolution



Perform the following local-change:

​In the Product rule used for migrating the rule to higher env, suggested to
include instances of both Rule-Obj-Template and PegaMKT-Data-Outbound-TemplateRun-DB classes where the pzInsKey of the Rule-Obj-Template rule should be same as the TemplateInsKey of the PegaMKT-Data-Outbound-TemplateRun-DB instance.

 

Suggest Edit

Published October 1, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us