RE: local variables

Mathieu Drouin — Sun, 10 Sep 2023 12:27:27 GMT

Depends on what you want to do. If you are actually typing a value in the Account Balance field, this is what it would look like:

a!localVariables(
  local!currencyType: 1,
  local!record: a!map(
    USD: 0,
    USDBALANCE: 0,
    dollar: 0,
  ),
  local!usd: local!record.USD,
  local!usdBalance: local!record.USDBALANCE,
  local!dollar: local!record.dollar,
  {
    a!floatingPointField(
      label: "Account Balance",
      value: local!usdBalance,
      saveInto: {
        local!usdBalance,
        a!save(
          local!dollar,
          a!match(
            value: local!currencyType,
            equals: 1,
            then: {
              if(
                a!isNotNullOrEmpty(local!usdBalance),
                (local!usdBalance / 3.5),
                - 1
              )
            },
            equals: 2,
            then: { local!usdBalance },
            equals: null,
            then: { false() },
            default: then: { false() }
          )
        ),
        a!save(local!usd, local!dollar)
      }
    ),
    a!floatingPointField(
      label: "Dollar Equivalent",
      labelPosition: "ABOVE",
      value: local!dollar,
      saveInto: local!dollar
    )
  }
)

If you want to handle the case where you pre-populate these values and just save them back without you typing anything. It would be best to calculate them before sending them as rule inputs. Otherwise, you could also initialize them as local variables but you have to be sure to save them back into your rule input when you submit the form.

A couple of extra links that might help:

RE: local variables

Stefan Helzle — Sun, 10 Sep 2023 09:38:40 GMT

That is because you fell into a typical trap like many others new to Appian. Input fields do only display a value, and the saveInto is only ever evaluated when the user types a different value. This means, that you need to make any calculations in the saveInto using one or more a!save().