Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-1627

Cockpit/Renderer fails to show badges if activity ids contain dots in BPMN

      Reproduce steps:
      get a diagram and build in ids with dots

      Problem:
      there are no process instance badges ff an element's id contains a dot

      Expected behavior:
      badges will be shown properly

      Hints (optional):
      see little example project

        This is the controller panel for Smart Panels app

            [CAM-1627] Cockpit/Renderer fails to show badges if activity ids contain dots in BPMN

            Stefan created issue -
            Robert Gimbel made changes -
            Rank New: Ranked higher
            Stefan made changes -
            Link New: This issue is related to SUPPORT-766 [ SUPPORT-766 ]
            Bernd Ruecker made changes -
            Summary Original: Cockpit fails to show badges if BPMN ids contain dots New: Cockpit/Renderer fails to show badges if activity ids contain dots in BPMN

            Christian added a comment -

            See http://www.schemacentral.com/sc/xsd/t-xsd_ID.html for valid pattern for xml IDs.
            Quote: "... must start with a letter or underscore, and can only contain letters, digits, underscores, hyphens, and periods."

            Christian added a comment - See http://www.schemacentral.com/sc/xsd/t-xsd_ID.html for valid pattern for xml IDs. Quote: "... must start with a letter or underscore, and can only contain letters, digits, underscores, hyphens, and periods."

            Hi Christian.

            Thanks for the feedback! That means using dots in activity is not valid BPMN 2.0 XML? That would be indeed interessting.
            I thought the engine validates the XML with the Schema - and this should fail in this case. Or did we disable the schema validation per default?

            Thanks & cheers
            Bernd

            Bernd Ruecker added a comment - Hi Christian. Thanks for the feedback! That means using dots in activity is not valid BPMN 2.0 XML? That would be indeed interessting. I thought the engine validates the XML with the Schema - and this should fail in this case. Or did we disable the schema validation per default? Thanks & cheers Bernd

            Stefan added a comment -

            Periods are dots

            Stefan added a comment - Periods are dots
            Roman Smirnov made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Roman Smirnov made changes -
            Assignee New: Roman Smirnov [ smirnov ]
            Roman Smirnov made changes -
            Assignee Original: Roman Smirnov [ smirnov ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            Remaining Estimate New: 0 minutes [ 0 ]
            Original Estimate New: 0 minutes [ 0 ]

              michael.schoettes Michael Schoettes
              stefan.hentschel Stefan
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: