Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-2429

Stunner designer strips square brackets characters - HT Notification

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.7.0.GA
    • 7.4.1.GA
    • jBPM Designer

    • RHPAM 7.4.1 on EAP 7.2.

    • CR1
    • Hide

      Before deploying any notifications enabled process, edit the bpmn xml outside of business central to fix any removed brackets in the xml, then externally build the kjar and deploy.

      Show
      Before deploying any notifications enabled process, edit the bpmn xml outside of business central to fix any removed brackets in the xml, then externally build the kjar and deploy.
    • Hide
      1. Start the Business Process designer.
      2. Create a process with a human task.
      3. Open the "Notifications" window in the task.
      4. Assign the "Body" field with the following value: "test[test]"
      5. Save and close the process definition
      6. Open the process definition again
      7. Open the notifications window again

      Actual result

      The body is "testtest" without the square brackets.

      Expected result

      The body is "test[test]" with the square brackets.

      Show
      Start the Business Process designer. Create a process with a human task. Open the "Notifications" window in the task. Assign the "Body" field with the following value: "test [test] " Save and close the process definition Open the process definition again Open the notifications window again Actual result The body is "testtest" without the square brackets. Expected result The body is "test [test] " with the square brackets.
    • 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20)

      In a Human task, if you edit the "notifications" configuration and add some text in the "Body" field, when you save and close the Process Definition and come back again to the notifications window, any sqare bracket disappears from the text.

      When using notifications, mvel expressions can be used to access task variables by using expressions like: ${doc['varName']}; if you come back to the notifications to add a second notification in the future, the brakets will be removed, generating exceptions when the template for the email body is processed.

      This issue is similar to: https://issues.jboss.org/browse/JBPM-4149
      But requires the additional step of re-opening the process diagram.

              handreyrc Handrey Cunha
              rhn-gpte-dtorresf Diego Torres Fuerte
              Lubomir Terifaj Lubomir Terifaj
              Lubomir Terifaj Lubomir Terifaj
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: