Hi,
I'm using Blue Prism with an application that has separate Development, QA, and Production environments. The different environments are of the same version and appear visually identical but sometimes produce different identifiers when spied in Application Manager. We handle this by spying the objects in each of the environments and, when difference are found, we add multiple actions to the wait stage that detects the existence of the object (i.e., if all three environments produce different identifiers for the same window, the wait stage has three actions to wait for each of the window identifiers). Only one version of the window will actually appear and, if we need to interact with objects on the window that also have different identifiers, we have three functionally identical code paths that merge back together when the interaction reaches an object that has the same identifier in the different environments.
What I want to know is whether Blue Prism waits for the different actions sequentially (wait for action 1 and, if the object does not appear, wait for action 2 and, if the object does not appear, wait for action 3) or simultaneously (wait for any of the three objects to appear, regardless of the order of the action). If the wait is simultaneous, I don't need to worry about the order of the actions but, if it is sequential, I should ensure that the Production action always appears first for performance reasons.
Thanks,
Michael Bailey
I'm using Blue Prism with an application that has separate Development, QA, and Production environments. The different environments are of the same version and appear visually identical but sometimes produce different identifiers when spied in Application Manager. We handle this by spying the objects in each of the environments and, when difference are found, we add multiple actions to the wait stage that detects the existence of the object (i.e., if all three environments produce different identifiers for the same window, the wait stage has three actions to wait for each of the window identifiers). Only one version of the window will actually appear and, if we need to interact with objects on the window that also have different identifiers, we have three functionally identical code paths that merge back together when the interaction reaches an object that has the same identifier in the different environments.
What I want to know is whether Blue Prism waits for the different actions sequentially (wait for action 1 and, if the object does not appear, wait for action 2 and, if the object does not appear, wait for action 3) or simultaneously (wait for any of the three objects to appear, regardless of the order of the action). If the wait is simultaneous, I don't need to worry about the order of the actions but, if it is sequential, I should ensure that the Production action always appears first for performance reasons.
Thanks,
Michael Bailey