Thanks Meggie for the reply.
I will check that out to see if that will work.
To elaborate on my process. I am trying to set up a workflow that will handle the addition of new roads into our system and other similar tasks. So the process I envision is to create an LRS job to add the route into the network using versioning. Then before that version is posted an event editor will add the events to the route. But I want to keep the events in a version off of the LRS edit version in case something goes wrong and the event version needs recreated. Once everything is QC'ed then it all can be posted to the default and all required data will show up in default at the same time. We already have a workflow to accommodate event edits and I was trying to nest it within the other one to accomplish this but I wanted to pass a description from the LRS job to the event job.
For instance, we may have received paperwork to add route 1 so a new job is created. An LRS editor will add route 1 in a new version. Once that is done I want to create the event edit job next that will describe what route events apply in a child version off the LRS version. Currently we describe a job using the description field only and use the name just to show if a job is an LRS edit or an Event edit. I want to try to show what is going on and where in the job list which can be confusing.
I hope this makes sense.
Thanks again,
Charles
