We are using Pega Chat 7.31 and would like to map our pre answered questions that arrive in property pyUserData(<key>) to something on the pyWorkpage clipboard and have it display to the user on the work object screen. We also need it so that we can index the properties for search to find it.
How do we add those values into the necessary clipboard page?
Also does anyone know how to add a custom property to the inherited class "PegaCA-Work-Interaction-Chat" so we can have it on the pyWorkpage clipboard and populated from our answers? There must be a DT or Activity we can customize to our business needs.
You caused me a little confusion, as the CPMGetChnSvcsParams is a DT not an activity. Anyways, the problem we have is that the standard OOTB properties are simply not suitable and in the case of ContactId it's not appearing on the pyWorkPage even if set from the pre-chat answers! Nor does it appear in the pyUserData. We are not dealing with Contact and/or Account datasources here as we don't hold that information.
So I want to use our custom properties that inherit from our class in our implementation of Chat. But I need to know how to get our properties onto the pyWorkPage clipboard in order to use them to display on the users view.
The whole OOTB Chat implementation assumes you have contact and/or account information in a datasource and makes decisions based on that fact. We don't nor need those datasources, therefore we need to customise to suit our requirements.
So I would like to know how to influence the properties that appear on the pyWorkPage in order to meet our requirements. Which on the face of it is simply to represent the pre-chat answers to the users screen and to be able to index those properties so we can then search for them later on.
Hi Craig, is that the OOTB version of the CPMGetChnSvcsParams ? I'm looking at our 7.31 version and I see the first step of the DT has a when condition @PropertyExists(".ChannelServicesInteraction.pyUserData"). In your case, It looks like "ChatSvcsChatInteraction.pyUserData". I don't know if that particular page has these properties.
Hi Craig, glad to see it's working. The PegaCPMFS version would seem to be incorrect. I work in the base Customer Service product, so I was looking at the PegaAppCA version. If this is something you wish to have fixed OOTB, I would suggest raising an SR. I'll reach out the FS team internally to make sure it's fixed going forward in the next release. But, if you would like a hotfix for the OOTB version, that will require an SR that they can work against.