Hi Mikael,
Actually, looking at the previous two, these were different issues ...
I think Chris Wong had not set the parameter 'runtime', so his problem was then fixed - I can only assume so, because he did not come back :-(.
Hariharan Palanisamy had a problem where he was trying to access the event info from the job definition, not the chain. If you put a WaitEvent on the chain, then I think you need to reference the
wait event in the parameter mapping (chain editor), not as default value on the job definition/process definition that the chain calls. That is what I think was going on, here ... not sure, though.
What is your precise problem, you might want to open a new thread on the subject ... it is better than hijacking threads like this, we have had two different (but similar) issues here already ;-).
What would help is a few screenshots and the full error stack ... make a small test case where you reproduce the problem, try to keep it as simple as possible, and use non-identifiable values (no company/customer details).
Best regards,
HP
Message was edited by: h. Carpenter "It works for me, but then again, I am lucky!"