This content has been marked as final. Show 6 replies
As far as I know, the XPath expressions should be evaluated at run time as you expected, rather than using them as literal values. I don't have access to my server now so I can't run a test. I'll get back when I can.
I've performed some other tests. I was able to build a workflow that throws an event and another one that receives the event as a start point. I was able to get that one to pass variable data with the event. Unfortunately, this does not satisfy my original use case.
Here's my scenario:
- Workflow 1 executes a number of steps.
- Workflow 1 sends an email notification with a form attached. The form will contain a hidden field with the Process ID for workflow 1.
- Workflow 1 sits and waits for custom event to be received.
- A user receives the email notification, fills out the form, and submits it to mail it back in to LiveCycle.
- Workflow 2 is set up with an email endpoint. Workflow 2 receives the form submitted via email, extracts the data from the form, and throws the custom event. The Process ID that was originally stored in the form is populated on the event data.
- Workflow 1 receives the event thrown by Workflow 2. The event filter will make sure it is only processing an event where the process ID values match.
- Workflow 1 completes execution.
I have so far been unsuccessful passing event data in this manner. I'm trying to use this approach to handle offline workflow assignments to users that aren't in LDAP.
Has anyone worked with events? It appears that only Adobe has done so. Any help would be greatly appreciated.
make sure process variables are of "input" type or else they will not be populated!
The variables can't be defined as "input" type. My process is waiting to catch the event right in the middle of the process, not as a start point.
I've done something very similar but I've used a user step instead of an event in my Workflow 1. I associated a temporary user for the step to wait for the response. In my Workflow 2, I used the "Complete Task" operation to complete the task.
That might be an alternative if you run into too much trouble with events.
I've worked with events in ES. I gound that using the Service Pack 1a had problems and was really showing some immaturaty.
At the time I was using filter expressions on the event receiver to match against values of a variable inside the process instance (not too different from what you are trying to do.
Since then I ran the same test several times for ES Service pack 1b and it works.
What version of ES are you running?