Record Producer to create change request OR change task?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2015 04:35 PM
I have a requirement where we are trying to present a single front-end to users and then based on a question/answer we will either generate a new Change Request and new change tasks. Or we will only need to create a new change task where the parent is an existing Change Request.
I was thinking I was going to be able to accomplish this with record producers but am not seeing how it can be done since the record producer item needs to be defined against a predetermined table.
I saw a thread on the community where Mark Stanger suggest a Wizzard but this was back in 2008....
I started poking around Wizards and they seem very convoluted compared to record producers.
I have already built about 30 Catalog Items with all the correct variables, client scripts, ui policies; all tested and client is happy with. I was hoping I could just mimic what I did on the Catalog side in a record producer so I can have a consistent front end experience for their users and then be able to address their change management requirements.
Any ideas / suggestions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2015 05:03 PM
As a suggestion, If not going with wizards, I would go with a catalog item that has a dedicated workflow. Where we can use activities like if, and run scripts to create task based records based on the condition. Or you can do the same with a custom module where submission of form gets us to new task based record. Validation can be done via a B-Rule.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2015 12:15 AM
Hi Emyrold,
You could use "current.setAbortAction(true)" in your "script" for record producer to force the producer not to create a new record.
So, ideally you can point it to any table (for simplicity though, point it to change_request or change_task). Now, you can use the GlideRecord functionality in scripts to dynamically insert new records in both the Change Request and Change Tasks or only in Change Tasks.
This is not a straight forward functionality, but could be helpful for your current requirements.
Thanks,
Mandar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2015 06:36 AM
Thank you Mandar...!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2015 12:19 AM
Hi Emyrold,
In my suggestion, Wizard is the best option.