Record Producer to create change request OR change task?

[emyrold]

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?

[emyrold]

Hi All, thank you all for your suggestions.   What we've decided to do is actually prototype both the record producer and wizard approach to front-ending the creation for change requests/tasks.

We will then evaluate base on the following:

1) usability testing

2) Ongoing development support in terms of building new items and updates to existing.   ***Can a non-developer, but techie person build new front-ends.

3. Length of time it takes to author a new (medium sized) front-end in hours?

Thanks everyone,

-Erik