Login Workflow Automation Without Element Exists and Conditional Branching

Help Studio
1

RPA Scenario – RPA Best Approach Needed

Target URL: https://acme-test.uipath.com/login

Objective: Automate the login process with different conditions, avoiding the use of Element Exists activity and Else If branching logic.

Test Cases:

1.Successful Login– Valid username and password.
2.Invalid Credentials– Incorrect username or password.
3.Login Page Not Loaded– Page fails to load or times out.
4.Forgot Password Flow– User clicks “Forgot Password” and initiates recovery.

Requirement:
Looking for an optimal approach in RPA (preferably using UiPath) to handle the above scenarios without using Element Exists and Else If conditions.

2

You should be working in modern, and using Check App State.

3

They function similarly, and as I mentioned earlier, they should not be used.

4

That doesn’t make any sense. It’s the correct way to do it. Why would the requirements say not to do it the right way?

5

Hi @postwick I’m looking for other solutions to handle this condition. Using ‘Get URL’ is one way to automate the flow, but it fails when the credentials are wrong, since the URL doesn’t change. I’m looking for other solutions to handle this condition. Using ‘Element Exists’ causes unnecessary delays, especially when the fourth condition matches before the others.

6

Not if you do it inside a Parallel or Pick Branch.

7

You can use Ui related trigger modern activities like Element State Change Trigger or Element Attribute Change Trigger etc.

8

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.