SATURDAY, MAY 19, 2012

Posts Tagged ‘Service catalog’

Multiple Checkbox Variables in Service Catalog and Surveys

Tuesday, 09 November, 2010 11:02 Written by Mark Stanger
4 Comments

I just learned something new today about working with checkbox variables/questions in Service-now.com. Even though I’m probably one of the last people to figure this out, I’ll post it here so at least I can find the solution again when I need it!
Service-now allows you to set up variables or questions for use in data collection when working with Service Catalog or in Surveys. One of these variable types is the checkbox variable. The way that these variables works has always bothered me. The problem I’ve always had with them is that the system wants to group them all together and gives them a generic label of ‘Options’ when they are presented on the screen like this…

There are a couple of things I don’t like about this arrangement. First, the ‘Options’ label just looks bad. I’d really like to change that name to something else. Secondly, just because they follow each other in order doesn’t mean that I want to have all of those checkboxes grouped under a single question when presented on the screen. They might be asking completely different things. Well, it only took me 3 years but I’ve got a solution now that requires nothing more than a little bit of care in the arrangement of a few variables on your catalog item or survey. :)

Learn more ...

Adding Fields to the Service Catalog Checkout Screen

Friday, 05 November, 2010 08:07 Written by Mark Stanger
15 Comments

I‘ve written before about some customizations that can be made to the catalog checkout screen in Service-now. The catalog checkout screen gives users one last opportunity to review their order and provide some additional details about the overall request before submitting an order. One common customization request I’ve heard before is to add additional fields to this checkout screen.

This article is an extension of an idea presented on the Service-now wiki that shows one way to approach this problem. The solution described here overcomes some of the problems with the wiki solution and gives a little bit more detail about how the solution works so that it’s easier for you to customize on your own. I’ll also include some formatting examples and show how you can add more than one additional field to the checkout screen.

Learn more ...

GlideDialogWindow – Terms and Conditions Acceptance Page

Monday, 11 October, 2010 07:02 Written by Mark Stanger
16 Comments

L

ast week I had a request come in from a client where they wanted to require users to accept certain terms and conditions before ordering a specific catalog item. I have seen this type of request before, but I don’t think I’ve really seen an elegant solution to it…or anything that could really be called a solution at all :) . Usually you end up with some combination of a wizard, some custom form, and some crazy scripts that make no sense to anyone but the person who created it. Then I realized that I had just written about a solution a week or so ago when I wrote about how to create a UI Page popup using GlideDialogWindow! The specific application of the solution I wrote about was a little bit different, but the basic pieces were identical. By making some basic tweaks to a solution I already knew about, I was able to come up with what I think is a really nice way to require acceptance of some terms before a user orders a catalog item. This same method could also be used on other forms and tables in Service-now.com.

Learn more ...

Wait for Closure of all Tasks in Graphical Workflow

Monday, 16 August, 2010 08:57 Written by Mark Stanger
3 Comments

A

common Graphical Workflow requirement in Service-now is to tell the workflow to wait for some trigger before continuing. The ‘Wait For condition’ activity is available out-of-box and is very simple to configure. Usually when working with Service Requests or Change Requests I am asked how you can set up the workflow to wait for completion of all associated tasks before closing the Request Item or Change Request ticket. This can be easily accomplished by using a script in your ‘Wait For condition’ activity to query for any associated tasks that are still marked as ‘Active’. If the task is marked as ‘Active’ then it hasn’t been closed yet and the workflow should wait for that closure. Here are some sample scripts that I’ve used before to wait for task completion on both Request Items and Change Requests.

Learn more ...

Re-using Choice List Options in Fields and Variables

Wednesday, 14 July, 2010 06:22 Written by Mark Stanger
2 Comments

Choice lists are one of the basic input elements available in Service-now.com. They are very simple to personalize and add or remove any options you need for your application. Something I see fairly often is the need to use the EXACT same choices in different tables that may not be directly related as extended database tables. Another scenario is where you have a choice list defined on a standard field and you want to use that same field and its choices in a service catalog ‘Select box’ variable. Service catalog record producers often have this requirement. In these cases, you may be tempted just to manually re-create the entire list of choice list options for the new field or ‘Select box’ variable. As long as the lists are the same, you can save yourself some setup time (not to mention the ongoing headache of maintaining the same information in 2 places) by making use of the ‘Choice table’ and ‘Choice field’ options.

Learn more ...

Move List Collector Options

Tuesday, 22 June, 2010 09:42 Written by Mark Stanger
12 Comments

H

ere’s a cool catalog client script that I figured out for a client. It allows you to move one or more selected options from one side of a list collector variable slushbucket to another. Using the script is pretty straight forward. Just supply the name of the list collector variable you are working with, and then make sure you provide an array of option IDs to move from one side to another. The option IDs need to be added to the ‘selectedIDs’ array in the middle chunk of code. The code below is set up to move ALL options in the right column of a slushbucket to the left.

Learn more ...

Limiting Number of Selections in a List Collector

Friday, 18 June, 2010 07:47 Written by Mark Stanger
6 Comments

L

ist collector variables are a great way (currently the only way) to allow a user to select multiple options from a referenced table in a single variable on a service catalog item. The list collector variable allows you to choose from one to many (potentially hundreds or more) selections. What if you wanted to limit the number of items that a user could select? This script does exactly that. It restricts the selected items list on a list collector variable to whatever amount you choose. Just use the catalog client script below and set the variables for the maximum number of selections and the name of the variable to apply the restriction to.

Learn more ...

Readonly Variables on a Standard Form

Saturday, 22 May, 2010 16:18 Written by Mark Stanger
45 Comments

A

while ago I helped to answer a forum posting for someone who was looking for a way to present catalog variables to an end-user on a Request Item form but restrict the editing of those variables. At the time, I came up with a solution that worked, but that I really wasn’t happy with. I recently came across another forum posting where the poster wanted to do something similar. The difference for the most recent poster was that the variables were to be shown on an Incident form (which had been generated by a record producer). There were some subtle differences in the way variables were presented on the different forms that made my original script unusable for the incident form. So, I’ve had to revisit this topic to come up with a better solution and I’ve decided to compile all of the different options for making variables read only on a regular form. These solutions can be used in a variety of places, but will most often be applied to the Catalog Item, Catalog Task, Incident, or Change Request tables. Enjoy!

Learn more ...

Copying a Variable Set

Wednesday, 19 May, 2010 07:41 Written by Mark Stanger
2 Comments

T

his script was designed specifically for easily creating a copy of a variable set but it could be easily adapted to create a copy of any other record (and associated records) in Service-now. Rather than use a field-by-field copy technique, this script works more like an ‘insert’ on the records it touches. Because of this, you get an exact copy without having to specify each and every field to copy. If you don’t want an exact copy of a particular field, you can overwrite it in the script. You can implement this copy functionality to copy a variable set by creating a UI action with the following settings…

Learn more ...

Adding a Redirect and Info Message to a Record Producer

Thursday, 25 March, 2010 13:01 Written by Mark Stanger
6 Comments

R

ecord producers in Service-now allow users to create records on any table directly from the Service catalog interface. Typically, record producers are used to allow users to create incident or change request records. When the record is submitted using a record producer, you are redirected directly to the generated record. Oftentimes it is more desirable to redirect users back to the catalog or their homepage and provide them with an information message telling them that their record has been created. Here’s a script that allows you to do that.

Learn more ...

« Older Entries
Newer Entries »

Latest Comments

  • Jim Coyne: I’m not sure exactly what you are looking for, but can you use “window.location” in your...
  • Ian: Might want to check the single quotes around ITIL in the condition line, they gave an error for me until I...
  • Mark Stanger: That’s correct. This returns instance URLs. I don’t have an equivalent currently that...
  • ND: Hi Mark, This is very useful information. I am looking for similar method to find URL of a site created by us. We...