ordinal attribute value

[SamLima]

what number value for ordinal attribute means?

------------------------------
Sam Lima
------------------------------

[Devendra_KumarP]

Hi Sam, 
Ordinal value is one of the attribute to select element from application. it depends number of fields on page. you need to update the ordinal number value and highlight the fields to make sure correct field is spied.

------------------------------
Devendra Kumar Prajapati
Tech Lead
Infosys
Chandigarh
------------------------------

[SamLima]

Hi @Devendra_KumarP

I mean what does it mean if the value equals 2 or 4? what should I know about how to decide the number?​

------------------------------
Sam Lima
------------------------------

[VikrantSharma]

Hi Sam,

Ordinal number represents the order in which the element was created by the target application. For example, an ordinal of 1 indicates that the element was created first, of all elements detected in the target application. 

Ordinal number can differ in some special circumstances like if application has a multi-threaded user interface each time its launched or if an element is not present in a different scenario (e.g. update button not available in case of an inactive account).  So, you can update the Ordinal value and try to highlight to find the right Ordinal number if the initial Ordinal number is not working. Please refer the Ordinal section in the below Blue Prism documentation page for more clarity.

https://bpdocs.blueprism.com/bp-6-8/en-us/helpChoosingRequiredAttributes.htm

Hope this helps!

------------------------------
Vikrant Sharma
Senior Solution Designer
Blue Prism
------------------------------

[devneetmohanty07]

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

----------------------------------
------------------------------