Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
Master
-
7.2.x, 7.1.x, 7.0.x
-
Committed
-
1
-
4
Description
When we add an XML document to the "Source" from Kaleo Designer and then go to the "View" mode, some content can be added to specific nodes, resulting in a different workflow definition than the one first given.
Steps to reproduce
- Go to Kaleo Designer.
- Go to the "Source (Kaleo XML)" mode.
- Replace the content of the editor with the content from single-approver-3.xml
.
- Go back to the "View" mode.
- Go back to the "Source (Kaleo XML)" mode.
- Compare the resulting XML document to the original one we got from single-approver-3.xml
.
Expected results
- The content we got from the editor would be identical to the one from single-approver-3.xml. At most, some formatting changes would be applied.
Actual results
- Where we had
<notification> <name>Creator Modification Notification</name> <template> <![CDATA[]]> </template> <template-language>freemarker</template-language> <notification-type>email</notification-type> <notification-type>user-notification</notification-type> <execution-type>onAssignment</execution-type> </notification>
now we have this:
<name>Creator Modification Notification</name> <template> <![CDATA[]]> </template> <template-language>freemarker</template-language> <notification-type>user-notification</notification-type> <recipients> <user/> </recipients> <execution-type>onAssignment</execution-type> </notification>
In this new result, the lines below were added:
<recipients> <user/> </recipients>
The same happened to the node at line 85.
Attachments
Issue Links
- causes
-
LPS-79288 workflow with timers fail to publish
- Closed
-
LPS-83804 Changing the Recipient Type of Review Notification fails
- Closed
-
LPS-88053 Recipient Type in Tasks' Notifications of Kaleo Workflow is not consistent with its definition
- Closed
- duplicates
-
LPS-74524 Kaleo Designer adds spurious configurations to XML document when changing to "View" mode
- Closed