We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.16.0, 7.16.0-alpha1
    • None
    • None
    • None

      AT

      • Set a map of variables to the process instance scope of the process instances after the migration (see CAM-13406 for reasoning)
      • Variables can be set via migration plan builder (see CAM-13401 for reasoning)
      • Reuse the batch variable concept (introduced with CAM-12301)
        • Batch id is stored in the config of execution jobs to query for the variable by batch id on handler execution
        • Batch id is stored in VAR_SCOPE_ and BATCH_ID_ column
        • No history is written (follow-up ticket CAM-12302)
        • Batch variables are deleted in monitor job handler
      • Set variables are reflected in the operation log: nrOfVariables
      • Transient variables are supported synchronously but not asynchronously (follow-up ticket CAM-12332)
      • Prevent Java deserialization when javaSerializationFormatEnabled is false by throwing an exception
        • The problem is reflected per each variable in the migration report
      • REST API exists
      • Docs exists

        This is the controller panel for Smart Panels app

            Loading...

              • Icon: Sub-task Sub-task
              • Resolution: Fixed
              • Icon: L3 - Default L3 - Default
              • 7.16.0, 7.16.0-alpha1
              • None
              • None
              • None

                AT

                • Set a map of variables to the process instance scope of the process instances after the migration (see CAM-13406 for reasoning)
                • Variables can be set via migration plan builder (see CAM-13401 for reasoning)
                • Reuse the batch variable concept (introduced with CAM-12301)
                  • Batch id is stored in the config of execution jobs to query for the variable by batch id on handler execution
                  • Batch id is stored in VAR_SCOPE_ and BATCH_ID_ column
                  • No history is written (follow-up ticket CAM-12302)
                  • Batch variables are deleted in monitor job handler
                • Set variables are reflected in the operation log: nrOfVariables
                • Transient variables are supported synchronously but not asynchronously (follow-up ticket CAM-12332)
                • Prevent Java deserialization when javaSerializationFormatEnabled is false by throwing an exception
                  • The problem is reflected per each variable in the migration report
                • REST API exists
                • Docs exists

                  This is the controller panel for Smart Panels app

                        tassilo.weidner Tassilo Weidner
                        tassilo.weidner Tassilo Weidner
                        Tassilo Weidner Tassilo Weidner
                        Yana Vasileva Yana Vasileva
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              tassilo.weidner Tassilo Weidner
                              tassilo.weidner Tassilo Weidner
                              Tassilo Weidner Tassilo Weidner
                              Yana Vasileva Yana Vasileva
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              1 Start watching this issue

                                Created:
                                Updated:
                                Resolved: