Legacy Lava in Workflow

Question 1

CLIENT: Northpointe

ASANA TASK: https://app.asana.com/0/1203194444641517/1203588930320816/f

They are getting a lot of Lava exceptions related to this workflow: https://rock.northpointe.org/admin/general/workflows?workflowTypeId=73&ExpandedIds=C350

Exceptions List: https://rock.northpointe.org/admin/system/exceptions/50705

Can someone help me correct the 'legacy lava syntax' that it is using?

Question 2

Legacy lava is when you access attribute values using dot notation instead of using the "Attribute" filter. In that Screenshot, "TransactionCodesTransformed" is an attribute, but the Lava references it using Workflow.TransactionCodesTransformed instead of Workflow | Attribute:'TransactionCodesTransformed'. That's just one instance. You can see later in the Lava it's doing same thing with "ProcessorBatchTotal".

DavidTurner · Answer 1 · 2023-01-19T17:45:08+0000

Legacy lava is when you access attribute values using dot notation instead of using the "Attribute" filter. In that Screenshot, "TransactionCodesTransformed" is an attribute, but the Lava references it using Workflow.TransactionCodesTransformed instead of Workflow | Attribute:'TransactionCodesTransformed'. That's just one instance. You can see later in the Lava it's doing same thing with "ProcessorBatchTotal".

Legacy Lava in Workflow

Please log in or register to add a comment.

Please log in or register to answer this question.

1 Answer

Please log in or register to add a comment.