Some fields inside notifications in a node do not auto-save

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: Master
• Fix Version/s: 7.4.3.17 CE GA17, Master
• Component/s: Workflow
• Labels:
  • 7.4-known-issue-until-remove-flag
  • Kaleo-Migration-Bugs
  • frontend
• Fix Priority: 4
• Epic Link: Migration Debts
• Git Pull Request: https://github.com/liferay-zulu/liferay-portal/pull/40

Description:
The Notification Types field into notifications does not show the value chosen by the user

Steps to Reproduce:

1. Go to Open Menu > Workflow > Process Builder
2. Add a new process
3. Click on start or end node
4. Click on notifications
5. Fill the required fields
6. Go to (1)Template Language/(2)Notification Types/(3)Execution types field and choose a new value

(1) Expected Result:
– Given –

• The user clicks on Template language field

– When--

• The user choose a new value (example : Text)
• Click on the arrow back of the node on the sidebar
• Enter at the notification created and see the Template language field

– Then –
expected: The value should be saved

Actual Result:

The value is not saved

Possible workaround : If the user change the template field before click on the arrow back, it will save the value wanted

(2) Expected Result:
– Given –

• The user clicks on Notification types field

– When--

• The user choose a new value (example : Email)
• Click on the arrow back of the node on the sidebar
• Enter at the notification created and see the Notification types field

– Then –
expected: The value should be saved

Actual Result:

The value is not saved

Possible workaround : If the user click on save, get back to process builder page and enter in the definition again, the value it will be saved

(3) Expected Result:
– Given –

• The user clicks on Execution types field

– When--

• The user choose a new value (example : On Exit)
• Click on the arrow back of the node on the sidebar
• Enter at the notification created and see the Execution types field

– Then –
expected: The value should be saved

Actual Result:

The value is not saved

Possible workaround : If the user change one of the required field before click on the arrow back and after change the option wanted, it will be saved

Verified on master : a0f6b39c55139d75e6f57f3cccda1b9893804537