-
Bug
-
Resolution: Done
-
Critical
-
None
-
7.27.0.Final
-
NEW
-
NEW
-
Workaround Exists
-
-
-
2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18)
Once deleting a whole Space, the existing BPMN re-usable activity nodes cannot be longer configured properly, because trying to open the forms panel results on an exception. which makes it impossible to set the right form field values for the activity.
There is no known way to work around this (yet), so this is a BLOCKER issue, because:
- The field dropdown becomes NOT usable, even after ignoring the error popup - no way to change the value or set any new one
- Even creating new processes, when showing the forms for any re-usable activity it still fails
- It does not seem a client cache issue, so even after logout the issue persists
- By looking at the internal file system, the process or actual spaces have no reference to the deleted assets, so no way to fix the issue in any file descriptor
So even trying the above work arounds, the user is NOT ABLE TO USE PROPERLY re-usable activities in processes, see:
- is blocked by
-
JBPM-8875 Stunner - Re-usable subprocess doesn't show options for Called Element properties (DROOLS-3727 merge)
- Resolved
- is related to
-
JBPM-8905 Stunner - An error messages after deleting space and opening properties panel for reusable sub-process
- Open
- relates to
-
RHPAM-2432 Stunner - it is possible to break process by setting incorrect called element
- Closed