Setting Metadata Permission

[travis....@teknion.com]

Metadata permissions require you to save them twice in order to save. I have an organization with id = 221934. A user is apart of this organization if the superuser checkbox is checked in their metadata. The menu bar for an application has a few links that has a visibility set to ${has_right('221934')}. If I am giving a user access to superuser I have to go into their metadata, hit edit, check the box, hit save, then go back in and edit/save again without making any changes for the first check to take affect. This issue was not there before, perhaps something was overlooked in the latest patch.

[Bidisha Das]

Hi,

Can you please explain clearly what exact problem you are facing? What do you need to save twice?

From your explanation,what I could get is you have added a field "Superuser" with type boolean in user metadata and you are filtering the users on basis of that.An user is included in the organisation only if the Superuser field in his metadata is checked.

If this is the scenario,let me know how you did it? Also,how are you giving the access rights to the users ? I could not get what you meant by saving twice?

Please clarify on the above queries so that I can help you further.

Thanks & Regards

Bidisha

[Travis Vliegen]

Yes, what you have recapped is correct. To further explain, each user has a class in their metadata called, app_cara. This class has an attribute called superuser, which is a boolean. An administrator would add users to the RMP application. This admin would have to manually set the permissions of each user. In this case, if an admin wanted to give a user access to everything then he would assign them 'superuser' privileges, doing so by checking the superuser checkbox in that individuals metadata.  

In the superuser organization the code looks like this => ${get_user_metadata().app_cara.superuser} . If that evaluates to true then the user has superuser privileges. 

Now, the issue is that when an admin physically goes into the user's metadata on the actual RMP ide to check the box the privilege is not set and the condition above evaluates to false. However I have noticed that if I was to then go back into that same user's metadata and click on the edit icon then the save icon, without editing anything, then the previous change would take affect. I will point out that the checkbox from the previous change does show that it was checked. It is only when I actually go to test that I can not see a change in permissions.

When I say test, I mean I open the RMP application as a superuser and what I expect to see are the header links which have permissions set as such; "visible" : "${has_right('221934')}", ( 221934 is the id for the superuser organization). I do not see these links on the first save attempt, but I do after I edit/save again. 

I hope this clears up and confusion. 

Thank you for your time and I look forward to your response,

Travis Vliegen 

--
Fujitsu - RunMyProcess
---
You received this message because you are subscribed to a topic in the Google Groups "Fujitsu RunMyProcess Developer Community" group.
To unsubscribe from this topic, visit https://groups.google.com/a/runmyprocess.com/d/topic/supportforum/QscXDMS-6LY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to supportforum...@runmyprocess.com.
To post to this group, send email to suppor...@runmyprocess.com.
Visit this group at http://groups.google.com/a/runmyprocess.com/group/supportforum/.
To view this discussion on the web visit https://groups.google.com/a/runmyprocess.com/d/msgid/supportforum/CAMGV9zt01A%3Dsr_aTgRYf%2BwY1oHtbh8kfjSJz2cQikOjNE06jeg%40mail.gmail.com.
For more options, visit https://groups.google.com/a/runmyprocess.com/d/optout.

--

Travis Vliegen

teknion.com

Confidentiality Notice: This communication, including any attachments, may contain information that is confidential and privileged. [It may constitute non-public information and is intended to be conveyed only to the designated recipient(s).] If the reader or recipient of this communication is not the intended recipient, or you believe that you have received this communication in error, please notify us immediately by return e-mail and promptly delete this e-mail including any attachments without reading or saving them in any manner. Any other distribution, copying or disclosure is prohibited and may be unlawful. We accept no responsibility for changes made to this e-mail or to any attachments after transmission from our office.