-
Bug
-
Resolution: Unresolved
-
Neutral
-
None
-
6.2.11
-
None
Steps to reproduce issue with jcrMultiValueField
- edit /workflow-pages/includes/publish.yaml adding 1 more field as below:
emailNotification: label: Email Notification $type: jcrMultiValueField field: $type: linkField datasource: $type: jcrDatasource workspace: users rootPath: /admin nodeNameProperty: email allowedNodeTypes: - mgnl:user - mgnl:folder describeByProperty: email
- file: publish.yaml
- to access the added field, we need a custom CommandAction (and its definition) for example below ones:
- definition: WorkflowCommandActionDefinitionExt.java
- action class: WorkflowCommandActionExt.java
Customization is just print out the field and put it to params object.
.. Logs, screenshots, gifs...
Expected results
- custom field appear and work for user
.. Justify non-trivial expectations with a link to a doc or a relevant discussion.
Actual results
- UI issue happen
- log file: log1.txt
Steps to reproduce issue with link field
- edit /workflow-pages/includes/publish.yaml adding 1 more field as below (replace multiValueField by a single linkField):
emailNotification: label: Email Notification $type: linkField datasource: $type: jcrDatasource workspace: users rootPath: /admin nodeNameProperty: email allowedNodeTypes: - mgnl:user - mgnl:folder describeByProperty: email
Expected results
- custom field appear and work for user
.. Justify non-trivial expectations with a link to a doc or a relevant discussion.
Actual results
- Clicking on "Publish" button run without any error report. However from back end side, we can find issue from log which reported that stored item cannot be serialized. This may cause mis-understand from customers that publication works. Please also fix this error report.
- workflow issue happen due to UI item can not be serialized
- log file: log2.txt
Workaround
- Please advice
Development notes
- N/A
Acceptance criteria