Some tags are stripped from Kaleo Designer's Source tab and are not visible in View

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.0 DXP FP10
• Fix Version/s: 7.0.0 DXP FP24, 7.0.X EE, 7.0.4 CE GA5
• Component/s: Business Productivity, Business Productivity > Kaleo Designer
• Labels:
  • QA-V
  • fw_test_manual
  • liferay-digital-enterprise-70-sp5
  • liferay-fixpack-de-24-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Story Points: 1
• Fix Priority: 3
• Git Pull Request: https://github.com/liferay/liferay-portal-ee/pull/1068

Summary
In Kaleo Designer, after adding a workflow in XML into Source mode, if we Save or change to the View mode, we see that the XML is stripped of its original data. Some clear examples of this are task timers for notifications, scripted recipients for recipients, and resource action for assignments.

The only way to actually get Liferay to take the XML in its original state is to upload it into Workflow Definition. Considering that Liferay permits the uploading of an XML via Workflow Definition with all of the impacted nodes (e.g. task timers, resource action, and scripted recipients) and maintains it in its original state, I think that Liferay should still maintain the original source.

Important Notes

• Regarding task timers, the functionality is available in Liferay Developer Studio's workflow designer interface, but it is not available in DXP's OOTB Kaleo Designer UI.
• Regarding scripted recipients, I created a bug report at LPS-70344 for an issue where in the UI scripted recipients does not exist (instead, we see "scripted assignments" under notifications). But in the Kaleo Workflow DTD, scripted recipients is listed as an actual usable field.

Steps to Reproduce
1. Set up clean DXP + DE-10 fix pack
2. Sign in as [e-mail]
3. Go into Control Panel > Configuration > Kaleo Designer
4. Create a new Workflow
5. Give the new workflow a name
6. Click the Source tab
7. Copy the contents of the attached XML file, and paste it into Source – this contains a scripted-recipient sample.
8. Change to View mode OR Save
9. Go back to the newly created workflow's Source

Actual Result
Certain elements are stripped from the original workflow.

Expected Result
The XML should maintain its original state, just like it would if we directly upload an XML file to Workflow Definition.