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

Stunner - Relax constraint on signal name

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.7.0.GA
    • 7.6.0.GA
    • jBPM Designer
    • Release Notes
    • Hide
      A milestone can be triggered by signal. It is triggered when its name is the same as the signal name.
      If this is the use case, the issue restrict a user to set the milestone name only to the allowed values of signal name. The empty spaces are not allowed what can be undesirable.
      Show
      A milestone can be triggered by signal. It is triggered when its name is the same as the signal name. If this is the use case, the issue restrict a user to set the milestone name only to the allowed values of signal name. The empty spaces are not allowed what can be undesirable.
    • Hide
      1. Open stunner bpmn project
      2. add Signal node into the canvas
      3. in properties set Signal to 'Milestone 2: Order shipped'

      Actual result

      Validation fails on checking signal name value

      Expected result

      Validation does not fail on checking signal name value

      Show
      Open stunner bpmn project add Signal node into the canvas in properties set Signal to 'Milestone 2: Order shipped' Actual result Validation fails on checking signal name value Expected result Validation does not fail on checking signal name value
    • 1

    Description

      Once migrating the it-orders case mgmt example from the legacy designer to the new one, an issue appeared: It seems there is a validation error on the process, the example is using two signals with symbol ":" and spaces.

      This warning can be ignored and the process can still be saved, but you can't recreate it from scratch as the editor will prevent you from creating a new signal with colon or spaces in it. The fact that we use the node name as the signal name in case management (to trigger that node) makes this a more severe issue as you're more likely to use spaces and possibly other special characters in node names. The underlying XML does not have any restrictions on signal name (xsd:string), and the engine also accepts any string afaik, so as long as the parser can support it as an attribute value we can support more characters.
      <bpmn2:signal id="_825e5b59-8a03-369d-b7ed-e5e3824400c9" name="Milestone 2: Order shipped"/>

      Attachments

        Issue Links

          Activity

            People

              dtikhomi@redhat.com Dmitrii Tikhomirov
              romartin@redhat.com Roger Martinez
              Lubomir Terifaj Lubomir Terifaj
              Lubomir Terifaj Lubomir Terifaj
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: