Reply posted on October 23, 2019 by GeedAPega
Hi, As an alternate solution, you can also use the decision table and data transform to meet your requirement. Regards, Geeda
Hi, The OOTB 'ValidEmailAddress' validation rule will validate only the format " xxx@xxx " We need to perform customization based on business requirement. I have tried the below customization at my end, Create a EditValidate rule...
I'm not sure there is a set number at which the infinite loop will generate a stack overflow. The activities should be designed in a way to prevent infinite loops.
Design files you've downloaded are not a Pega package (like RAP file). It's not a ruleset or something:) You can only review it and follow its guidance
Can you check this link to see if it is helpful: https://community.pega.com/knowledgebase/articles/conversational-channels/installing-pega-ocr-component
Yes, that is correct behavior. We cannot expect natural language processing to detect language from just numbers. It has to be a semantic statement in a given language. However, there is a workaround for your problem. In your case, Text analyzer fails...
Add click event and call Local Action. In the flow action pre-activity you can call service and once got response you map to the property showing on UI. Then you can see the value pre-selected.
Please wait while we search for PDN content that suits your question.