Home› Service Manager Console App Feature Requests
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.

Add "Hidden" response type to Advanced Request Offering

Nick_FlintNick_Flint Customer Advanced IT Monkey ✭✭✭
edited May 2017 in Service Manager Console App Feature Requests
When adding a user prompt to an Advanced Request Offering, add an option for a "hidden" field. Use the "User Prompts or Information" as the field name and then require that a value be entered in the "Configure" section.

This could then be combined with with the options in the "Layout" selection to set user input based on the responses in other prompts.

Example:
Prompt 1-> Is this a new or replacement printer?
Prompt 2 -> Installation of Network Drop required (hidden response type) (Only displayed if Prompt 1 is 'new)

If the user selects 'new' for prompt 1, the user input in the request will include "Installation of Network Drop Required" but the user never needs to see that on the request.

8
Up Down
8 votes

Submitted · Last Updated

Comments

  • Brian_WiestBrian_Wiest Customer Super IT Monkey ✭✭✭✭✭
    The ARO has this option in the Page layout section. 


    Here you can see that if they mark "Will this modify server OS licensing as True (checkbox control)
    The other two questions will appear on the offering. 
  • Nick_FlintNick_Flint Customer Advanced IT Monkey ✭✭✭
    That part is there, but the secondary field prompts are displayed in screen because they are text inputs (e.g. <input type="text" ....).

    What I'm asking for is the ability to create an input of type hidden (e.g. <input type="hidden" ..
     
    See https://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_input_type_hidden


  • Stephane_BouillonStephane_Bouillon Customer Advanced IT Monkey ✭✭✭

    A hidden field that has a default value that can be used to steer downstream processing would be very helpful. The hidden prompt/values should be part of the <UserInput/> that is in the request. See also Bug in Advanced Request Offering ? — Cireson Community

  • Konstantin_Slavin-BoKonstantin_Slavin-Bo Customer Ninja IT Monkey ✭✭✭✭

    You can do this with ROToolbox by using @AddClass{"class": "hidden"}. This will hide the prompt. Adding a default value can be done the same way, but you'll need to add the js code yourself.

    If there's a need for this, I could add a @AddHiddenDefaultPrompt to the toolkit? It would add some value to the prompt and hide it by default.

  • Konstantin_Slavin-BoKonstantin_Slavin-Bo Customer Ninja IT Monkey ✭✭✭✭

    @john_doyle just added this:

    Added a new @hidden tag, which hides the prompt which follows it. Combine this with a List prompt with a default value to create a hidden input value on the form.

    (commit)

    You can download the updated version of ROToolbox from his git: https://github.com/doyle-johnpaul/ROToolbox

Sign In or Register to comment.