Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Wizard Setps in Catalog Builder

Dennis17
Tera Guru

Hi colleagues,

I have a couple of questions regarding Catalog Builder:
1. Is it possible to have new Wizard Steps applies just in specific Catalog Item Templates? I would like to avoid to have a new Wizard Step for all templates.

2. Once I have the Wizard Step with some variables (Single-Line Text), how can I store the information that the creator of catalog item filled to create the catalog item?

 

Thanks in advance!

Best regards.

Denis

1 ACCEPTED SOLUTION

Hi @Dennis17 

 

I think yes, you can use or access the variable but I never tried this. Give a try in PDI and share feedback with us.

*************************************************************************************************************
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

5 REPLIES 5

Akos Szilagyi
Tera Expert

The answer to the second question of yours, is to make a variable that you add to the any of the sections (reference variable to the sys_user table), and you can set the field Default Value to: javascript:gs.getUserID(). When the builder user edits the cat item in Catalog Builder, his user account will automatically populate in there. You can also set the field by a ui policy to read only, so he cannot change it. (Depending on your use case you might want to limit which resources can / should edit that field. Keep in mind, in the background view a lot of 'other' users can change field. - I implemented a logic for that field by ACL.) It all depends on your process.