Did you take a look at the "Base URL To Project" property when you publish the workflow? Make sure that it is referring to the server that you are publishing to, either by name or IP. Also ensure that you can reach that server from the workstation that you are testing on.

Another place to look is under Start-->Programs-->Altiris-->Workflow Designer-->Tools-->Server Extension Configurator. If you click on the elipse next to Deployment Info make sure that the values are properly filled in.

Good luck.

Hi there.

Are you sending the email to the CEO from within the dialog workflow Interaction Setup dialog model? Or are you sending it from within a Start Process/Event Configuration? I find that using the latter works best for carrying over the ResponsePageURL.

I'm not sure what your familiarity with workflow is (not to say I am an expert by any means), so please forgive me if this is general knowledge:

1. Double-click your dialog workflow component to edit it.
2. Click the Event Configuration tab and click the ellipse next to Start Process - Empty Configuration.
3. Drop a Send Email component on the model that appears and drag your ResponsePageUrl into the HTML editor portion.

What should happen is that the email will fire off first and the link within it will point to the form tied to the Interaction Setup of your dialog workflow.

Hope this helps.

LNew

Thanks for the responses! I have tried both ways but am going with the Start Process/Event Configuration method. I have done the steps listed above and all works great...until I actually click on the "respond" link. That's when I get the page can not be displayed message. I am thinking I must not have something setup correctly.

I am wanting to create an approve/deny form that displays when the link is clicked but as of now, I am getting nothing.

Thanks,
Jamie

I'm also no expert, but... I am a crazed monkey.

You need to do two things:
1. Use ResponsePageLink, not ResponsePageURL. The link version is an automatic variable that is formatted with anchor tags and the whole 9 yards. Using ResponsePageUrl you're relying on the client's Mail Client (sorry) to convert that to a link. Plus it's ugly.

2. the responsepageurl and responsepagelink are actually dynamically determined values. They are based on *where* the workflow is running. If you have published the workflow to your server, then the ResponsePageUrl and ResponsePageLink will use the "Root URL" as defined in the ServerExtensionsConfigurator. (I know, awesome name)

To set this up you have to:
a. open server extensions configurator (described above)
b. click the ellipsis by 'deployment server settings'
c. set RootUrl to be a valid base url, accessible to your executives, for this workflow server. http://wf.myco.com/ or http://192.168.33.22 whatever makes sense in your enviornment.
d. close all the dialogs, save, restart server extensions.
.... now the magic bit....

e. Republish your workflow project. As soon as you've done that it will start sending emails with a sensible url.

hope that helps. PM me if it doesn't.

What's the url in the email? Is it sensible? does it have a localhost in there? Does it refer to the server?