[Bug]Not able to identify the Components using UTAM page Object for salesforce

[girish-kadambari]

Actual behavior

• Unable to compile a Page Object

• Invalid generated code

• Runtime error

What is your expected behavior?

Steps to reproduce

Environment

• UTAM: [e.g 1.0.0] vX.Y.Z

• Java Version [e.g 11.0.9.1]
• OS: [e.g. iOS]
• Browser: [e.g. chrome, safari]
• Browser Version: [e.g. 22]
• Test Framework: [e.g JUnit]
• Test Framework Version: [e.g wdio v7.16.11]

Additional context

[kartikperumal]

hi @girish-kadambari Could you please add more information or be more descriptive of what the issue is? Thank you!

[girish-kadambari]

@kartikperumal

I'm currently attempting to automate Salesforce scenarios using Utam for Page Object automation. However, I'm encountering difficulties finding the respective elements. Could you provide insights into whether Salesforce supports all existing page objects for automation with Utam, and if there are any best practices or considerations for handling dynamic elements in Salesforce interfaces?

[kartikperumal]

Thanks @girish-kadambari , So you are using the UTAM Browser Extension tool and it is not able to identify the existing page objects in the page? We could add you to our slack support channel if you can share your email address and it would make it easier to try and debug what's going on. Thank you!

[girish-kadambari]

Thanks @kartikperumal , girish.kadambari@testsigma.com is my email address.

[sandeep-adireddi]

Hey @kartikperumal , I too Have similar issue . I want to know the following

1. Does each component of salesforce page have a page object, and is there an issue with the Chrome extension, or do some components lack a page object?

[jimevanssfdc]

@sandeep-adireddi Not every component of the Salesforce application has a Page Object (PO) available. This is normal, and expected. It is up to individual development teams whether to create and/or publish POs for their features.