Role-based dropdown not working

Hi Neil Conacher 

Definitely the Dependency SetOptions is a good strategy. Indeed we have had been configuring such features for different scenarios, including that issue.

In order to make it working like a charm you need to setup the custom sugarLogic isUserInRoleList.

Place the attached file into folder custom/include/Expressions/Expression/Boolean/

Then go to Admin -> Repair -> run the following actions:

• Quick Repair and Rebuild
• Rebuild Sugar Logic Functions
• Rebuild JS Grouping Files
• Clear Additional Cache

The sugarLogic function isUserInRoleList gets a list of roles by name and returns a bollean, example:

isUserInRoleList(createList("Tracker", "Sales Administrator"))

This way you are able to setup specific dropdown lists for specific roles disregarding the user within.

Regards

Easy peasy!

• The main dropdown list (defined in the vardefs) must accomplish all options. This way Reports will be able to render any options accordingly
• You need to define a SetOptions dependency for values Prospect, Partner and Lead: isInList($account_type, createList("Prospect", "Partner", "Lead"))
• You need to define a SetOptions dependency for value Active Client and generic users: and(equal($account_type, "Active Client"), not(isUserInRoleList(createList("Special Role"))))
• You need to define a SetOptions dependency for value Active Client and special users: and(equal($account_type, "Active Client"), isUserInRoleList(createList("Special Role")))
  
• You need to define a SetOptions dependency for value Inactive Client: equal($account_type, "Inactive Client")

In short words, all possible scenarios must be considered by SetOptions dependencies, the way any SetOptions scenario has its specific DD list.

Good luck!

Hi Andre,

Thanks for your prompt response - I like the Easy Peasy part of it

I'll give that a go.

Just to clarify, I need to to have a separate SetOptions code block for each scenario rather than combining all the logic into one dependency block ?

Neil

Pay attention that the custom expression aren't apply in the mobile app for frontend perspective.

Yes, you need to configure individual SetOptions dependencies once the trigger attribute for each dependency has to have the sugarLogic function to execute its actions.

Thanks Cedric.

Do you know if this is something that Sugar aim to address going forward ?

Neil

Hi Andre

Just to let you know this is now working (just doing some quality control at the moment) and I'll upload the code for the benefit of the community when finished.

One question however.... what is the implication of ("edit", "save") in the 'hooks'

When I've been working with SetRequired I've tended to only use "edit" as a hook

Thanks

Neil

Hi Andre

Just to let you know this is now working (just doing some quality control at the moment) and I'll upload the code for the benefit of the community when finished.

One question however.... what is the implication of ("edit", "save") in the 'hooks'

When I've been working with SetRequired I've tended to only use "edit" as a hook

Thanks

Neil

As far I know the hook 'save' applies only for dependency SetValue.

Regards