| Summary: | Exception when trying to create a Process-Form | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Patrick Steiner <psteiner> | ||||||
| Component: | Form Modeler | Assignee: | Neus Miras <nmirasch> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tomas Livora <tlivora> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 6.0.0 | CC: | lpetrovi, pzapataf | ||||||
| Target Milestone: | ER5 | ||||||||
| Target Release: | 6.0.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: |
Build Name: 13464, Getting Started Guide-6-Beta-1
Build Date: 28-10-2013 13:46:10
Topic ID: 13469-547483 [Latest]
|
|||||||
| Last Closed: | 2014-08-06 20:13:32 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Patrick Steiner
2013-10-29 12:14:34 UTC
I think the best way to respond this issue is explain the current behaviour. When the user access the forms menu, has two situations: - When no task is selectedAttached image:NoTaskSelected.png) * Edit Process Form. Allows access to the process initial form. If it doen't exist, a new empty form is created and the data binding had to be defined manually. * Generate all forms. Generates the process forms (for each user type task an the intial form ) with the data bindings automatically defined. And just in case the form doesn't exist, adds the related fields. - When a task is selectedAttached (image:TaskSelected.png) * Edit Task Form. Allows access to the task form. If it doen't exist, a new empty form is created and the data binding had to be defined manually. * Generate Task Form. Generate the task form with the data bindings automatically defined. In case that the form exists, the databinding are updated but the fields are no added to the existing form to avoid overwrite changes that the user could done manually. Created attachment 821674 [details]
NoTaskSelected.png
Created attachment 821675 [details]
TaskSelected.png
The described behaviour is not the one seen by the V6 Beta Version. Will this be part of the next Beta drop? (In reply to Patrick Steiner from comment #5) > Will this be part of the next Beta drop? Yes. "MODIFIED" status means that the code will make it to the next build. (When that build gets to you, I don't know.) Verified on BPMS 6.0.0.ER5 |