How do you scope your Screens in a web application

I am trying to create my object repository with Screens according to this documentation. Technically I am able to create what I need, but I am struggling to find the correct best practice in defining the scope of a screen.

Example from a typical web application: There is a login screen, the login screen shows user name and password text boxes. Once you are signed in, you go to organization selection screen, select an organization and after that you are navigated to a catalog, …

So we have

  • login screen
  • organization selection screen
  • catalog

Now, here is the problem: sometime all 3 screens share the same URL, one of the three screens is displayed dynamically based on your session state (are you logged in or not, organization selected or not, etc..).

In that case, do you create 3 different screens in the object repository or do you create one screen in the object repository?

Bonus question: If you have 3 screens in object repository, how do you check dynamically, what screen is currently displayed? (this gets quite difficult technically as you have to reference elements using the related screen from object repository)

@lukas.arv

Two ways here..1 create 3 screens and use ..or create a 3 screens and use containers to separate the elements for each page ..I would say create single screen if all the attributes are same across and then use containers inside it to have elements separated this way you have a seggregation of elements and also as the screen attributes are same when screen changes you need to change only in one place..

Cheers

thank you Anil! The idea with Containers looks promising, I was not aware of this feature of nesting elements in the object repository.. So I can create App->Screen->Container->Element

1 Like

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