Hi Sam,
Whenever you are working with the design of an application modeller for any application, the ordinal depends on the number of fields that are available at that point of time. In case your application is not dynamic then whatever ordinal value you provide at the design time should be valid even for executing such kind of automation flows as well.
So ordinal value needs to decided based on a hit and trial approach till you are able to spy it effectively. However, if in future the UI of the application changes or get updated, the same ordinal value would again need to be tweaked.
We employed a logic in one of the desktop applications, where what we did was we used an increment logic with exception handling such that the bot would try to check for the element for ordinal values between 1 and 8 since we knew at times, between this range the ordinal changes at times. Something similar you guys too can approach.
------------------------------
----------------------------------
Hope it helps you out and if my solution resolves your query, then please mark it as the 'Best Answer' so that the others members in the community having similar problem statement can track the answer easily in future
Regards,
Devneet Mohanty
Intelligent Process Automation Consultant | Sr. Consultant - Automation Developer,
Wonderbotz India Pvt. Ltd.
Blue Prism Community MVP | Blue Prism 7x Certified Professional
Website:
https://devneet.github.io/Email: devneetmohanty07@gmail.com
----------------------------------
------------------------------
---------------------------------------------------------------------------------------------------------------------------------------
Hope this helps you out and if so, please mark the current thread as the 'Answer', so others can refer to the same for reference in future.
Regards,
Devneet Mohanty,
SS&C Blueprism Community MVP 2024,
Automation Architect,
Wonderbotz India Pvt. Ltd.