We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.

We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.

For more information around feature requests in the Cireson Community click here.

Option on CI prompts to Not Preload results

Its confusing to end users to have a text filter and then a second filter. Would be much easier if there was a prompt config in the ARO that tells it to NOT preload the results and force user filter to search.
4 votes

Submitted · Last Updated

Comments

  • Michael_BaldryMichael_Baldry Customer Adept IT Monkey ✭✭
    This is by far the most common feedback we've received on the CI prompts. People get very confused about how to use them, since it isn't immediately apparent that you need to select an item from the box after filtering. Having this option in place (and possibly automatically selecting the only remaining item if they filter it down to 1) or changing it to a combobox (like the "Create Request on behalf of" box), would be far more intuitive for single-select lists. 
  • Greg_WojtkunGreg_Wojtkun Premier Partner IT Monkey ✭
    The issue here is for form prompts that query a large list of CMDB objects. 1. it hurts performance a bit, 2. takes a few seconds to load, and 3. Takes up real estate on the page. 4. In order to be able to select from 5000 plus objects, as an example, you need to ensure all of those pre load so you need to change the setting of "Grid View Cap" to 5000+, etc. 

    So - the smart thing here is just to add an option under prompt config in the ARO of  a simple check box that says "Do not pre load results" and thus this will force the user to use the filter box that is already there rather than the current workaround of having to set up a filter question before it and then use a token. 
Sign In or Register to comment.