Uploaded image for project: 'JOC - JobScheduler Operations Center'
  1. JOC - JobScheduler Operations Center
  2. JOC-1632

It should be possible to change the declaration of a list variable that is already used in schedules

    XMLWordPrintable

Details

    • Feature
    • Status: Dismissed (View Workflow)
    • Medium
    • Resolution: Duplicate
    • 2.5.5, 2.6.2
    • 2.7.1
    • JOC Cockpit GUI
    • None

    Description

      Current Situation

      A workflow W1 declares the list variable l1 with the key f1 and f2 as String

      • W1 is assigned the schedule S1
      • S1 defines some entries.

      When changing f2 to be a Number and adding f3 as a String, the workflow is deployable.

      A message appears

      BadRequestError: WrongValueType: WrongValueType(name=l1[0].age, type=String, expectedType=Number)

      This error is from the automatic submission of orders to the Controller when changing a workflow that is assigned a schedule.

      The reason for this is, that the schedule already has entries where f2 is defined as String and f3 is missing.

      • There is no option to change the entries manually to fit the declaration in the workflow.
      • It is also not possible to delete all entries, as the last entry can not be deleted.

      To make the change effective the only possible way is to delete the list declaration completely and then to redeclare with f2:Number and f3:String. Then all entries in S1 must be typed in again.

      Desired Behavior

      When changing the declaration of a list variable in a workflow, all assigned lists should be changed automatically.

      When a type is changed to number
      If the source is String, try to convert to Number. If not successful, use the default number
      If the source is Boolean, convert true to 1 and false to 0

      When a type is changed to Boolean

      • If the source is string, try to convert to Boolean.
      • 1->true, true->true, yes->true, on-> true.
      • 0->false, false->false, no->false, off-> false.
      • If not successful, use the default Boolean=false.
      • If the source is number, convert > 0 to true and <=0 to false
      • When a key is removed, remove it from all lists
      • When a key is added, add it to all lists with a default value.

      Attachments

        Issue Links

          Activity

            People

              ap Andreas PĆ¼schel
              ur Uwe Risse
              Kanika Agrawal Kanika Agrawal
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: