How to deploy context dictionary to other environment
So I was trying to deploy the context dictionary setting via product file, but I was not able to identify what instance of rules to include in the product, in order to move the context dictionary settings.
Any suggestions?.
Accepted Solution
Updated: 17 Sep 2021 3:14 EDT
Pegasystems Inc.
IN
@KanL5414 There is a product rule created with all the context dictionary rules which were generated. On the Context Dictionary screen, if you switch to the Audit Log tab, at the very bottom you will see the link to the Product rule.
CXForward
US
@RaghuShankhawaram Thanks Rahukiran. That worked.
HSBC
IN
@RaghuShankhawaram , Hi Raghu, we have already deployed the context dictionary to higher environment. But as a part of new requirement we added another entity and resaved the context dictionary in Dev.
But when we used the product file generated to deploy the changes , we don't see context dictionary getting updated in higher environments. It still has only old entities. New entity is not showing up and also ruleset is blank .
Any idea why its not showing up?
Pegasystems Inc.
IN
@DharanyaM6431 What version of the platform and CDH are you using?
HSBC
IN
@RaghuShankhawaram We are using PEGA 8.5.3 version. In terms of CDH We are using 8.4
Pegasystems Inc.
IN
@DharanyaM6431 Can you cross-check and confirm the CDH version? I am assuming you are using CDH 8.5 version as we introduced the Context Dictionary product rule in that release.
Also when you say "we added another entity" , can you clarify if you added a new context or added an association to an existing context?
You also mentioned about the ruleset being blank. Can you elaborate on this? Are you saving the context dictionary to the existing ruleset where it was saved earlier or is it a completely new ruleset?
Updated: 2 Aug 2022 1:15 EDT
HSBC
IN
@RaghuShankhawaram We have added new association data and saved the context dictionary into new higher ruleset version. Sorry we are using 8.5 only.
Does a restart will help?
Pegasystems Inc.
IN
@DharanyaM6431 I would suggest raising a GCS support ticket to get this looked into.