What Motivates You to Participate Here in the PSC?
Reply posted on October 15, 2019 by Linoy AlexanderPega
If the recommendation here is to use the Pega repository type in the pipeline, I would strongly recommend against it. While the orchestrator is recommended to be a separate instance, the artifact repository should be its own distinct entity. You can...
Reply posted on October 14, 2019 by NAQUSPega
Hi Currently, we don't have the support to record test cases on case types from built on applications. You can add a test case ruleset for scenario tests in your expense application and record the test çases in that ruleset.-Shahi
Reply posted on October 11, 2019 by LuisMoura
Hi guys, have you tried to click on options icon on columns of report to try to remove column format on those? It seems to be the source of the problem.
Reply posted on October 11, 2019 by Linoy AlexanderPega
I would strongly recommend against migrating applications in-between environments that are on different platform versions. There are always changes to to the Pega runtime, data model and rule assembly in between releases and while we strive for...
Reply posted on October 11, 2019 by Vikas@MultichannelPega
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...
Reply posted on October 10, 2019 by KUMARISNEHA
It is only a select query with Where condition as: WHERE (("PC0".CaseID IS NOT NULL) AND "PC0".TimeStamp >=? AND "PC0".TimeStamp <=?) ORDER BY 10 DESC* only. There are 2 table joins but those are index tables. When...