In Blue Prism's Application Modeller, the Ordinal attribute is the primary tool used to resolve "duplicate match" errors. When multiple elements share identical attributes (like Class Name, Name, or Type), the Ordinal attribute allows the Application Manager to identify an element based on its position in the search order (e.g., the 1st, 2nd, or 3rd instance found). By enabling Ordinal and assigning a specific integer value, you instruct the robot to select one specific instance among the duplicates, ensuring a unique match.

A. Child Count: This identifies how many children an element has; while it can differentiate containers, it rarely provides a unique identifier for standard input fields like passwords.

B. Parent Class Name: This identifies the class of the parent container. If multiple identical fields exist within the same window structure, the Parent Class Name will likely be identical for all.

C. Parent Ordinal: This distinguishes between multiple parent elements. While useful if the parents are duplicates, it does not directly resolve the duplication of the specific child element (the password field) itself.

E. Class Name: The Class Name is often generic for input fields (e.g., "Edit" or "TextBox"). Since the error already states multiple matches were found, the Class Name is clearly not unique.

Blue Prism University: Introduction to Object Design - Application Modeller Section (Version 6.0+), "Working with Attributes and Identification."

Blue Prism Official Documentation: Guide to the Application Modeller, Section: "Attribute Selection," Subsection: "Using Ordinal and Match Index to resolve duplicates."

Blue Prism Academic Support: Foundation Training Guide, Chapter 5: "Object Studio," Topic: "Spying Elements and Handling Duplicate Matches."