The CreatorCon Call for Content is officially open! Get started here.

Show Variable Editor for Incidents Created from Backend

Abhishek Kathe
Mega Guru

Incidents created via Record Producers shows the Variable Editor section. However, incidents created directly from the backend do not.

How can I make the Variable Editor section visible (with empty variables) for backend-created incidents?

2 ACCEPTED SOLUTIONS

Hi @Abhishek Kathe 

I understand that this is a client requirement, but as a ServiceNow expert, it's important to educate the user on what is good and what isn’t, and what can bring real value. If something is not easily possible and creates technical debt, let’s avoid introducing it

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

View solution in original post

Ankur Bawiskar
Tera Patron
Tera Patron

@Abhishek Kathe 

that's OOTB behavior and you can't show it on form if INC is not generated via record producer

Logically if the incident got created from record producer the Variable Editor formatter is shown automatically with the variable information caller submitted from portal.

Why would you require this to be seen when INC is not created from record producer?

-> you can try to play with the UI macro "com_glideapp_questionset_default_question_editor" OR create a fresh macro by making a copy of that and then try to manipulate it

-> that OOTB macro calls another macro

AnkurBawiskar_1-1760007151103.png

 

AnkurBawiskar_0-1760007138798.png

 

💡 If my response helped, please mark it as correct ✔️ and close the thread 🔒 — this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

8 REPLIES 8

Hi @Abhishek Kathe 

I understand that this is a client requirement, but as a ServiceNow expert, it's important to educate the user on what is good and what isn’t, and what can bring real value. If something is not easily possible and creates technical debt, let’s avoid introducing it

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

Hi @Dr Atul G- LNG  thanks for the deep dive

Ankur Bawiskar
Tera Patron
Tera Patron

@Abhishek Kathe 

that's OOTB behavior and you can't show it on form if INC is not generated via record producer

Logically if the incident got created from record producer the Variable Editor formatter is shown automatically with the variable information caller submitted from portal.

Why would you require this to be seen when INC is not created from record producer?

-> you can try to play with the UI macro "com_glideapp_questionset_default_question_editor" OR create a fresh macro by making a copy of that and then try to manipulate it

-> that OOTB macro calls another macro

AnkurBawiskar_1-1760007151103.png

 

AnkurBawiskar_0-1760007138798.png

 

💡 If my response helped, please mark it as correct ✔️ and close the thread 🔒 — this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Hello @Ankur Bawiskar thanks for the response

I will check the feasibility accordingly