I think you are talking about the forms remaining in the database.
They are not bound to the processes, so you need to delete them by accessing the Derby database.
To do that, go to http://localhost:8080/console, then login with system and manager as login and password, then click on the DB manager link, then select the BPMSDB database.
You should be able to see the table TASKS and delete its content.
No, that is not the case currently, as a form may be used by several different processes.
Does this still apply with 5.1.1? I am currently using 5.1 and there are some issues when deploying processes with user forms: - Sometimes the Designer does not deploy the forms, even if changes where made in the form - It also happens when the process is deployed using a different process-name - I had an instance of a process (process version 10). Then I edited the model (and form), deployed it anew (now version 11). When I looked into the instance of version 10, the new form was displayed and the instance could not be completed. I guess this was due to changes in the form that made the new .xform incompatible to the old .xsd which was probably still used with version 10. There was no problem creating and completing new instances of version 11.
Therefore I'd like to know if a) xforms are now strictly linked to the version of a process they got deployed with b) designer deploys the form every time, not only if it believes and realizes that changes where made
Regards,
Roland
The administrator has disabled public write access.
thanks for the fast answer. Concerning b): With Designer 5.1 it did not help if I checked the "Deploy Forms" option. It is always enabled, even in the preferences. Nevertheless, it only deployed from time to time. Sometimes it helped to "modify" the form (change a letter, change it back, save). So this was fixed with 5.1.1?
Greetings, Roland
The administrator has disabled public write access.