Question

1
Replies
47
Views
Sayantan Chowdhury (SayantanC3655)
Capgemini
Lead System Architect
Capgemini
IN
SayantanC3655 Member since 2017 5 posts
Capgemini
Posted: 3 weeks 3 days ago
Last activity: 1 week 3 days ago
Posted: 1 Sep 2021 5:54 EDT
Last activity: 15 Sep 2021 1:51 EDT

Adding legacy webchat conversational process in a casetype copies invalid properties on pyWorkPage

Hi,

Legacy webchat conversational parallel processes have been added in the stages in casetype rule. The case is created through the chatbot and it works properly as configured. However, it is observed that a few OOTB  properties(names below) are set in the work page but the applied to class of those properties are different than the workclass. Open assignments on the case can be submitted in pega portal without any issues but we are getting validation errors when the same assignment is completed though DX api e.g. from custom React frontend.

 

It seems to be a product issue. Any known workaround/fix available ?

 

OOTB properties with different applied to class that are set on pyWorkPage with values -

  1. pyQuestionDropDownType

  2. QuestionMode

  3. pyConversationConfiguration

  4. pxQuestionDataPagePrompt

  5. pxQuestionDataPagePromptValue

  6. pyConversationQuestionFormat

  7. pxQuestionDataPage

  8. pyIsConversationShape

 

These properties are set in embedded pagegroup property pyQuestion in pyWorkPage with appropriate class context.

It seems these are somehow getting copied into pyWorkPage in step 4 of OOTB activity pxSupplyAnswerToQuestion

 

Error returned in response to DX API -

Hi,

Legacy webchat conversational parallel processes have been added in the stages in casetype rule. The case is created through the chatbot and it works properly as configured. However, it is observed that a few OOTB  properties(names below) are set in the work page but the applied to class of those properties are different than the workclass. Open assignments on the case can be submitted in pega portal without any issues but we are getting validation errors when the same assignment is completed though DX api e.g. from custom React frontend.

 

It seems to be a product issue. Any known workaround/fix available ?

 

OOTB properties with different applied to class that are set on pyWorkPage with values -

  1. pyQuestionDropDownType

  2. QuestionMode

  3. pyConversationConfiguration

  4. pxQuestionDataPagePrompt

  5. pxQuestionDataPagePromptValue

  6. pyConversationQuestionFormat

  7. pxQuestionDataPage

  8. pyIsConversationShape

 

These properties are set in embedded pagegroup property pyQuestion in pyWorkPage with appropriate class context.

It seems these are somehow getting copied into pyWorkPage in step 4 of OOTB activity pxSupplyAnswerToQuestion

 

Error returned in response to DX API -

Response Body : {"pxObjClass":"Pega-API-CaseManagement-Assignment" ,"errors":[ { "ID":"Pega_API_055" ,"message":"Validation messages found." ,"pxObjClass":"Pega-API-Error" ,"ValidationMessages":[ { "pxObjClass":"Pega-API-Error-ValidationMessage" ,"ValidationMessage":"The page contains an undefined property: pyWorkPage.pyQuestionDropDownType\nThe page contains an undefined property: pyWorkPage.QuestionMode\nThe page contains an undefined property: pyWorkPage.pyConversationConfiguration\nThe page contains an undefined property: pyWorkPage.pxQuestionDataPagePrompt\nThe page contains an undefined property: pyWorkPage.pxQuestionDataPagePromptValue\nThe page contains an undefined property: pyWorkPage.pyConversationQuestionFormat\nThe page contains an undefined property: pyWorkPage.pxQuestionDataPage\nThe page contains an undefined property: pyWorkPage.pyIsConversationShape\nValidation failed: Errors Detected." } ] } ] }

Pega build - PRPC-8.6.0-101

 

Thanks.

Pega Platform 8.6 Pega Survey Conversational Channels Case Management Cross-Industry Lead System Architect