@sundm Absolutely, in fact we welcome any community members who would like to present. Cheri Guadet from CXForward is presenting our November community event.  Please find a link for that event https://community.pega.com/events.  You can access recordings and decks from past events at: https://collaborate.pega.com/discussion/cdh-community-events

@Marcus_D In general, it is recommended for business partners to go through enablement -- to become acquainted with CDH. It can help inform the Migration Alignment Workshop. Also the organizational transformation that @odeht discussed during this session can be very useful.

@Marcus_D @noelj It is highly recommended to upgrade to the latest version. It allows you to take advantage of the latest fixes and features.  The latest versions allow for leveraging the latest enhancements to the product. For example, Version 8.6, introduced Value Finder, Scenario Planner, etc. and are very valuable in accelerating business benefits.

@sundm Lead Decisioning Architect

@noelj Leveraging the structure provided in NBAD, with each of those items provides for the configuration to be forward-compatible.

@modhr1 Yes, multi-tenancy is not currently supported in CDH. It is in Product Management's backlog and is a priority, but not sure about timelines.

@LindaS @Marcus_D LDAs are experienced SDAs who lead the development on CDH. They are a counterpart of the LSA. They work closely with the business team, translating their marketing strategies for CDH implementation.  LDA is not a new role, but it is one that we don't currently have certification or Academy training for as we do for LSA. That said, we are currently developing training programs and certification pathways for LDAs.  This will be released soon.

@Marcus_D@sundm@noelj@sundmIf you are referencing multi-level decisioning, each Action can be designated to be decisioned for a particular context. Also, Action naming must be unique.@sundm ​​Each Action can only used for a single context.@sundm@sundmHere are a couple examples from the Marketplace with Taxonomy examples: https://community.pega.com/marketplace/components/nba-designer-template-insurance, https://community.pega.com/marketplace/components/nba-designer-template-healthcare

@noelj In that instance, it sounds like you have two different actions, if the engagement policies differ. What is being presented may be ""the same,"" but creating two Actions sounds like it would support that need more directly.

@Marcus_D @noelj Yes, you should be able to use 8.5 and leverage CDH and NBA-D.

@noelj It depends on the approach, if it's an iterative and phased approach, Dev can likely be leveraged. If it's a ""Big Bang"" approach, a parallel environment would be better.

@noelj Yes, if v8.4 leverages the NBAD and the framework, the upgrade will be largely automated. Rigorous regression testing, etc., after upgrade is a best practice to ensure all extension points are working as expected.

@LindaS @noelj The current GA version is Pega 8.6. NBA Designer and the Framework have added many enhancements from Pega 7.x versions onwards.  The Next Best Action (NBA) Designer in its current form started in 8.4 but we are currently at 8.6.  This presentation highlights some of the differences.

@sundm @LindaS Recordings of past events, decks presented previously, and Q&A can be found at: https://collaborate.pega.com/discussion/cdh-community-events 

@noelj This would likely need to be considered on a project-by-project basis to understand the current structure and if we are moving from NBAD v1 to NBAD v2, etc. If there is a requirement to follow a vertical-specific structure and re-factor the logic accordingly, the template could be beneficial. If the migration is from an existing NBAD v2 implementation, then the template would probably not provide additional value.

@modhr1 The wiki specifically covers a path from custom frameworks from any CDH version to NBA Designer v2 (8.3+), so is not version specific beyond that.

@modhr1 The example I presented is that largest and most successful in EMEA, but I believe there are a number of bigger migrations in North America.

@noelj It would be interesting to further understand the requirement here. If there are attributes, or contextual items about a customer that would/could be leveraged for future decisioning or re-decisioning, those should be captured and become part of Interaction History. From there, IH Summaries can provide a view into that previous learning or interaction with the customer.

@noelj Currently, the Campaigns page is available in NBA Designer to support this requirement, but going forward, Pega encourages clients to transition to an "always on" approach to outbound marketing. The Campaigns landing page will be available to support "one-off" and/or "urgent" communications. The "always on" and omni-channel approach allows clients to leverage machine learning to not only provide the Next Best Action to customers, but also to decide the best channel to communicate with them.

@modhr1 NBA Designer does not account for the existence of a Product Catalogue. At its simplest, pricing would be attributes of the Action to which a product is associated with, allowing for 1:1 Ops Manager to manage OOTB. Anything more complex would be implemented in an appropriate extension point.