Home› Service Manager Portal 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.
Options

Call a request offering from a link or script that prepopulates some fields

L_SchickL_Schick Member Advanced IT Monkey ✭✭✭
in Service Manager Portal Feature Requests

We would like to allow a request offering to be called from a link or script that populates some fields for users.

One example of this would be we have a request offering to ask for exceptions to our internet filtering. Currently our users open the request and have to manually type or paste the URL, Unfortunately mistypes happen frequently. It would be nice if we could link to the Request Offering and have the URL field get pre filled out based on the website its coming from

We also have a folder/file access request offering this would benefit from as well.

43
Up Down
43 votes

Submitted · Last Updated

Comments

  • Options
    PIERRE-LOUIS_DURRISPIERRE-LOUIS_DURRIS Customer Advanced IT Monkey ✭✭✭
    That would be a great improvement, with this solution, we could add link in our application to the incident form with application, urgency, impact, title pre-populated.
  • Options
    Adrian_PaechAdrian_Paech Customer Advanced IT Monkey ✭✭✭

    Yes Please. This would be massive for us!

    Adrian

  • Options
    Geoff_RossGeoff_Ross Cireson Consultant O.G.
    This would be awesome for a 'resubmit request' task that would allow, once a service request or change has been rejected, to return to the offering form, with all the prompts complete as per the original request allowing the user to change something in order to get the request approved second time around.
  • Options
    Adam_DzyackyAdam_Dzyacky Product Owner Contributor Monkey ✭✭✭✭✭
    +1 for the very reason described by @L_Schick.
  • Options
    seth_coussensseth_coussens Member Ninja IT Monkey ✭✭✭✭
    PIERRE-LOUIS_DURRIS said:
    That would be a great improvement, with this solution, we could add link in our application to the incident form with application, urgency, impact, title pre-populated.
    @PIERRE-LOUIS_DURRIS you could do a variation of what you are talking about here by having multiple RO templates and then using a link that refers to the appropriate RO via GUID/URL. This would fill in the urgency and impact based on the template.

    Obviously not as flexible as what is described in this request offering but it would allow for some of what you are asking for. 

    Just a thought.
  • Options
    Nick_FlintNick_Flint Customer Advanced IT Monkey ✭✭✭
    I see this as a step toward being able to "Daisy Chain" request offerings; for example, in an Employee On Boarding scenario, rather than retype the employees name and general information for every request offering, have one link to the next with the values already entered pre-filled.
  • Options
    Bruno_SerafimBruno_Serafim Customer IT Monkey ✭
    edited April 2017
    Nick_Flint said:
    I see this as a step toward being able to "Daisy Chain" request offerings; for example, in an Employee On Boarding scenario, rather than retype the employees name and general information for every request offering, have one link to the next with the values already entered pre-filled.

     It would be very useful for us too.
  • Options
    Chris_Chekaluk1Chris_Chekaluk1 Customer Advanced IT Monkey ✭✭✭

    This is great, but are we talking about a new portal API here, and/or passing parameters via the RO/ARO's url (similar to how parameters can be passed to Dashboard widgets)?

  • Options
    Peter_MiklianPeter_Miklian Customer Advanced IT Monkey ✭✭✭
    edited March 2021

    Another use cases:

    1. Request Offering placed (RO) in multiple Service Offerings (SO) has unique URL combining SOID,ROID. Example: Shared Mailbox RO is in both Access and E-Mail SOs. Opening it from the E-mail SO URL would prepopulate first field: I want to: Create new shared mailbox while URL containing Access SOID would choose I want to: Grant permissions to shared mailbox.
      1. Those unique URLs are reason to show the same RO multiple times in search, too. If I remember correctly new portal version should display only 1 occurrence in the (global?) search. I'm not sure when this got/will get to production.
    2. Similar to @Nick_Flint example: we have SR "New employee hardware and software" which should submit line manager (LM) of the new employee. We could notify the LM after "New employee" SR (create AD, e-mail, accounts, ...) is completed and those 2 SRs could be linked together (Related WI).
Sign In or Register to comment.