AnsweredAssumed Answered

Evaluating Document Library Actions based on User Attributes

Question asked by vamirr on Sep 11, 2015
Latest reply on Dec 21, 2015 by art99trash
I'm attempting to restrict the availability of certain document library actions based on user attributes.  For example, if a user works for one company, show action A, if the user works for another company, show action B. 

I'm usually writing java code against the repository; doing so for Share is a learning curve.  Right now I have an empty custom class extending BaseEvaluator wired up for the two actions.  The context in BaseEvaluator seems a little sparse.  How can I go about accessing user attributes from the BaseEvaluator evaluate function?  If that's not possible, how can I go about adding the values I'm interested in to the JSON that is passed to the evaluate function?

Outcomes