Content Item vs Catalog Item

[Sruthi18]

Hi all,

There are 2 questions from my end :

1) Inside "Content Item" I have created the variables set in which we have variable to enter the input . But when I go to portal and check , no variables are shown in the form . Why ? will content item takes only the information variables instead of input taking variables ?

2)I want to populate the URL of the record producer selected based on the questions on the content item/other catalog item and when I click on that link then it should redirect me to that particular record producer(form) and populate value of the same variables which were selected on the content item/other catalog item. 

Please help me on this .

[Jan Prochazka]

Hi @Sruthi18 ,

1) The purpose of the Content Item type of the service catalog items is to provide a specific piece of information to a specific users, at a specific place within catalogs. It is not expected that user needs to provide any inputs to work with the Content Type. Rather, it helps to quickly navigate to a specific information artifact based on defined content type:

• KB Article - it serves as a proxy to a specific KB article to specific users (you can define roles )
• Catalog Content - this will take user to a specific catalog item
• Module - a shortcut to an item of the Application Navigation Menu (Application Module)
• External Content - via this, there can be provided an external information, e.g. a useful URL with an explanation why it is useful and how to use it.

Imagine the Content Item as a bookmark or an encapsulation for a specific information for which you can specify who can access it and where it can be found - you can define in which catalog and category it can be found, who it is available for, etc.

Content Items can be seen as a capability of providing information to users in a structured, controlled, service-catalog way.

A recommendation can be:

If you need the user to interact via entering some variables, use a standard Catalog Item or Record Producer. You can also consider combining a Content Item, serving as a proxy getting the user quickly to the right Catalog Item where inputs will be gathered (variables) and catalog items will pro processed. I guess, there should be some added value for that like configuration of users who can see the Content Item or providing some explanation before starting working with the Catalog Item, otherwise this

Notes:

• The related lists Variable Sets and Variables are as default NOT available on the Content Type record, and this is on purpose.
• Of course, you can add these related lists and define Variable Sets and Variables for your Content Item. It is technically possible, because the table Content Item [sc_cat_item_content] extends the table Catalog Item [sc_cat_item],
• Having the Variable Sets / Variables defined for the Content Item has not effect when being rendered on both portal and back end.

2) You can pass any parameters via URL (in a standard way using param_name=param_value pairs in your URL) and use them in catalog item or record producer, for instance by using onLoad Catalog Client Script.

You only need to:

- parse URL parameters

- set them into your variables using g_form.setValue

This technique is described e.g. here:

https://www.servicenow.com/community/developer-forum/pass-parameter-through-the-url-in-service-porta...

But let me ask why you need to do this?

If I understand your desire correctly, you want:

1. Catalog Item no. 1, you originally wanted it as Content Item, and you want your user to populate some variables there and submit
2. Catalog Item no. 2 which is opened base on the Catalog Item #2 submission, and you want to pass variables from the cat. Item 1 to Cat. Item 2 and then submit it

It seems to me as a kind of double work. Why users cannot go directly to teh Catalog Item no. 2, enter the variable there and submit? They anyway need to enter their variables in the Cat. Item no. 1. What's the added value of teh Catalog Item no. 1 then?

I hope this helps, if so, please mark it as helpful.

Regards,

Jan