Forward Mark Catalog For Free

Catalog UI policies control the behavior of catalog item forms when presented to your users. Catalog UI policies can be applied to a catalog item or a variable set. UI policies are useful when applied to service catalog items.

Catalog client scripts run when a user orders an item from the service catalog. Catalog client scripts can also run when variables or variable sets for a catalog item are displayed when a user requests that item. For a variable to be accessible using a catalog client script, it must have a variable name.

A catalog item can be a good or service. If something can be ordered by itself, it is a catalog item. If something only makes sense as part of a greater whole, it is part of an item, rather than an item in and of itself. For example, a new Dell server is a catalog item, as is a new Executive Desk.

Service catalog variables capture and pass on information about choices a customer makes when ordering a catalog item. Variables help define the structure of a catalog item form that is displayed to the customer.

Simply put: If you're offering end-users the ability to request a service where you need to control approvals and fulfillment, you will use a catalog item. If you're just looking to gather information or need to gather open-ended feedback/suggestions from your users, you will use a record producer.

A Catalog Item is a form used to submit information, a request, or to create a task. Catalog Items contain questions that gather information from users to create a record in a table. Use App Engine Studio (AES) to easily create customized Catalog Items that users can access in Service Portal and on mobile devices.

The basic Service Catalog item types include: Record producers: giving alternative ways of adding information such as Incidents via the service catalog. Order guides: to group multiple catalog items in one request. Content Items: catalog items which provide information instead of goods or services.