'Create Request on Behalf Of' Visible Always for Single ARO

Chris_Keander

I'm wondering if it's possible to present the "Create Request on Behalf Of" picker for end users as well as analysts, but only on a particular request offering.

Ideally I'd like to take the query results and multi-map it to a field on the Incident form other than the Affected User.

Nicholas_Velich

Hi @Chris_Keander ,

In order to show the "Create On Behalf Of" picker on only one Request Offering and for all users, you would do the following:

1. Change the AD group setting you mentioned to scope to a group with all of your users. 
2. In the custom.js file, determine which page of the Portal you were on. If on the Request Offering page of interest, do nothing. If you are on any other Request Offering page, hide the entire "Create On Behalf Of" picker using CSS, applied via JQuery (or use .hide()). 

The "what page am I on?" logic can be extracted from the code on the page @Conner_Wood linked above.

The JQuery bits can be referenced here: http://api.jquery.com/css/ Additionally, we hide the text box portion of this picker already through the code referenced above. We could possibly just add a .parent() call to grab the label element in addition to just the text box, although I have not tested that.

Thanks,
Nick

Conner_Wood

I know someone has already altered the way it is displayed, I assume it would be possible to also implement custom pickers, but mapping to another relationship seems a bit much for tweaks and probably requires direct Cireson Support.

Create on Behalf - Function / Customization

Chris_Keander

I saw this post earlier, but I'm afraid it may not do exactly what I'm looking to have happen.  I understand I can change the AD group that presents this user picker, but that is a global change.

I really only want it to show up on one RO and not everything.  I could also look into using a query picker, but when we have tens of thousands of users, there's no easy way to get around the default limitations either.

David_Allen

@Chris_Keander , this is something I would find really helpful to.  As you say, at present the settings are rather global, it would be really helpful to have the Create On Behalf Of field for specific RO's. I also found that using a standard query picker just introduces other problems too.

If you raise it as a feature request, I'll certainly vote it up!

Nicholas_Velich

Hi @Chris_Keander ,

In order to show the "Create On Behalf Of" picker on only one Request Offering and for all users, you would do the following:

1. Change the AD group setting you mentioned to scope to a group with all of your users. 
2. In the custom.js file, determine which page of the Portal you were on. If on the Request Offering page of interest, do nothing. If you are on any other Request Offering page, hide the entire "Create On Behalf Of" picker using CSS, applied via JQuery (or use .hide()). 

The "what page am I on?" logic can be extracted from the code on the page @Conner_Wood linked above.

The JQuery bits can be referenced here: http://api.jquery.com/css/ Additionally, we hide the text box portion of this picker already through the code referenced above. We could possibly just add a .parent() call to grab the label element in addition to just the text box, although I have not tested that.

Thanks,
Nick

Chris_Keander

How about this, is there an easier way to HIDE the "Request on Behalf Of" controls (and associated labels) for a particular ARO if I have the URL?