Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Workflow Solution
Showing posts in English
LNew | 14 Oct 2008 | 0 comments

Note: While this article makes reference to "smart tasks", these are not intended to be the Help Desk 6.5 smart tasks. Rather, they are actions that can be performed in conjunction with your workflow process. So too, these actions may not complete the task or process, but will operate as a supplement.

When working tasks such as incidents, you may want to utilize a smart task as a means to access an additional resource such as Google or perhaps even that marvelous website known as Juice. The following instructions walk you through creating a smart task in a Workflow Solution process.

(This is another helpful hint post for my fellow novices...)

  1. Open your Workflow process and double-click a dialog workflow that is associated with an actionable task.
    ...
erikw | 01 Oct 2008 | 0 comments

I found a very nice movie about Workflow that shows what it can do.

http://vids.myspace.com/index.cfm?fuseaction=vids....

Symantec's Altiris Workflow Solution v 6.0 is a series of products that were acquired from LogicBase called TLogic. Used together, they can help you automate virtually any IT process or workflow and imbed business logic into the processes too. The product can be useful for something that requires repetitive human interaction, such as designing an automated system for gambler's comp packages at a casino to keeping track of cleaned rooms at a hospital. Almost any type of process or Workflow can be automated with Workflow Solution.

Regards
ErikW

LNew | 25 Sep 2008 | 0 comments

The following is a tip on saving a Send Email component as your default or as part of your Workflow Library for future use. Whenever you add a new component of that type, the component will be a mirror-image of what you previously saved, in both the text and the settings. This will serve in a manner similar to the Outlook function of creating and saving an email template.

(This may be a trick known to all of you Workflow experts out there, but I figured I'd post it for my fellow novices!)

  1. Double-click the Send Email component that you want to modify in order to edit the configuration.
  2. On the Email Contents tab, the From Address can be changed to a constant value or something referenced within the process or your Project Properties.
  3. Set up the To, CC, and BCC address...
nac | 15 Sep 2008 | 6 comments

Many times we have to customize the installation of vendor MSI, by selecting complete, typical or customize installation of the package. This will install particular features when selected. If we add another feature, it may not install, and we cannot see the files and registries added by the component present in this feature.

Using Custom Action:

Check for the custom action which is installing selected features and edit to add the feature.

Edit the custom Acton to add New Feature

LNew | 11 Sep 2008 | 0 comments

I ran into this problem when creating a workflow for a standard time off type of request - there wasn't a way to force the 2nd date (in this case, the end date) to key off of the 1st, or start, date and therefore prevent the user from selecting something like 9/27/08 to 9/25/08 for his/her time off.

A coworker of mine helped me come up with a way of comparing the dates inside of the form itself, rather than looping out of the form. This way, the workflow would not progress if the end date was not greater than the start date and we can utilize custom validation to handle both the model and the error message. Consequently, the user would be required to fix the date issue right then and there.

There may be an easier/quicker way to handle this, but here's what we came up with:

In this example scenario, we will use what may be a...

neil_rogers | 07 Aug 2008 | 0 comments

In Workflow, the term "Collection" is a term that does not refer to traditional Altiris Collections, unless it has the Altiris icon. If it is a blue file box, then it can be used for array items.

Collections are how array handling is done. If you have a list of computers in an array, and need to add a ticket for each one, then use the component: "For each element in Collection."

It has two output paths: Next Element and Finished. The Next Element is similar to a while or for loop. Just loop it through the rest of the components and back to itself. Inside of that process it can have things like matches or equals rules, Commands, Create or Edit Tickets and then the data path goes back to the For Each element in Collection until it runs out of elements!

There are other handy ways to handle items in arrays or add items to arrays...

Rob Moore | 07 Aug 2008 | 1 comment

We've been using the Workflow Solution for several months now, and while the integration with Altiris Helpdesk is pretty tight, it is missing some key features that just drive me nuts. One of those is the inability to dynamically assign a worker to an incident.

To solve this issue, I've created a simple SQL integration component that queries the Worker table for a list of all the active workers and queues, and their associated Worker ID number. This list can then be put in to a drop down list component. Once a user selects a user name, the associated variable also returns the worker ID. This can then be used in the Associations tab of the Create incident component.

Andy Tous | 23 Jul 2008 | 1 comment

When using the Service Desk component "Create Ticket", notice the "Comment" field under the "Ticket Details" tab only shows information using a single line.

This will cause your comments to show on a single line when viewing from the Altiris Helpdesk side.

You should be able to fix this from the Workflow Designer by simply opening the "Create Ticket" component, "Ticket Details" tab. Click to edit the "Comments" and click on the on the "Source" button then "OK".

You will notice the [CR] squares will appear next to each line.

NOTE: If you edit the comments using the "Design" mode, you must click on "Source" and "OK", otherwise everything will display on a single line again.

scottwed | 03 Jun 2008 | 1 comment

In some situations, your workflow process may need to be split into two or more separate streams. For example, you might need to have three people approve a request before continuing. If you did them sequentially, it would take a lot longer to obtain all the necessary approvals.

Updated: Correction, the parallel tasks are not discarded upon the first path reaching an end point. However, the practice of merging is still extremely important to avoid accidental firing of downstream tasks and data dependencies that may not exist. To implement merging, execute the following steps.

Add the Workflow.Advanced.dll to your project by clicking on the "Import Components" button in the left pane of the Designer interface. Select the highlighted item and click Add.

...
Shadrocks | 08 May 2008 | 0 comments

If you have been disappointed with the lack of how-to documentation about using Workflow solution, here is a free e-learning class, provided by Altiris, to get you started.

I installed the solution for a look and quickly hit a wall when I attempted to build my first workflow. This 26-minute course looks as though it will be a big help.

Cheers!

http://learn.altiris.com/eCommerce/index.cfm?FuseA...