This bug has been fixed.

Fixed Version

  • Ver. 12.2.1

Affected Version and Operation

  • Ver. 12.2.0 and later versions
  • The aggregated value of a numeric column in a Table-type Data Item is referred to in the expression that has been set in a Numeric-type Data Item or in a Service Task (Data Assignment)

Bug Details

  • Occurs in a workflow App that meets all of the following conditions:
    • The expression that has been set in a Numeric-type Data Item or in a Service Task (Data Assignment) includes reference to the aggregated value of a numeric column in a Table-type Data Item
      • In “Service Task (Data Assignment)”, if it updates the value of a Numeric-type Data Item
    • The following two values In the numeric column in the Table-type Data Item that is referenced in the expression do not match
      • Table column number
      • Column index (0 start)
  • What will occur
    • The aggregated value is not reflected in the Numeric-type Data as the item specified in the expression is not referenced
Column setting in Table-type Data Item
Example of a bug consequence

Workround・Recovery

  • Please avoid this problem by the following method
    • For the column item (numeric) in Table-type whose aggregated value is referred to by the calculation expression, change the setting so that the following two values match
      • Table column number
      • Column index (0 start)/li>
    • You can change the display order of table columns with Drag & Drop
      • Please note that if you are outputting the table items in “Service Task (PDF generation)”, you will need to modify the “Base PDF” according to the change
    • You can change the table column number by deleting and adding the table column
      • When adding a table item, the number of “maximum number of existing table column + 1” is automatically set
    • If you find it is difficult to change the display order of table items or delete/add them, please consider defining a new Table-type Data Item from scratch
    • After matching the two values of the table item, make sure that the value referenced in the calculation expression (# q_table.summary [‘5’], etc.) is also the same value (“5” part), and correct if necessary
    • Please Start a new Process after modifying the App and [Releasing] it
  • An alternative way to workaround is to temporarily not use the value calculation expression. Please refer to the sum values in the table and enter them manually.
  • There is no way to avoid or recover from this problem for Processes that have already started. Consider rerunning the Process.
  • This bug is due to be fixed in the coming version (Ver. 12.2.1)

%d bloggers like this: