Version Server 1.67.5 | Client 1.98.0 | Docu 2.19.4 | Styleguide 0.63.3
Released: 26.08.2021


Compatibility

  • ONE DATA 46.51.0
  • Portal 1.4.0
  • OAuth 1.1.3

Features

  • Add "logged-in user" to the set of available Apps variables.
  • Add the option to set variables (hardcoded in the first iteration) via a WF execution button.
  • HTML is rendered in table but not rendered (plain html text) in the filter dropdown of the table column.
  • Add the option to "action buttons" to also execute a function with variable assignments.
  • HTML is not rendered in the text input elements in Apps, but is shown as a plain html text.
  • Automplete needs double click if something is pasted to actually take the pasted value.

Bugfixes

  • App builder does not save after multiple changes and history version selection wrong.
  • Postgresql dialect not detected by sql editor.

Deprecation

With the latest release of Apps the variableAssignments property has been deprecated and replaced with the all new endpointParameters. This means the variableAssignments will still work, but will be removed in the future (in ca. 6 months). Please check your existing Apps, especially when using table actions or/and execute button element, as those allow you to use the variableAssignments property.


// deprecated, but still working approach
"variableAssignments": [
  {
    "variableName": "user_name",      // Technical variable name
    "variableType": "STRING",         // Variable value type
    "variableValueColumn": "Name"     // Column in the table element in which the value is present that should be passed to ONE DATA
  },
  {
    "variableName": "user_email",      // Technical variable name
    "variableType": "STRING",         // Variable value type
    "variableValueColumn": "Email"    // Column in the table element in which the value is present that should be passed to ONE DATA
  }
]

// new, fancy approach replacing the deprecated one from above  
"endpointParameters": [
  {
    "name": "user_name",          // Technical variable name
    "type": "STRING",             // Variable value type
    "valueFromColumn": "Name"     // Column in the table element in which the value is present that should be passed to ONE DATA
  },
  {
    "name": "user_email",         // Technical variable name
    "type": "STRING",             // Variable value type
    "valueFromColumn": "Email"    // Column in the table element in which the value is present that should be passed to ONE DATA
  }
]