Request Offering needs more generic fields

Carol_Lee

Hi, we have a lot of questions to ask on a SR form.  Can we add more generic Text fields in the request offering to map the questions?

Also, it is an advance request offering.  What is "Multiple mapping"?  What is it used for?  Maybe it can help me. I need to add 5 sets of the 2 questions on SharePoint URL and access type, and we are running out of generic fields to map.

Please advise.

Adam_Dzyacky

Hey there Carol. So two things at play here:

1. The Service Request class itself
2. Cireson Advance Request Offering

If you extend the Service Request class you can add more generic fields, boolean values, etc. I highly recommend doing this through the SCSM Authoring Tool. This will allow you to map your many inputs to many different fields

or

Using the Cireson Advanced Request offering you can map many inputs to a single field. Check this out - https://community.cireson.com/discussion/comment/9891#Comment_9891

Brian_Wiest

To add onto Adam's statement. In our environment we use both.

One we use the ARO to assist with the Multi Mapping of prompts and adding text into the description. If you look at this tread you can see some screenshots of how others laid out their description fields (and note you can do the same to Any data field)

https://community.cireson.com/discussion/comment/6826#Comment_6826

Now before the ARO was available we did extend the IR and SR classes with 20 generic string fields, and with the ARO we still use them. How they come into play is we will typically map questions responses into the description but also to one of the extension fields. Then we use these fields for reporting.

Example Hardware support call.

In the RO we ask questions on top of the error message or issue description to "normalize" the issue type.

Error Type =

Error Code

Firmware

Hardware malfunction (Ie will not power on, broken LCD)

Jamming

Spilled Toner.

We then map that answer into the description field and one of our custom extension fields.

This now allows us to run a report of all the printer hardware calls and place into a simple pivot table of the error types. Easily allow management to see percentages of fleet issues without keyword searching.

HTH

Adam_Dzyacky

Hey there Carol. So two things at play here:

1. The Service Request class itself
2. Cireson Advance Request Offering

If you extend the Service Request class you can add more generic fields, boolean values, etc. I highly recommend doing this through the SCSM Authoring Tool. This will allow you to map your many inputs to many different fields

or

Using the Cireson Advanced Request offering you can map many inputs to a single field. Check this out - https://community.cireson.com/discussion/comment/9891#Comment_9891

Brian_Wiest

To add onto Adam's statement. In our environment we use both.

One we use the ARO to assist with the Multi Mapping of prompts and adding text into the description. If you look at this tread you can see some screenshots of how others laid out their description fields (and note you can do the same to Any data field)

https://community.cireson.com/discussion/comment/6826#Comment_6826

Now before the ARO was available we did extend the IR and SR classes with 20 generic string fields, and with the ARO we still use them. How they come into play is we will typically map questions responses into the description but also to one of the extension fields. Then we use these fields for reporting.

Example Hardware support call.

In the RO we ask questions on top of the error message or issue description to "normalize" the issue type.

Error Type =

Error Code

Firmware

Hardware malfunction (Ie will not power on, broken LCD)

Jamming

Spilled Toner.

We then map that answer into the description field and one of our custom extension fields.

This now allows us to run a report of all the printer hardware calls and place into a simple pivot table of the error types. Easily allow management to see percentages of fleet issues without keyword searching.

HTH

Carol_Lee

Thank you @Adam_Dzyacky @Brian_Wiest It helps.  One thing I have also learned that I have to put the static questions in the Layout page too in order for them to show up.  Thanks.