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

Expression in Follow-Up-Date for Tasks is not resolved

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Duplicate
    • Icon: L3 - Default L3 - Default
    • None
    • 7.2.0
    • engine

      I have a simple one-step process that creates a user task (see attached bpmn file). For the user task, I have set expressions for both the due date and the follow-up-date like so:

      camunda:dueDate="${dueDate}" camunda:followUpDate="${followUpDate}"

      I deploy the process in a WAR on Wildfly 8.2.0. Afterwards, I start an instance of the process via camunda tasklist, providing values for "dueDate" and "followUpDate" via the generic task form (see attached screenshot).

      The process instance starts without errors, but in tasklist and in the database (we are using H2 in our development environment) I can see that the value for dueDate has been set, but not for the followUpDate (it has a "null" value).

      It seems that the expression is not resolved/applied to the followUpDate. What am I doing wrong?

      I am testing with version 7.2.0 of the open source edition.

        This is the controller panel for Smart Panels app

          1. genericTaskForm.PNG
            genericTaskForm.PNG
            25 kB
          2. test-process.bpmn
            3 kB

            [CAM-3474] Expression in Follow-Up-Date for Tasks is not resolved

            Robert Gimbel added a comment -

            Hi Sven,

            did you mean to open a SUPPORT Case? This is the community JIRA project, without SLA.

            I can convert the issue if you like.

            Cheers
            Robert

            Robert Gimbel added a comment - Hi Sven, did you mean to open a SUPPORT Case? This is the community JIRA project, without SLA. I can convert the issue if you like. Cheers Robert

            Sven Jörges added a comment -

            Hi Robert,

            no, it's OK for me if this stays a "community ticket" without SLA - my workaround for the moment is to use the due date in place of the follow-up-date, as my specific client fortunately does not care.

            Just wanted to check whether this is a bug or pebcac.

            Cheering back
            Sven

            Sven Jörges added a comment - Hi Robert, no, it's OK for me if this stays a "community ticket" without SLA - my workaround for the moment is to use the due date in place of the follow-up-date, as my specific client fortunately does not care. Just wanted to check whether this is a bug or pebcac. Cheering back Sven

            Robert Gimbel added a comment -

            smirnov can you take a look please if this one is fixed already.

            Robert Gimbel added a comment - smirnov can you take a look please if this one is fixed already.

            Roman Smirnov added a comment -

            Hi Sven,

            It was a bug. It has been fixed with CAM-3097.

            Anyway, thanks for reporting it.

            Cheers,
            Roman

            Roman Smirnov added a comment - Hi Sven, It was a bug. It has been fixed with CAM-3097 . Anyway, thanks for reporting it. Cheers, Roman

              smirnov Roman Smirnov
              joerges@gfi.ihk.de Sven Jörges
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: