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.

Ability to map only questions that have answers provided to Title

Jason_MeyerJason_Meyer Customer Advanced IT Monkey ✭✭✭

Hypothetically, we have a request offering that has 15 questions.  We are trying to standardize the data we have on this specific request offering.

I would like to 'only' capture the questions that answers were provided.

Currently the best that we are able to do is capture all questions and any answers, or just the answers.

Question #1

Apple, banana, orange

Question#2 if Apple is selected.

Fuji, Granny Smith, Gala are the options.

Question #2 Gala is selected.

So then, in the work item title we would like"Apple - Gala" listed.    Our developers are saying that depending on the number of options in Question #2, there will be a space for each option that isn't selected.

Thoughts on how to get the Title of the ticket to be clean/standardized?

0 votes

Submitted · Last Updated


  • Options
    Jeff_LangJeff_Lang Customer Ninja IT Monkey ✭✭✭✭

    We currently do this for ALL Request offerings, as in update the title depending on what was answered to certain questions within each  offering. The first activity we have on all Service requests is a Cireson PowerShell Activity. We use this to go through all the answers and add additional in info to the Title/Description for the SR and also for all activities in the SR

    EG the one for our Modify User Request, will add the DisplayName and Username on the end of the SR/Activity Titles, unless they ask for more than one user to be modified, then we put in "Multiple Users" instead of the DisplayName/Username.

    Also where we have a single ARO that can be used for multiple types of requests, we may have a dropdown as the first field to select what type of request it is, then this is also put into our title field.

    In general for all our requests we try to add information the same way to the title so things can be easier to find on the grid views.

    NOTE: We disable the Title field on all service requests, so that no one can change them manually. We tend to use the Title field for reporting request types as we can have multiple different requests in a single ARO, so reporting on the template used doesn't really help us.
Sign In or Register to comment.