[Answered] User Access rights

[dlstrawn]

[sean.lanktree]

I can think of two different paths you could take.

1.) Upon starting up your application, make a call to the back-end to retrieve the authority setting for that user. You could extract the user using vvUtility_getCurrentUser and maybe go to a database and return back the authority. Based on the response, you would toggle the functionality (hide/show buttons, disable/enable inputs, etc....).

2.) Create 2 app records within Portal Admin for this app. Under the "Settings" section when adding the new app, there is input for "Optional Parameters". Set this value for one app as "editable=true". Then assign this version of the app to users who are allowed to edit and the other version (without this parameter) to those who may not edit. Then within your app, use Ext.getUrlParam('editable') and toggle the functionality based off of its value.

[dlstrawn]

ok, I like method 1... it would be nice if it were part of the portal! :)

[TerryB]

For what it's worth, I've handled that situation by not trying to manipulate the UI and just checked the users authority when server is called to update something. If user not allowed to do that, just ignore the update and return message saying they are not permitted to make changes. Doesn't require any extra server calls or extra code on front end whatsoever. Unless your users aren't sure if they are allowed to update...? For me, it's on stuff like Customer Master. Sales people can update Address info and most other info on file. But only A/R accountant can change terms. I sure wasn't creating a separate pgm just to handle that.