Login to participate
Endpoint Management & Virtualization DownloadsRSS

Create an Incident using a Command Line Tool

rbross's picture

This is a command line tool that will allow you to programmatically create an incident in Helpdesk (HD). It uses the HD SOA supplied Web service to do its work.

This is a .NET based tool, so before using it be sure that the .NET framework is installed on your machine.

The tool can either take command line parameters (just type "CreateWorkitem" to see them) or by using the command

"CreateWorkitem -f:[xml file path]"

The tool will read the XML file that contains the parameters. A sample XML file is included for reference.

License: AJSL
By clicking the download link below, you agree to the terms and conditions in the Altiris Juice Software License
Support: User-contributed tools on the Juice are not supported by Altiris Technical Support. If you have questions about a tool, please communicate directly with the author by visiting their profile page and clicking the 'contact' tab.
bgreen's picture

This is a great idea

This is a great idea - I can see it being very useful for creating Altiris HD tickets from 3rd party monitoring software, among other things.

Is there a specific version of the .NET Framework that this requires, or will it work on all of them?

xmoreland's picture

Yes!

I was just asked to give an example of how we can do this.

Sorta hard since we don't have it running yet!

Very useful!

hoagland's picture

Add to existing Work Item?

rbross, This looks like a great idea. I'm hoping you can point me in the right direction to do something similar. I'd like to programatically add a comment to an existing incident. Any advice greatly appreciated!

Jim

ribak's picture

See the Helpdesk Integration Guide (extract attached)

3.2.3 Edit Incident command

The Edit Incident command behaves similarly to the New Incident command except that it operates on an existing incident and requires an incident id. Unlike the New Incident command, it is not necessary to specify a workitem_title along with commit=yes as a good title already exists.

Note: it might not be advisable to specify any input data other than workitem_comment unless you’re using commit=yes or unless your invoking page explains what is happening. This is because the user has no good way to know what fields may have changed over those originally in the incident (comment is fair game since it is blanked by the edit process anyway and the invoking solution may want to suggest appropriate text for the incident it is helping the user create).

URL:
?cmd=editItem&id=[&=[&=][&commit=yes]]
where:
= the incident number or guid to be edited.
= one of the fields from the Appendix A – Incident view fields.
= a value appropriate for the specified field.

jorm76's picture

Very Good Tool...

This is a great idea, I can see it being very useful for creating Altiris HD tickets from 3rd party software.

I can your add more concepts? "Category", "Priority", "Imapct", "Urgency" and so on into XML

IT Consultant
Altiris Certified Engineer

johnquinn's picture

Don't think you can do that.

I know this is an old thread, but I just got my hands on this becasue I was looking for a solution to automatically generate incidents for regularly scheduled tasks I want to perform.

I tried adding simple tag to accomodate things like Category and Priority but they did not work.

Now like in my case with what I plan to do with it, the title will be consistent, so the solution to that would be to use Incident Rules to set the Category and such.

It would be great if it could be added right into the xml up front, but at least the Incident Rules could make up the slack.

twerickson's picture

?????

Can you assign it to a certain cue through this command line? I'm having a little problem with the syntax...

David Ekstrom's picture

Using InfoPath

I'm looking to use Microsoft Infopath for some workflow forms and having trouble with the necessary commands to pass to information from Infopath to create and Altiris incident. Anyone have experience with doing this? I know there is a way for Infopath to look at the Altiris incident database and pull fields from it, but how do I then write those fields back to create a new incident?