Details

    • Type: Task Task
    • Status: Done Done (View Workflow)
    • Priority: Normal Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: FN
    • Labels:
      None Labels
    • Customer:
      Mobinets

      Description

      We identified an issue with the current Flowable process definitions on cloud env related to empty <errorEventDefinition/> elements in BPMN end events.
      Problem:

      In some deployed process definitions, end events had <errorEventDefinition/> without an errorRef.

      Flowable requires an error code for error end events.

      When these processes are executed, the following exception occurs:

      org.flowable.common.engine.api.FlowableIllegalArgumentException: Error Code must not be null
      at org.flowable.engine.delegate.BpmnError.setErrorCode(BpmnError.java:53)
      at org.flowable.engine.delegate.BpmnError.<init>(BpmnError.java:48)
      at org.flowable.engine.impl.bpmn.behavior.ErrorEndEventActivityBehavior.execute(ErrorEndEventActivityBehavior.java:48)

      Root Cause:

      Flowable engine requires all <errorEventDefinition/> elements to have a valid errorRef.

      Some older BPMN files were deployed without a global error or without specifying errorRef on end events.

        Activity

        Ayed Bada logged work - 23/Jan/26 12:00 AM
        • Time Spent:
          4 hours
           

          -create and test new soap api patchErrorEventDefinitions
          -intercept all process upload to add error refs

        Ayed Bada logged work - 26/Jan/26 12:00 AM
        • Time Spent:
          7 hours
           

          -create and test new soap api patchErrorEventDefinitions
          -intercept all process upload to add error refs

        Ayed Bada logged work - 27/Jan/26 12:00 AM - edited
        • Time Spent:
          3 hours
           

          test and apply script on cloud env

        Ayed Bada made changes -
        Field Original Value New Value
        Gantt Options Milestone (set to milestone: having a due date but zero effort)
        Planned Start 2026-01-27 24:00 (milestone: set planned start date to due date)
        Planned End 2026-01-27 24:00 (milestone: set planned end date to due date)
        Ayed Bada made changes -
        Assignee Hassan Abdine [ habdine ] Ayed Bada [ abada ]
        Ayed Bada made changes -
        Summary atch Flowable BPMN End Events to Fix Missing Error Codes Patch Flowable BPMN End Events to Fix Missing Error Codes
        Ayed Bada made changes -
        Description We identified an issue with the current Flowable process definitions in the system related to empty <errorEventDefinition/> elements in BPMN end events.
        Problem:

        In some deployed process definitions, end events had <errorEventDefinition/> without an errorRef.

        Flowable requires an error code for error end events.

        When these processes are executed, the following exception occurs:

        org.flowable.common.engine.api.FlowableIllegalArgumentException: Error Code must not be null
            at org.flowable.engine.delegate.BpmnError.setErrorCode(BpmnError.java:53)
            at org.flowable.engine.delegate.BpmnError.<init>(BpmnError.java:48)
            at org.flowable.engine.impl.bpmn.behavior.ErrorEndEventActivityBehavior.execute(ErrorEndEventActivityBehavior.java:48)


        Root Cause:

        Flowable engine requires all <errorEventDefinition/> elements to have a valid errorRef.

        Some older BPMN files were deployed without a global error or without specifying errorRef on end events.
        Ayed Bada made changes -
        Description We identified an issue with the current Flowable process definitions in the system related to empty <errorEventDefinition/> elements in BPMN end events.
        Problem:

        In some deployed process definitions, end events had <errorEventDefinition/> without an errorRef.

        Flowable requires an error code for error end events.

        When these processes are executed, the following exception occurs:

        org.flowable.common.engine.api.FlowableIllegalArgumentException: Error Code must not be null
            at org.flowable.engine.delegate.BpmnError.setErrorCode(BpmnError.java:53)
            at org.flowable.engine.delegate.BpmnError.<init>(BpmnError.java:48)
            at org.flowable.engine.impl.bpmn.behavior.ErrorEndEventActivityBehavior.execute(ErrorEndEventActivityBehavior.java:48)


        Root Cause:

        Flowable engine requires all <errorEventDefinition/> elements to have a valid errorRef.

        Some older BPMN files were deployed without a global error or without specifying errorRef on end events.
        We identified an issue with the current Flowable process definitions on cloud env related to empty <errorEventDefinition/> elements in BPMN end events.
        Problem:

        In some deployed process definitions, end events had <errorEventDefinition/> without an errorRef.

        Flowable requires an error code for error end events.

        When these processes are executed, the following exception occurs:

        org.flowable.common.engine.api.FlowableIllegalArgumentException: Error Code must not be null
            at org.flowable.engine.delegate.BpmnError.setErrorCode(BpmnError.java:53)
            at org.flowable.engine.delegate.BpmnError.<init>(BpmnError.java:48)
            at org.flowable.engine.impl.bpmn.behavior.ErrorEndEventActivityBehavior.execute(ErrorEndEventActivityBehavior.java:48)


        Root Cause:

        Flowable engine requires all <errorEventDefinition/> elements to have a valid errorRef.

        Some older BPMN files were deployed without a global error or without specifying errorRef on end events.
        Hide
        Ayed Bada added a comment -

        This issue exists only on Cloud and is related to the Flowable version upgrade
        -------Solution Implemented--------

        1/// Developed a SOAP API method patchErrorEventDefinitions that:

        -Reads the latest process definitions.

        -Replaces empty <errorEventDefinition/> with <errorEventDefinition errorRef="ERR_TECHNICAL"/>.

        -Redeploys the patched BPMN automatically.

        2/// Intercepted all manual BPMN uploads through FN and SRD platforms to add any missing errorRef before deployment.

        Only empty error end events are modified; all other BPMN logic remains untouched.

        -------Impact-----

        -Fixes runtime exceptions caused by missing error codes.

        -Safe to deploy on staging or production before full validation.

        -Prevents regression by automatically patching future manual BPMN uploads.

        Show
        Ayed Bada added a comment - This issue exists only on Cloud and is related to the Flowable version upgrade ------- Solution Implemented -------- 1/// Developed a SOAP API method patchErrorEventDefinitions that: -Reads the latest process definitions. -Replaces empty <errorEventDefinition/> with <errorEventDefinition errorRef="ERR_TECHNICAL"/>. -Redeploys the patched BPMN automatically. 2/// Intercepted all manual BPMN uploads through FN and SRD platforms to add any missing errorRef before deployment. Only empty error end events are modified; all other BPMN logic remains untouched. ------- Impact ----- -Fixes runtime exceptions caused by missing error codes. -Safe to deploy on staging or production before full validation. -Prevents regression by automatically patching future manual BPMN uploads.
        Ayed Bada made changes -
        Status Open Bug [ 10108 ] Dev Scheduled [ 10014 ]
        Ayed Bada made changes -
        Status Dev Scheduled [ 10014 ] Implementation in progress [ 10016 ]
        Ayed Bada made changes -
        Status Implementation in progress [ 10016 ] To Be Released [ 10400 ]
        Khaled Khalil made changes -
        Component/s FN [ 16303 ]
        Khaled Khalil made changes -
        Status To Be Released [ 10400 ] Ready for QA [ 10023 ]
        Ayed Bada made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 7 hours [ 25200 ]
        Worklog Id 289834 [ 289834 ]
        Ayed Bada made changes -
        Baseline Start 2026-01-27 24:00 (set baseline based of initial work logging)
        Baseline End 2026-01-27 24:00 (set baseline based of initial work logging)
        Ayed Bada made changes -
        Time Spent 7 hours [ 25200 ] 1 day, 3 hours [ 39600 ]
        Worklog Id 289835 [ 289835 ]
        Ayed Bada made changes -
        Time Spent 1 day, 3 hours [ 39600 ] 1 day, 6 hours [ 50400 ]
        Worklog Id 289836 [ 289836 ]
        Ayed Bada made changes -
        Worklog Id 289836 [ 289836 ]
        Ayed Bada made changes -
        Time Spent 1 day, 6 hours [ 50400 ] 1 day, 5 hours [ 46800 ]
        Worklog Id 289836 [ 289836 ]
        Ayed Bada made changes -
        Time Spent 1 day, 5 hours [ 46800 ] 1 day, 6 hours [ 50400 ]
        Worklog Id 289836 [ 289836 ]
        Khaled Khalil made changes -
        Issue Type Bug [ 1 ] Task [ 3 ]
        Workflow Mobinets_Dev_BugWF_J4.4 [ 203612 ] ACE: Software Development Workflow [ 203807 ]
        Status Ready for QA [ 10023 ] Done [ 10000 ]
        Khaled Khalil made changes -
        Reporter Ayed Bada [ abada ] Zein Trabelsi [ ztrabelsi ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Bug Open Bug Dev Scheduled Dev Scheduled
        10m 47s 1 Ayed Bada 27/Jan/26 12:45 PM
        Dev Scheduled Dev Scheduled Implementation in progress Implementation in progress
        5s 1 Ayed Bada 27/Jan/26 12:45 PM
        Implementation in progress Implementation in progress To Be Released To Be Released
        7s 1 Ayed Bada 27/Jan/26 12:46 PM
        To Be Released To Be Released Ready for QA Ready for QA
        1m 46s 1 Khaled Khalil 27/Jan/26 12:47 PM
        Ready for QA Ready for QA Done Done
        2d 1h 23m 1 Khaled Khalil 29/Jan/26 2:10 PM
        Subversion JIRA

        Links Hierarchy

         Documentation

        Invalid license: EXPIRED

          People

          • Assignee:
            Ayed Bada
            Reporter:
            Zein Trabelsi
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Planned Start:
              Planned End:
              Actual Start:
              Date of Baselining:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 1 day, 6 hours
              1d 6h

                Drag and Drop