Can not generate action by NBAD Scheduler

General
,
1

Hi all,

I am facing some weird issues in one of the actions.

When I run NBAD Scheduler for 1 customer, it’s not generated action. But when I run a Multichannel campaign with strategy Trigger_NBA_TopLevel. it generated action for that customer.

So I compared the data flow for both, I see for NBAD scheduler, the record is getting dropped between GOS_NBA_TopLevel and Has Offers as belowdf.png

GOS_NBA_TopLevel is a startegy that calling Trigger_NBA_TopLevel

Anyone has an idea about the issue?

Thank you

2

Hi @Intandhp

we have built a comparison testing tool as part of the GOS_NBA_TopLevel ruleform - you can use that to troubleshoot whether indeed these two strategies produced different results for your scenario.

If indeed the results are different, pls go check the Guardrail warning report and pay attention to Strategy warnings that complain about “Strategy Compatibility”.

Otherwise, it might be more complex to look into, in which case better to raise an INC to engage with our customer support team.

Cheers

3

Hi @CHENQ,

I use the compare tools and get result for optimized run it is not generating the action

comparison.png
comparison.png338×123 3.81 KB

When I check the Guardrails, there is no complaint about Strategy Compatibility, most of the complaint are warning of pega unit warning and duplicate property mapping.

Regards,

Intan

4

Hi @CHENQ,

I found one of the decision tables is not optimized with the warning as below

not optimized.png
not optimized.png272×108 4.09 KB

Do you have an idea why it is not yet converted or only partially converted?

Regards,

Intan

5

Hi all,

I want to update this issue. I’ve solved the issue by changing the function in one of the decision table that I created. I replaced the empty property checks from “!=” into “PropertyhasValue()” function.

Also, this is the link that might be helpful related to global optimized strategies:

https://docs-previous.pega.com/decision-management/86/functions-supported-optimization

https://docs-previous.pega.com/decision-management/86/optimizing-strategies-allow-list-functions

Thank you all

6

Hi @Intandhp,

In short: the “not-optimized” warnings shouldn’t be too much of a concern for you as a Strategy designer, if the “Set Property” feature is not used by the Decision Table rule.

We are continuously converting more shapes into the optimized engine - hence the “not-optimized” warnings about components are just indications that our progress hasn’t reached that component type yet.

Regards,

Qingwen