Skip to Content
avatar image
Former Member

Best Practice: Providing Functionalites depending on active User?

I am relatively new to the UI5 Framework and I have a new use-case in my company that I want to implement with UI5 and OData Services.

Basically the application has two functionalities with different stakeholder:

  • Role A is able to create new requirements
  • Role B is able to check the requirements and update them with new information

How can I implement this the best way? My previous thoughts on that:

Possibility 1:

I have the OData Service in the Backend that is used by two separated application depending on the role. The access is controlled through the launchpad over the PCFG objects. So a specific user can only use the application that he actually needs. I believe that matches the basic granularity of Fiori apps. On the other hand, it invalidates the DRY principle since I would have redundant code like most of the view.

Possibility 2:

I check in the UI5 Framework which user is currently using the app and enable/disable the required controls in the controller class. I haven’t come across on how to do this. Is there a way in the framework to check which PCFG object is used?

What is the correct way to implement such a use case? Is there a better option that I am not aware of? I would appreciate any thoughts on that matter, thanks J

Best regards

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers