catalog creation

[iwsservicen]

I am creating a catalog form and would like to know whether there is a standard approach to implement filters using a single script.

Scenario 1:
If a ServiceNow form contains 4 input fields, but the final output requires 5 or 6 fields—where the additional fields are not part of the form but do exist in a related ServiceNow table through a mapped relationship—should this be considered a simple or complex requirement? It seems like a common use case.

Example:
Form fields: User, Host Pool, VDI Name, Status
Required output: The above 4 fields plus Location and Device Type, which already exist in the underlying table but are not displayed on the form.

[Brad Bowman]

I'm not quite tracking on the related/underlying table, but generally speaking one can create a Catalog Item which creates a service request - REQ & RITM records, or the Catalog Item is a Record Producer which creates a record on a given table.  It sounds like you're talking about a Record Producer, so I'll start with that. 

You create a variable for each data point that you want to collect on the initial request form.  In a Record Producer, these variables can be mapped to the field on the related table. If they're not mapped, they are displayed as additional information on the resulting record in the Variables section of the form.  So if your Record Producer contains 4 variables that are mapped to fields, the table which the record is created on will contain many more fields, but only 4 get populated with the request, then the form for the table determines which other fields from the table are displayed.

If your Catalog Item is not a Record Producer you would need to define all (6 in this case) variables that you want to exist.  Since you only want 4 to display on the initial request form, you would create a Catalog UI Policy or Catalog Client Script to hide the other two variables on the request form only.