Service Catalog Form Builder
Filed under:
Helpdesk Solution
3rd Party Products
Submitted by janjira on Tue, 2007-09-04 14:48.
Want to make populate your Service Catalog with lots of different forms for different types of requests? Don't want to program them all separately? Don't want to spend hours debugging and maintaining lots of different templates?
There is a simple solution at: http://thaweekan.com/?page_id=3
- No programming is required
- No changes required to the Helpdesk or the database
- Create and modify custom forms in minutes using only the New Task command in the Helpdesk Console.
- Use radio buttons, dropdown lists, check boxes and text
- Forms are compatible with all the Rules including Validation Rules.
- Forms can be attached to incidents
Do check this out.
(35 votes)
Great tool!
This is a great tool! I purchased a copy this week. For those who haven't seen it, it's definitely worth researching at janjira's website.
Great Tool!
Very handy little tool. It integrates seemlessly into the Helpdesk solution. I purchased it this week and have already built 3 forms. It does work with SP4 of Helpdesk, but having SP5 with the Service Catalog is the way to go.
How to??
I won't be upgrading to SP5 until this weekend but want to play with it before then. How do you use it with SP4?
Getting an error upon executing
I have the product installed on SP5. I followed the steps in the documentation to create a form and that went fine.
I go to the Winuser console and I can see the link both by making it a common entry or by putting it into a category.
However, when I click on the link to access the form, I get the following error:
User control source files must have a .ascx file extension.
Details
Exception - System.Web.HttpException: User control source files must have a .ascx file extension.
at System.Web.UI.UserControlParser.CheckUserControlFileExtension(String fileName)
at System.Web.UI.UserControlParser.GetCompiledUserControlType(String virtualPath, String inputFile, HttpContext context)
at System.Web.UI.TemplateControl.LoadControl(String virtualPath)
at Altiris.AppWeaver.TemplateModule.OnLoad(EventArgs e)
Any thoughts????
Question about this..
how are these effected by upgrades? Are the customizations preserved?
thanks
your question
No, they are not preserved. You have to copy them just as you do with other Helpdesk customizations.
Its a great tool, though...well worth it.
DC
Reply
Dee, are you responding to someone else. I didn't ask about Help Desk. ha..ha..ha..
How long have you used Altiris? Are you using the Wise Packaging solution? If so, call me.
Vince B.
Moxie Interactive
Help Desk Manager
(678) 916 - 4490 office
(678) 478 - 6303 cell
Actually, as the
Actually, as the customizations are all made using the custom.config files as recommended by Altiris and no changes are made required to any of the built-in templates, you should be able to upgrade Helpdesk without affecting this template.
Outstanding tool. It makes
Outstanding tool. It makes building forms so much easier. With the latest version, you are able to build your forms from xml instead of having to plug controls directly into the task, making big forms so much easier. I have worked with the Workflow Management tool & this actually produces better forms thus far! Definitely made my company buy it!
Excellent piece of code
This is a great add on for HD 6 versions. Very clever and very useful.. Have created a modified version that enables you to create forms that are not just Service Catalgue forms but can be used more generically (like providing a justification and backout plan form for change requests....
Excellent product
I have to agree that this is a very excellent add-on to the HelpDesk. I have already created a few forms and have deployed them in my HelpDesk.
I really like how the output comes out nice and clean in the comments section.
Of course one thing I would really like to see in the form building is some kind of date control where instead of actually typing in the date, the user could be presented a pop-up that would fill the date in so that the input is consistent for all users.