The first concerns using drag-and-drop of executable processes via WSDL files. If there is a function that does a request-response, where the request is back from the the executable process and the response is to it (as with the second operation of a form request, notifyTaskCompletionRequest) the designer mistakenly assumes that the request is TO the executable process.

The second concerns grouping - when grouping a task into a sub-process, assignments placed in the task (e.g. a literal statement) are deleted.

The third is regarding how forms designer produces .wsdl files and .xsd files - even when creating a simple form with the forms designer, something is causing an error in the mapper in attempting to resolve a reference to ar:createTaskRequest in the dependencies.

A .zipped project is included with examples for all three bugs.

Hubert Delany

Thank you for bringing these to our attention, Hubert. We'll investigate and I'll get back to you early next week.

Thanks,
Pascal.

Hi Hubert,
Answer for your third disquiet:

Forms are designed within Form Editor perspective with available control elements. Once after saving and refreshing a form in designer - .xsd and .wsdl files are automatically generated by the Workflow Visual Connector(which is integrated within Intalio|BPMS Designer) and provides work of art that can be used to integrate the forms with business processes.

Please let me know about ‘ar:’ prefix that you’re talking about is in creating respective <bpel:propertyAlias> for a particular process design?



Thanks,
Shivanand.

Hi Hubert,

I was able to reproduce the concern that grouping a task into Sub-process, we are not able to view the assignments in mapper.
For now we can have the workaround for this issue like,
1. Ungrouping the task again the mapper displays perfectly with previous assignemnts.
2. By undoing the process also we can get the same.
3. While grouping an activity, you can prefer the alternative way of taking the sub-process where you can group more activities.

Any questions on this, please revert back to me.

Thanks
Surendra

Yes I am aware of how the workflow editor is used and that it produces these files. (if not I would not have been able to post the bug at all)

the problem occurs when attempting to make use of the files. an error occurs in the mapper. the ar: prefix is part of the error message and comes from the generated .wsdl file.

Yes I am aware of how the workflow editor is used and that it produces these files. (if not I would not have been able to post the bug at all)

the problem occurs when attempting to make use of the files. an error occurs in the mapper. the ar: prefix is part of the error message and comes from the generated .wsdl file.