-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
2022 Week 05-07 (from Jan 31)
Our implementation should be able to handle use cases like the description below.
We do support expression functions, but their usage outside actions, we don't. For example:
{
"functions": [
{
"name": "isAdult",
"operation": ".applicant | .age >= 18",
"type": "expression"
},
{
"name": "isMinor",
"operation": ".applicant | .age < 18",
"type": "expression"
}
]
}
And in the state:
{
"states":[
{
"name":"CheckApplicant",
"type":"switch",
"dataConditions": [
{
"name": "Applicant is adult",
"condition": "${ fn:isAdult }",
"transition": "ApproveApplication"
},
{
"name": "Applicant is minor",
"condition": "${ fn:isMinor }",
"transition": "RejectApplication"
}
],
"defaultCondition": {
"transition": "RejectApplication"
}
}
]
}
See more details at: https://github.com/serverlessworkflow/specification/blob/0.8.x/specification.md#using-functions-for-expression-evaluation
