My collegue Mark Everard has a nice series on putting a custom workflow together so maybe this can help:
I have already looked at it along with a huge collection of links about workflow from another page (Dont remember the link right now and its on another computer).
All the workflows I have found know at programming time that after event X comes event Y or Z and we therefor need to run them with this group of parameters. All that can be solved programming time.
What I need is a way to go from a known workflow to a unknown workflow (programming time) This workflow need to have a set of start parameters (with the loadstartparameters method). The action to load is known runtime but not programming time and its not an option to include a method to include each and every action in every workflow.
Have been looking some more and it seems a posible way to solve this is by storing the information in a temponary place and let every action look there for informations to load when they start. But it gives alot of problems with how to make sure the informations are the right one if there is more than one workflow running at a time.
What you can do in EPiServer is that you can configure a workflow to be automatically started whenever another workflow of a specified definition completes.
The workflow runtime in EPiServer will in that case scan through all public properties on the workflow type for both the completing and starting types and all properties that match both in name and type will be read from the completing instance and written to the starting instance.
So if for example both the completing and starting workflow types have a public property Email of type string then the value of Email will be "passed" from the completing instance to the starting instance.
Great thanks :)