Expression Resolver

[yuval-hazaz]

Expression Resolver

[yuval-hazaz]

Can you provide 3 example use cases?

All uses cases (currently) are in a workflow.
Some background:
During the flow, several data objects may be available in the context - a customer record that was
fetched from the DB, a result of a sub process, some values that were provided as an input and so on.
The creator of the flow should be able to make decisions based on the context, and also be able to use the data in context.

example 1:
Check if the customer age based on his data of birth is larger then a given input.
Return @DataDiff(Years, Context.Customer.DateOfBirth, Now()) > Context.Input.AgeToCompare
Example 2:
Use two separate input parameters to set the customer phone number
Return Context.Input.AreaCode + "-" + Contxt.Input.PhoneNumber
Example3:
Check the returned value of a sub process to determine what to do next
Return Context.SubProcessResults > 5

Some of the basic decisions and data manipulation can be done using other tools like the "Decision Table" but for more complex scenarios the developer will need the Expression Resolver

[yuval-hazaz]

Which language should we use?
Should we resolve on the client with the existing context or on the server? (probably server)
Should we allow full language features (e.g. if, then) or just expressions that resolve to a value?

see this: https://github.com/TechnologyAdvice/Jexl

[yuval-hazaz]

@iddan please see if you have any input for the discussion

[iddan]

Can you provide 3 example use cases?

[iddan]

Other option I'm familiar with: https://www.npmjs.com/package/@axa-ch/json-logic-js

[iddan]

And: https://www.npmjs.com/package/@briza/illogical

[iddan]

This is a great discussion. We'll reopen it once this feature is getting more relevant but for now, I'm closing it.