After the most recent O365 update, my outlook script has been failing sporadically. For the test the script is launching the client, then checking for the text at the bottom of the screen that says "connected to Microsoft Exchange". It is using the waitforimage function to wait for the image which contains the word "connected". The recorder is unable to see the text, so I am unable to use a wait for text command which would likely be more robust. After reviewing the screenshots it appears that the client is connected but the words are drawn slightly different (thicker font) on the failed transactions. I'm out of ideas on how to fix the issue and am hoping maybe one of you has run across something similar.
Solved! Go to Solution.
I have not scripted against this particular Outlook feature,
but I can share some considerations that might be helpful to you.
1. Recapture the
image.I would expect that you have already
2. If you are on 12.5
level, disable Advanced Image Processing.In the Reorder menu Tools->Options…->Advanced->Use advanced
image processing->choose False. This
will enforce exact match, pixel to pixel, of the actual image to the image
stored in the Recorder database.
3. Rather than looking
for what should be present, look for what should be absent. If Outlook is not connected, you can look for
image , or just for . Absence of such image would indicate that Outlook is connected. The latter of these two images might work
well with Advanced Image Processing enabled. Since WaitForImage
does not have an option to wait for the disappearance of the image, you may need
to write you own code that would do it using BitmapExists
4. You may also consider using Optical Character Recognition (OCR).
If these suggestions and suggestions you may get from other
forum participants will not allow you to resolve your issue, please consider opening a support