UIA Chrome Elements Work in Object Studio, but not in Process

[MarkPulleyn]

Hi

I'm developing a process in SAP C4C, using Chrome and UIA mode in Application Modeller, with the 'force-renderer-accessibility' URL, as recommended.

However, I'm finding that not all identified elements are recognised/retained when the process is ran for Process Studio, even though they may still work when run through Object Studio.

Others are not retained at all.

Example Attributes would be: UIA Name selected as a Wildcard, as it refers to a piece of data (which will be different for each case being processed),
UIA Control Type - Value Data Item
UIA Automation ID - Value is a long mix of numbers, letters and characters

I may also use Match Index.

Any suggestions as this has proved to be very frustrating,

------------------------------
Mark Pulleyn
------------------------------

[PvD_SE]

Hi Mark,

With the risk of stating the obvious:
Could it be that identifying the elements in production takes longer time than anticipated and experienced when developing the solution?

What is the exact exception thrown in production?

------------------------------
Happy coding!
Paul
Sweden
------------------------------

[RaivisLazdāns]

Hi,

That`s actually the first idea that I also had. 
When rendering is enabled it takes more time for elements to get fully loaded and extra wait times might be needed.
E.g. you can not call one navigation after another without waiting for next element to get loaded. 

Best regards,

------------------------------
Raivis Lazdāns
Lead Process analyst/ RPA developer
Europe/Riga
------------------------------

[AmolJangam]

Hi Mark,

I would suggest to go by the html path and specifically use the XPATHs for elements in Browser mode, if possible rather than UIA mode.
However, if it is not possible then provide the intelligent waits before you perform activity in application.

Hope it helps.

------------------------------
amol jangam
test lead
infosys
Asia/Dili
------------------------------