CODEWITHSUNDEEP
abapwebdynpro
lerugoff
lerugoff

Reputation: 21

Where and how should authority checks in a WebDynpro application happen in order to enable or disable controls?

There are several screens in Web Dynpro, on which certain fields and buttons, which, depending on whether the user has an object of authority, should be active or inactive.

I have an authority object with the ACTVT field. Various actions are prescribed there ("Change", "Delete", "Create", etc.) For example, there is an "Edit" button on the screen. For users who have this permission object, this button is active, for those who do not have this object, the button is not active. When a user enters this screen, as I understand it, there should be a check - whether he has this authority object or not. And now I don't quite understand where this check should be carried out

So far, I know very little about Web Dynpro technology. I studied documentation, small courses and searched for everything that is on the Internet. I do not understand where it is better to start and where exactly to implement the AUTHORITY-CHECK OBJECT check.

Upvotes: 2

Views: 468

Answers (1)

Daniel
Daniel

Reputation: 21

Long time ago, but maybe still of interest...

You should implement your authority check in a class. Call this in your WD application in the WD_INIT of the highest component controller. So you can share this information by the context. Now you can disable/enable your UI elements based on this information.

Upvotes: 0

Related Questions