Views and Record producers - Do they go together?

[Lisa Butcher]

I have created two views.  When one view is used to enter detailed information, I need to update other fields/values not on that view upon submit so the second view will display the information info. For example, our end user fills out view form and presses submit, fulfiller then takes case and works case in a different view, which contains additional fields.  I need to auto populate these additional fields accordingly (the caller does not fill out these additional fields so I need to auto populate.  For example: description, caller, Type etc.

Is this called a record producer?  I could not figure out how to create a record producer and tie it to the view I already have configured.  Am I looking in the wrong area?

Assistance/guidance on what to search for is appreciated.  I'm really hoping I can use the views and auto populate fields.

[Pradeep Sharma]

Hello Lisa,

You can create an On Load Client Script on the target table to auto-populate the fields as per your req. There is a view field on Client script which you can use to execute the script based on the view.

Please refer OOTB Record producer "Create Incident" for reference where an end user can input the information and when they submit the form it has defaulted to ESS view whereas "Default view" is shown to fulfiller user. Please let me know if you have any questions.

Thanks,

Pradeep Sharma

[SanjivMeher]

Record Producers are used as an interface for end user to create Incident/Change/Case since they dont have direct access to these tables.

Record producer doesnt have any view. It is just a form with variables to take users input and map it to the corresponding table.

Views are only on tables. So an incident can have a different view for End users and different for ITIL. Because End user doesnt need to see all the fields. So we create a separate view for them. and a different one for ITIL.

You can find record producers under Service Catalog and are different from views