Refine variables dependent on user's Department

[JonnyFoster]

Hello team

I'm in the midst of redesigning a catalog item for request to an application that is available to most people within my organisation - (Core Systems). However, there are several access levels within this application that are available and provide access to different areas of the system, however these are specific to a user's role within the company.

Is there a way in which I can restrict which variables appear dependent on the requested_for.department? For example, I don't want our Retail team to be able to ask for access to the Finance side, but they should be able to make requests for roles attributed to the Retail department. 

Thank you

[Ankur Bawiskar]

@JonnyFoster 

missed your response.

yes those fields should suffice and then you can write the dynamic script.

If you feel you can add few fields later based on your script logic.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[JonnyFoster]

Thanks again.

What would you capture in the new table? I guess one row for the permission name, another one referencing the application/ it belongs to and then, perhaps, 'available to' columns for users, departments, etc?

Thanks

[GlideFather]

Hi @JonnyFoster,

please share more details on the design perspective.

Is that form accessed by wide audience?

You can use the catalog client script and apply it on variable (set) or you can create two catalog items and apply different access rules (user criteria). Retail team will see something and others will see something else...

It's too vague to tell you what's better, please share more details

[JonnyFoster]

Hello GF. 

I had considered separate Catalog Items for each department but I feel like there must be a more elegant solution. The form is used by a good 60-70% of the Business. 

I've got a solution limping along for now, which is working nicely, however it's not perfect. 🙂

[GlideFather]

Okay okay, well the Catalog maintenance is always unique and strictly tailored to the style and need the company is using it... 😛 

I remember client who had a set of two different items, one for one specific country and second for all the others. And just a simple variable renaming was nuisance because it was doubled. Then there was new requirement and there were 4 items doing the same thing 😄 2 for that country and 2 for not just that one country 😄

So it's always about the design.... to think of good design is usually more difficult than to go and configure it 😛

But if you would keep one catalog item, catalog client script or catalog ui policy is the way for you to hide/display the variables based on roles, groups or any other conditions