Workflow Soluiton

 View Only

Setting the Root URL and Respond Link 

Mar 05, 2008 12:58 PM

When publishing a Workflow project that uses the Approval or Respond function it always points to ‘Local Host’ and not back to our workflow server. Additionally, if you would like to change the Respond Link text to suit your workflow needs we have added that to Part 2 of this post.

Part 1:

Changing Root URL server:

To make this change from the default – http://localhost – you need to log onto your workflow server and follow these steps.
  1. Click Start – All Programs – Altiris – Workflow Designer – Tools – WorkflowDesigner Server Extensions Configurator. You should see the following screen.
  2. On the above screen - click on the ellipse next to the ‘Deployment Info:’ option.
  3. The following screen will be displayed:
  4. Change value next to the ‘Root URL:’ to equal your workflow server using either IP address or name.
  5. Don’t change the ‘Localhost’ in the ‘IISRoot Path:’ field.
  6. When finished click ‘OK’ and then ‘OK’ again. Then click ‘Yes’ when asked to save your changes.
  7. You will then be asked to restart the ‘Server Extensions’ – select ‘Yes’. This will take a few second to update.
  8. Once this has completed your workflow which is using a Approval or Respond link will point to the workflow server and not the local host.

Part 2:

Changing Respond Link Name:

By default the respond link name is set to ‘Respond’ but you might want to change this to meet you workflow project needs. To change this feature inside your workflow from the default, follow the steps below.
  1. Within your workflow when using the ‘Dialog Workflow Component’ under the ‘Interaction Setup’ tab under the option ‘Respond Link Name’.
  2. The default setting is ‘Respond’ but you can place any word which reflects what your workflow requires and it will change the ‘Respond Link’.
  3. Below are 2 emails that show the default and a change ‘Respond Link.’ Default ‘Respond’: Changed setting to ‘Approval Please’:

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

Jul 09, 2009 08:12 PM

I actually got it to work, but I had to modify the "properties.config" file from IIS.  Did I miss a step somewhere?

Jul 09, 2009 08:01 PM

That seems like it should work, but it doesn't.  Any other ideas?

Related Entries and Links

No Related Resource entered.