What is the record producer and how can we start the script in record producer?

ram2497
Tera Contributor

‎08-06-2020 07:08 AM

What is the record producer and how can we start the script in record producer?

Please provide any examples.

 

Thanks

Ram

0 Helpfuls
  • 12,109 Views
3 REPLIES 3

Jaspal Singh
Mega Patron
Mega Patron

‎08-06-2020 07:14 AM

Hi Ram,

 

Record producer inserts records directly in Table. It is available from portal but unlike Catalog Item it does not have any Cart functionality nor has a REQ related.

There can be only 1 record producer submitted at a time while Catalog item can have multiple RITMs for 1 REQ.

Simple example for Record producers are Incident, Change, HR cases,etc.

If you need to script you need to look for Service Catalog >> Catalog Definition >> Record producer & then Open any record & look for field called Script (below an example).

find_real_file.png

Preview file
80 KB
Preview file
80 KB

DirkRedeker
Mega Sage

‎08-06-2020 07:45 AM

HI

Record producers appear side-by-side with Catalog Items in Service Portal and you can select them.

When filled in, they build a "simple-as-possible" option to create a new record (in any defined table).

E.g. the "Incident" Record Producer is stripped down to just write down your issue - that's it, and that's easy and simple for the end-user. That is the purpose of Record Producers.

Going to the classic UI, people need to satisfy a lot of fields and need to know how to handle them.

Think about Record Producers, when

> You want to collect data from your end-users

> in a very simple and userfriendly fashion

> If you want to offer this collection of data in your Service Catalot.

If hope this helps to sort out your question.

Let me know if that answers your question and mark my question as correct and helpful.

Enjoy & BR

Dirk

 

Sudhanshu Talw1
Tera Guru

‎08-06-2020 07:52 AM

Hi,

Record Producer=Record + Producer that means it gives an interface to create records in any of the table to which record Producer refers to.

Now why we need it?

As it is not possible to provide access to everyone on the backend table so what we do usually create a record producer which refers to a target table & is avaliable on the service portal which can be accessed by everyone.

The User submits the record producer & a corresponding record is inserted in the backend table.

First of all we have to select a table to which our record producer will create record on.

Then we have to create variables which will be shown on the form. The user fills it & on submit it will be stored on the table.

Now we have to map them:

For mapping simplest you can do keep the variable bckend names same as table name.

u_short_description=>backend table name of the variable

u_short_description=>RP variable backend name.

it will be automatically mapped.

Otherway onSubmit script:

current.short_description=producer.u_short_description;

Catalog UI policy helps you to show/hide options.

Catalog client scripts will help you to set values at backend fetch values from backend & populate them on change event.

For more info:

Reocrd Producer:

https://docs.servicenow.com/bundle/orlando-it-service-management/page/product/service-catalog-manage...

Types of Record Producer variables:

https://docs.servicenow.com/bundle/orlando-it-service-management/page/product/service-catalog-manage...

Catalog Client script:

https://docs.servicenow.com/bundle/orlando-application-development/page/script/client-scripts/concep...

 Hope it helps.

 

Please read it once & let me know if you have any query.

I typed it all the way.

Thanks

Sudhanshu