Make sure you are running the installer from the machine that Warewolf is being installed onto. Installing over the network will cause this problem.

If that is not the case, try manually starting it in Windows Task Manager > Services > Warewolf Server

Still having problems, then please log a bug and attache the following:

• C:\Program Files (x86)\Warewolf\Server\wareWolf-Server.log
• C:\Program Files (x86)\Warewolf\Server\Warewolf Server.InstallLog 
• C:\%localappdata%\Warewolf\Warewolf_Install.log
  

Hi Paul

Idea 1. Im not sure if this is what you are looking for: The for Each executes from 1 to x. Each iteration replaces * in the tool/service being executed with that number. When that number = a particular number, you want to take a new and different action?

Idea 2. We will be introducing a sequence tool that allows you to group a number of actions together and you could put that inside the For Each. Would that solve your problem?

Hi Paul

Excellent question. 

You are correct, performance would be a dog. The best design to handle this is to create your validation workflow to accept recordsets Inputs and return recordset Outputs (rather than scalars and then putting it inside a for each).

In this way you can map the entire recordset with next to no overhead into the validation workflow, do one db call and then handle the iteration between records inside that workflow.

Hi Paul

Warewolf is a Flow based language. Think about a typical coded function being a workflow and each service or tool in that workflow being a line or action.

So, if you are after the time, we need to execute a tool to get the time into a variable and then use it.

There are a few ways to get the current system time:
1. The calculate tool has all the MS Excel funcitons so you can just tupe: now() and then put that result into a variable.
2. The Assign tool can act like a Calculate tool if you start the assign value with an = so you can just type: =now()
3. The Gather System Information Tool has a Date & Time option
4. Date and Time Tool: If you leave the Input blank and the Input format blank, by default the tool will return the current system time in the system format.

I hope I have answered your question.

Thanks Paul. The WWF designer limits the space that can be used there. We felt it was better to put in what you can rather than nothing at all as a default.

We also added the ability for you to put the text there that you want (check the bottom of the decision) so you can overide the default.

We are rehosting WWF. Unfortunatley we cant get access to everything at a design level.

We will have another crack at the altering the design surface automaticaly.

We agree. There is a quite a bit that needs to be done to the variable list.

Thanks for the idea.

Nice idea Paul. We will give it some thought.

Currently this is not possible. Once a workflow has been called, it will run its course given the inputs provided.
Once the User interaction (Webpages) piece is done, you will be able to interact with the workflow if its built into the process.