topic Re: test and production environment in Product Forum

test and production environment

EwaTurowicz-Kwiatkowska — Fri, 25 Nov 2022 08:28:39 GMT

Hi
Maybe someone faced a similar problem. The process works very well on the application in the test environment. In a production environment, it fails at some stage. I moved the production application to the test environment and the process works. It looks like there is a problem with the environments where Blue Prism is configured. I have an IT department since configuration, and I don't deal with it myself. I don't know what IT should pay attention to and what is the reason for the error. Do any of you have any suggestions? I will be grateful for your support.
Regards
Ewa

Re: test and production environment

PvD_SE — Fri, 25 Nov 2022 09:55:00 GMT

Hi Ewa,

Indeed, your description points to a difference between your test and production environments. This can be quite trivial or more complicated, depending what action crashes and the reason behind the crash. The crashing action should give you and indication on where to look for the problem, the log should provide you with more information on what went wrong.

Happy coding!
---------------
Paul
Sweden

Re: test and production environment

john.hammond — Fri, 25 Nov 2022 11:04:45 GMT

Hi Ewa.
As Paul has mentioned, problems between Production and Development environments can be a relatively quick fix, or something needing a bit more thought. A couple of common things to consider:
- Have you run the process in the Development environment via the Control Room? If you have only stepped through the process in Development, it is very common that sufficient wait stages aren't in place. This would be indicated within the logs if an error along the lines of 'No element matches' or similar
- Check the default selections in the Application Modeller. One of the common attributes selected during development of a web-based process would be 'Web Page Address' - this may relate specifically to the development environment. If this is the case, uncheck this attribute and ensure that each element can still be successfully identified.

If you do receive any specific errors in the log, share them here and we may be able to help further.

Re: test and production environment

EwaTurowicz-Kwiatkowska — Mon, 28 Nov 2022 09:21:58 GMT

Hi

Thank you for your suggestions. I modified the waiting stages and everything looks fine here. The problem is the application field, which for some reason in the production environment is not visible to Blue Prism and the robot cannot select it. I still have an idea for a change, it looks like differences between test and production application. I will try to change the selection of the field using keyboard shortcuts (global send keys).