<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://juice.altiris.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Helpdesk Solution</title>
 <link>http://juice.altiris.com/helpdesk</link>
 <description>Community for users of Altiris&#039; Helpdesk Solution.</description>
 <language>en</language>
<item>
 <title>Helpdesk Solution - Sorting Worker Queries List</title>
 <link>http://juice.altiris.com/tip/4921/helpdesk-solution-sorting-worker-queries-list</link>
 <description> &lt;div class=&quot;clear-block&quot;&gt;
&lt;div class=&quot;img-shadow&quot;&gt;&lt;a href=&quot;/node/4921&quot;&gt;&lt;img src=&quot;/images/4921.jpg&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;Why on earth would you want to sort your worker query list? For easy reading of course! The following tip will help you sort your list for easier management and viewing. Ready... set... sort!&lt;/p&gt;
&lt;/div&gt;
 &lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/helpdesk&quot; class=&quot;og_links&quot;&gt;Helpdesk Solution&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://juice.altiris.com/tip/4921/helpdesk-solution-sorting-worker-queries-list&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://juice.altiris.com/tip/4921/helpdesk-solution-sorting-worker-queries-list#comments</comments>
 <category domain="http://juice.altiris.com/products/service-desk/helpdesk-solution">Helpdesk Solution</category>
 <category domain="http://juice.altiris.com/topics/customization">Customization</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://juice.altiris.com/crss/node/4921</wfw:commentRss>
 <group domain="http://juice.altiris.com/usergroups/losangeles">Los Angeles User Group</group>
 <group domain="http://juice.altiris.com/helpdesk">Helpdesk Solution</group>
 <pubDate>Mon, 14 Jul 2008 12:12:29 -0500</pubDate>
 <dc:creator>Dominique</dc:creator>
 <guid isPermaLink="false">4921 at http://juice.altiris.com</guid>
</item>
<item>
 <title>Helpdesk Solution - Sorting Quick Incidents List</title>
 <link>http://juice.altiris.com/tip/4920/helpdesk-solution-sorting-quick-incidents-list</link>
 <description> &lt;div class=&quot;clear-block&quot;&gt;
&lt;div class=&quot;img-shadow&quot;&gt;&lt;a href=&quot;/node/4920&quot;&gt;&lt;img src=&quot;/images/4920.jpg&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;You could sort the Worker Quick Incidents List but it will be temporary only as any upgrade, hotfix will overwrite the change. You will need to do it again on the new version, hotfixes, upgrades, repair, etc...&lt;/p&gt;
&lt;/div&gt;
 &lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/helpdesk&quot; class=&quot;og_links&quot;&gt;Helpdesk Solution&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://juice.altiris.com/tip/4920/helpdesk-solution-sorting-quick-incidents-list&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://juice.altiris.com/tip/4920/helpdesk-solution-sorting-quick-incidents-list#comments</comments>
 <category domain="http://juice.altiris.com/products/service-desk/helpdesk-solution">Helpdesk Solution</category>
 <category domain="http://juice.altiris.com/topics/customization">Customization</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://juice.altiris.com/crss/node/4920</wfw:commentRss>
 <group domain="http://juice.altiris.com/helpdesk">Helpdesk Solution</group>
 <pubDate>Mon, 14 Jul 2008 10:25:31 -0500</pubDate>
 <dc:creator>Dominique</dc:creator>
 <guid isPermaLink="false">4920 at http://juice.altiris.com</guid>
</item>
<item>
 <title>Updating Dashboard to Include Other Status Lookup Values</title>
 <link>http://juice.altiris.com/article/4775/updating-dashboard-include-other-status-lookup-values</link>
 <description> &lt;p&gt;
Have you ever wanted your incidents or your queued incidents (from your team) to reflect a count of Open as well as custom status incidents.
&lt;/p&gt;
 &lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/helpdesk&quot; class=&quot;og_links&quot;&gt;Helpdesk Solution&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://juice.altiris.com/article/4775/updating-dashboard-include-other-status-lookup-values&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://juice.altiris.com/article/4775/updating-dashboard-include-other-status-lookup-values#comments</comments>
 <category domain="http://juice.altiris.com/products/service-desk/helpdesk-solution">Helpdesk Solution</category>
 <category domain="http://juice.altiris.com/topics/customization">Customization</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://juice.altiris.com/crss/node/4775</wfw:commentRss>
 <group domain="http://juice.altiris.com/helpdesk">Helpdesk Solution</group>
 <pubDate>Thu, 26 Jun 2008 15:53:54 -0500</pubDate>
 <dc:creator>DeborahAlbrecht</dc:creator>
 <guid isPermaLink="false">4775 at http://juice.altiris.com</guid>
</item>
<item>
 <title>Requiring End Users to Include Comments When Submitting Incidents</title>
 <link>http://juice.altiris.com/tip/4761/requiring-end-users-include-comments-when-submitting-incidents</link>
 <description> &lt;div class=&quot;clear-block&quot;&gt;
&lt;div class=&quot;img-shadow&quot;&gt;&lt;a href=&quot;/node/4761&quot;&gt;&lt;img src=&quot;/images/4761.jpg&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;When using My Helpdesk Console (winuser), sometimes end users try to type their entire issue in the Title field, rather than the Comments field.&lt;/p&gt;
&lt;p&gt;I created a Validation Rule which requires the end user to include a Comment when submitting an incident using My Helpdesk Console (winuser).&lt;/p&gt;
&lt;/div&gt;
 &lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/helpdesk&quot; class=&quot;og_links&quot;&gt;Helpdesk Solution&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://juice.altiris.com/tip/4761/requiring-end-users-include-comments-when-submitting-incidents&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://juice.altiris.com/tip/4761/requiring-end-users-include-comments-when-submitting-incidents#comments</comments>
 <category domain="http://juice.altiris.com/products/service-desk/helpdesk-solution">Helpdesk Solution</category>
 <category domain="http://juice.altiris.com/topics/basics">Basics</category>
 <category domain="http://juice.altiris.com/topics/pcp/sample">Sample</category>
 <category domain="http://juice.altiris.com/topics/user-interface">User Interface</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://juice.altiris.com/crss/node/4761</wfw:commentRss>
 <group domain="http://juice.altiris.com/helpdesk">Helpdesk Solution</group>
 <pubDate>Wed, 25 Jun 2008 13:23:16 -0500</pubDate>
 <dc:creator>mboggs</dc:creator>
 <guid isPermaLink="false">4761 at http://juice.altiris.com</guid>
</item>
<item>
 <title>Incident vs Validation vs Routing Rules</title>
 <link>http://juice.altiris.com/article/4751/incident-vs-validation-vs-routing-rules</link>
 <description> &lt;div class=&quot;clear-block&quot;&gt;
&lt;div class=&quot;img-shadow&quot;&gt;&lt;a href=&quot;/node/4751&quot;&gt;&lt;img src=&quot;/images/4751.jpg&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;At our organization we have been using the Altiris Helpdesk Module for nearly two years. In that time we have made customizations to forms, added custom lookups, and generally taken advantage of the flexibility available in the Helpdesk module. All the while we&#039;ve found the technical documentation to be adequate, but sometimes a quick guide with practical examples on using the various Admin options within the Helpdesk module can be more advantageous.&lt;/p&gt;
&lt;p&gt;Of particular interest have always been the differences between three of the five rule types: Validation, Incident, and Routing. I have often found myself explaining the rule types again to both my manager and other members of the Change Advisory Board.&lt;/p&gt;
&lt;/div&gt;
 &lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/helpdesk&quot; class=&quot;og_links&quot;&gt;Helpdesk Solution&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://juice.altiris.com/article/4751/incident-vs-validation-vs-routing-rules&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://juice.altiris.com/article/4751/incident-vs-validation-vs-routing-rules#comments</comments>
 <category domain="http://juice.altiris.com/products/service-desk/helpdesk-solution">Helpdesk Solution</category>
 <category domain="http://juice.altiris.com/topics/basics">Basics</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://juice.altiris.com/crss/node/4751</wfw:commentRss>
 <group domain="http://juice.altiris.com/helpdesk">Helpdesk Solution</group>
 <pubDate>Tue, 24 Jun 2008 15:00:51 -0500</pubDate>
 <dc:creator>skakid</dc:creator>
 <guid isPermaLink="false">4751 at http://juice.altiris.com</guid>
</item>
<item>
 <title>Increase the Default Attachment Size in Helpdesk</title>
 <link>http://juice.altiris.com/tip/4731/increase-default-attachment-size-helpdesk</link>
 <description> &lt;div class=&quot;clear-block&quot;&gt;
&lt;div class=&quot;img-shadow&quot;&gt;&lt;a href=&quot;/node/4731&quot;&gt;&lt;img src=&quot;/images/4731.jpg&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;I was trying to set up an e-mail template today with an attachment that was nearly 8MB in size. Upon trying to attach the file, I got an error message: &quot;Maximum request length exceeded.&quot;&lt;/p&gt;
&lt;/div&gt;
 &lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/helpdesk&quot; class=&quot;og_links&quot;&gt;Helpdesk Solution&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://juice.altiris.com/tip/4731/increase-default-attachment-size-helpdesk&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://juice.altiris.com/tip/4731/increase-default-attachment-size-helpdesk#comments</comments>
 <category domain="http://juice.altiris.com/products/service-desk/helpdesk-solution">Helpdesk Solution</category>
 <category domain="http://juice.altiris.com/topics/customization">Customization</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://juice.altiris.com/crss/node/4731</wfw:commentRss>
 <group domain="http://juice.altiris.com/helpdesk">Helpdesk Solution</group>
 <pubDate>Mon, 23 Jun 2008 16:53:27 -0500</pubDate>
 <dc:creator>johnquinn</dc:creator>
 <guid isPermaLink="false">4731 at http://juice.altiris.com</guid>
</item>
<item>
 <title>Custom Status for Updated Incidents</title>
 <link>http://juice.altiris.com/article/4422/custom-status-updated-incidents</link>
 <description> &lt;div class=&quot;clear-block&quot;&gt;
&lt;div class=&quot;img-shadow&quot;&gt;&lt;a href=&quot;/node/4422&quot;&gt;&lt;img src=&quot;/images/4422.jpg&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;We found that there were many times that Workers did not realize an incident was updated via e-mail or another Worker and the incident would sit for hours or sometimes days before reviewed again. &lt;/p&gt;
&lt;/div&gt;
 &lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/helpdesk&quot; class=&quot;og_links&quot;&gt;Helpdesk Solution&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://juice.altiris.com/article/4422/custom-status-updated-incidents&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://juice.altiris.com/article/4422/custom-status-updated-incidents#comments</comments>
 <category domain="http://juice.altiris.com/products/service-desk/helpdesk-solution">Helpdesk Solution</category>
 <category domain="http://juice.altiris.com/topics/customization">Customization</category>
 <enclosure url="http://juice.altiris.com/files/Any status to Update.doc" length="43008" type="application/msword" />
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://juice.altiris.com/crss/node/4422</wfw:commentRss>
 <group domain="http://juice.altiris.com/helpdesk">Helpdesk Solution</group>
 <pubDate>Mon, 02 Jun 2008 12:02:16 -0500</pubDate>
 <dc:creator>DeborahAlbrecht</dc:creator>
 <guid isPermaLink="false">4422 at http://juice.altiris.com</guid>
</item>
<item>
 <title>Auto Scheduling Incidents by Priority Assignment</title>
 <link>http://juice.altiris.com/article/4420/auto-scheduling-incidents-priority-assignment</link>
 <description> &lt;p&gt;The good thing about the below incident rules is that they are easy to change for your companies needs. We base our scheduling on priority, however, if you base it off urgency or impact it is not difficult to replace the priority with either of those.&lt;/p&gt;
 &lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/helpdesk&quot; class=&quot;og_links&quot;&gt;Helpdesk Solution&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://juice.altiris.com/article/4420/auto-scheduling-incidents-priority-assignment&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://juice.altiris.com/article/4420/auto-scheduling-incidents-priority-assignment#comments</comments>
 <category domain="http://juice.altiris.com/products/service-desk/helpdesk-solution">Helpdesk Solution</category>
 <category domain="http://juice.altiris.com/topics/customization">Customization</category>
 <enclosure url="http://juice.altiris.com/files/low priority scheduling.txt" length="2647" type="text/plain" />
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://juice.altiris.com/crss/node/4420</wfw:commentRss>
 <group domain="http://juice.altiris.com/helpdesk">Helpdesk Solution</group>
 <pubDate>Mon, 02 Jun 2008 10:17:07 -0500</pubDate>
 <dc:creator>DeborahAlbrecht</dc:creator>
 <guid isPermaLink="false">4420 at http://juice.altiris.com</guid>
</item>
<item>
 <title>Assign Previous Comment to an Incident</title>
 <link>http://juice.altiris.com/article/4423/assign-previous-comment-incident</link>
 <description> &lt;div class=&quot;clear-block&quot;&gt;
&lt;div class=&quot;img-shadow&quot;&gt;&lt;a href=&quot;/node/4423&quot;&gt;&lt;img src=&quot;/images/4423.jpg&quot; alt=&quot;&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;As everybody knows whenever the HelpDesk user edits an incident based on parameters set on tasks, leaving no comments about the change done, Altiris HelpDesk just place a comment with the changes in the history frame of the incident. For example:&lt;/p&gt;
&lt;/div&gt;
 &lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/helpdesk&quot; class=&quot;og_links&quot;&gt;Helpdesk Solution&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://juice.altiris.com/article/4423/assign-previous-comment-incident&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://juice.altiris.com/article/4423/assign-previous-comment-incident#comments</comments>
 <category domain="http://juice.altiris.com/products/service-desk/helpdesk-solution">Helpdesk Solution</category>
 <category domain="http://juice.altiris.com/topics/customization">Customization</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://juice.altiris.com/crss/node/4423</wfw:commentRss>
 <group domain="http://juice.altiris.com/helpdesk">Helpdesk Solution</group>
 <pubDate>Fri, 30 May 2008 15:27:46 -0500</pubDate>
 <dc:creator>joamreynoso</dc:creator>
 <guid isPermaLink="false">4423 at http://juice.altiris.com</guid>
</item>
<item>
 <title>Advanced Report for Helpdesk</title>
 <link>http://juice.altiris.com/article/4417/advanced-report-helpdesk</link>
 <description> &lt;p&gt;
For all of those mangers who want to know…this report will help give an overview of incidents for your different queues.  It will return information that will allow management to review individual users who work within a specific queue (global parameter) over a period of time (global date parameters).  I created this previously to allow management to review incidents completed over a date range for review/bonus purposes.
&lt;/p&gt;
 &lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/helpdesk&quot; class=&quot;og_links&quot;&gt;Helpdesk Solution&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://juice.altiris.com/article/4417/advanced-report-helpdesk&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://juice.altiris.com/article/4417/advanced-report-helpdesk#comments</comments>
 <category domain="http://juice.altiris.com/products/service-desk/helpdesk-solution">Helpdesk Solution</category>
 <category domain="http://juice.altiris.com/topics/reporting">Reporting</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://juice.altiris.com/crss/node/4417</wfw:commentRss>
 <group domain="http://juice.altiris.com/helpdesk">Helpdesk Solution</group>
 <pubDate>Fri, 30 May 2008 14:00:33 -0500</pubDate>
 <dc:creator>DeborahAlbrecht</dc:creator>
 <guid isPermaLink="false">4417 at http://juice.altiris.com</guid>
</item>
</channel>
</rss>
