what is the purpose of a traditional form.

[jieLian123]

when design a portal, I found that service catalog is always used.

And always we have to create the catalog form through record producer

as it shows a better user interface.

In that way, what is the purpose of the traditional form in a develop process.

I am a little confused.

[Sandeep Rajput]

@jieLian123 Could you please explain what do you mean by traditional form here? If it is about the catalog item/record producer view on the backend/platform view then it is present on the platform to allow request product and services for the backend users (an ITIL user who needs to request something on behalf of other user). For such users, it is convenient to quickly request something without leaving the platform view and going to the portal.

Service Portal interface is mostly used by the end users as it offers consumer grade experience whereas the platform interface is for the support teams and the backend users. 

[jieLian123]

>Could you please explain what do you mean by traditional form here?

I was trying to say the form desighed by e.g. Form Design.

And I don't quite understand the diffrence between a Form Design designed form

and a service catalog record producer.

in Service Portal , a service catalog record producer is used other than a Form Design designed form.

is that right ?

[Harish Bainsla]

hi 

Service Catalog and Record Producers:

1. User-Friendly Interface:

   • Service Catalogs, especially when created using record producers, offer a user-friendly and structured way for end-users to request services or items. Record producers guide users through a step-by-step process, making it easier for them to understand and complete the request.

2. Automation and Process Orchestration:

   • Record producers in the Service Catalog are often associated with workflows. This allows for automation of backend processes once a user submits a request. Workflows can include approvals, notifications, and fulfillment tasks.

3. Standardized Service Requests:

   • The Service Catalog helps standardize and centralize service requests. Users can access a catalog of predefined services and products, reducing the chances of errors or inconsistencies in requests.

4. Visibility and Reporting:

   • Service Catalogs provide visibility into the types and volume of service requests. This data can be valuable for reporting and analysis to improve service delivery.

Traditional Forms:

1. Custom Application Development:

   • In some cases, you may need to develop custom applications or modules within ServiceNow that don't fit the standard service request model. For such scenarios, you would create traditional forms to capture and manage data.

2. Complex Data Entry:

   • If your application requires complex data entry or involves a variety of related records, traditional forms can be more suitable. They offer more flexibility in terms of layout and customization compared to the structured approach of record producers.

3. Non-Service Requests:

   • Not all data capture needs are service requests. Traditional forms are applicable when dealing with other types of records, such as incidents, problems, changes, or custom business processes.

4. Legacy or External System Integration:

   • Traditional forms might be necessary when integrating with legacy systems or external databases that don't align with the Service Catalog model.

5. Workflow Customization:

   • For highly customized workflows or processes that don't follow the standard service request flow, traditional forms offer more control over the design and behavior of the user interface.

When to Choose:

• Service Requests: If your application involves users requesting services or items following a predefined process, and you want to take advantage of automation and standardization, use Service Catalogs and record producers.

• Custom Processes or Data Management: If your application involves complex data management, non-service request processes, or integration with external systems, traditional forms may be more appropriate.

[jieLian123]

thank you very much.

I need a little more help.

Is it a good way to use Traditional Forms in service portal, or I should use Service Catalog and Record Producers instead.

I tried to use icon link and set the url with <tablename.do> to access a Traditional Forms in service portal,

but the back button[<] on the upper left of the form dosen't work properly .