Posted: 18 Nov 2020 16:34 EST Last activity: 25 Nov 2020 9:04 EST
Pega RDA Bot is not working consistently when deployed to production
We have implemented our bot which automates
1. the flow in mainframes application,
2. downloading of file from chrome browser and
3. flow in desktop application.
it is working fine in non prod environment, but getting some issues when deployed to production.
And almost all the issue are related to mainframes application screens. Getting screen is not created error(WaitForCreate --> False) on different screens for different users and its not consistant, sometimes its working, sometimes not. And for some users, not at all getting any issues. Checked match rules(no issues there).
I wonder what could be the issue, any help is appreciated.
***Edited by Moderator: Pooja to update platform capability tag***
You should be sure you have enabled Verbose logging for the TextScreens category at least. That will actually record a copy of the entire text screen to the logs. That can help you identify any differences you have been your screens and what they are seeing in production.
My best advice is to examine your RuntimeLogs to determine what is happening and identify the areas in your code you need to change to address each issue.
WaitForInputAllowed is used for screens where you need to wait until the screen allows your input. I rarely have to use this method. I generally wait for the NewScreenShowing event between screens to ensure the next screen is present.
There is no reason why a robotics process would behave differently between users. By definition it is a repeatable process you've coded for. I have seen variation in text adapters for different users before though as some have different permissions of steps in their screens that others do not have.
Without a careful examination of what is happening though, I cannot really offer much more than to suggest you examine the text screens you see in the logs along with the point of failures to see what might be happening. It is highly likely that you will be able to code for whatever you are seeing, as I have never had a text adapter automation that I could not get working. They are unique in that there's very little variation that the developer can induce, so once you figure out the steps required, it should be possible to automate it.
Would you attach an example error you are seeing and perhaps a screen shot of that portion of the automation? I may be able to give some guidance with that. Just be sure to obscure anything that may contain customer or any identifyng data in the error message.