Default "receptionType" values result in validation error in Kaleo Designer 7.0.x-private

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.0.0 DXP FP58, 7.0.0 DXP SP9, 7.0.X, 7.1.X, 7.2.X, Master
• Component/s: Business Productivity > Kaleo Designer
• Labels:
  • QA-AUTOMATION
  • fw_test_js
  • liferay-dxp-70-sp9
  • liferay-fixpack-de-58-7010
• Branch Version/s:
  7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Priority Level: Low
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal-ee/pull/18903

As part of fixing LPS-74909, we always add a receptionType attribute to <recipients> tags. However, it is causing breakage in the 7.0.x-private version of Kaleo Designer, because this version still validates the workflow definition schema. By the schema, receptionType should have one of the valid values (to, cc, bcc). Our fix sets no value to the attribute, which violates the schema.

So, if we backport LPS-74909, and try to publish a workflow with <recipients>, the receptionType attribute will be added by the "View" mode. On publishing, the validation will fail, with an exception such as this one:

com.liferay.portal.kernel.xml.DocumentException:
 Error on line 21 of document  :
 cvc-enumeration-valid: Value '' is not facet-valid with respect to enumeration '[bcc, cc, to]'.
 It must be a value from the enumeration.
 Nested exception: cvc-enumeration-valid:
 Value '' is not facet-valid with respect to enumeration '[bcc, cc, to]'.
 It must be a value from the enumeration.

Also, if the schema version is from 6.2, which does not even have receptionType, the publication will fail with an exception like this:

com.liferay.portal.kernel.xml.DocumentException:
 Error on line 21 of document  :
 cvc-complex-type.3.2.2: Attribute 'receptionType' is not allowed to appear in element 'recipients'.
 Nested exception: cvc-complex-type.3.2.2:
 Attribute 'receptionType' is not allowed to appear in element 'recipients'.

These errors are preventing the backporting so should be addressed. receptionType should not be automatically added to workflows if it was not present in the XML document before.