Licensing-Inquiry Regarding Ticket Creation from Custom Portal

[xingrui]

Hi everyone.

I would like to inquire whether it is permissible for a requestor to create records directly on the task's inheritance table through a widget in a custom portal. Specifically, I am concerned about potential licensing violations associated with this functionality.

I have researched this topic online and within community resources but have been unable to locate relevant documentation.

If anyone has insights or information on this matter, I would greatly appreciate your assistance.

Best Regards

[Mark Manders]

Why?

You have to guide the users somewhere to fill in the data. Why not guide them to a simple record producer instead of weird scripting to get the same? You are creating a widget to create a record. You are in fact creating a record producer, but completely outside of OOB ServiceNow, while everything is in there. Even if you get it to work, you run the risk of breaking it on each and every upgrade you do. You are talking about OOB and are shocked that if you are changing anything, it is no longer OOB, but you are creating something completely unsupported to get something to work which is already OOB available.

[xingrui]

Hi @Mark Manders,

I am aware that I should be utilizing the OOB solutions.

But I require a user interface calendar that can display records created by users and allow for some one-step actions on the portal. Unfortunately, I have not found any OOB widget that can achieve this functionality. I came across a document that suggests integrating a third-party solution, specifically FullCalendar.

How to add a Calendar widget for Service Portal - Support and Troubleshooting (servicenow.com)

[Mark Manders]

It's only getting more confusing. You want to show records in a calendar. That is in no possible way connected to using a record producer or not. The record producer creates the record. How you show them on the portal is a different requirement.

[xingrui]

Sorry for lack of clarity in my previous message.

My current Project Requirement is to enable users to visualize the timeline and events in the user interface calendar and to allow them to input values for fields directly by clicking on the relevant timeline event within the calendar. Records will be generated based on these submitted values.

Based on your reply, it seems that I should separate the event display in the calendar from the record producer. It's the right thing to do right?

[Mark Manders]

This is absolutely completely different from your initial request. You are now talking about updating records instead of creating them. This will probably impact your licensing, because you are making them record handlers instead of just creators.