How do I add a widget to a catalog variable

[timhorn]

We have several complex forms that include multiple UI Pages.   We just upgraded to Istanbul and we're looking to convert

our CMS portal to the Service Portal.   I've seen lots of posts about how UI Pages and UI Macros will have to be replaced with

variables that contain widgets.   Many of those posts show what the variable form should look like, with the "widget" field

showing up in the "default value" section.   No matter what I do, I can't get the widget field to show up.   I modified the form

layout to include it.   I tried using every type of variable.   It just won't show up.   Is there some trick to this?   I have to be

missing something obvious.

[ChrisBurks · Accepted solution]

The steps to adding a widget to a catalog item are as follows:

1. Create Service Portal widget

2. Navigate to desired Catalog Item to configure

3. Under the Variables section click New

4. Widgets can only be added to variable type "Macro". Therefore select "Macro" as the type

5. Click on the "Default Value" tab

6. In the Widget field select the widget created in step one

7. Select the Question tab

8. Fill in the required fields such as Question and Name.

9. Submit.

Now the widget should appear within the catalog item when rendered via Service Portal.

Here's a quick video to demonstrate:

addwidget

[timhorn]

I could have sworn I tried using a macro variable before, but that must have been before I added the field to the form.   This works great.   Thanks.

[mshetty794]

hi Chris,

I am able to add widgets into service catalog.I need to read those value in workflow when catalog is submitted. Please   help me

[ChrisBurks]

Hi Mithun,

I believe the easiest (and standard) thing to do is if you have information to be captured from a macro variable type whether it be an actual UI macro, UI page or widget is to create correlating hidden variables. When the data is entered in the macro then transfer that data to the hidden variable(s). Then from the workflow script you would be able to capture the data with regular current.variable.<variable_name>.