Forum Discussion
@Charles,
Like Patrick, I was also thinking Velocity (VTL) as a solution, but as I tried to solution your original post, the Workday namespace convention in the property names adds some complexity. I don’t know if Velocity beats the null-safe mapper for your particular use case, but it can be good info for your tool belt in the future.
The kind of ugly solution I came up with (in a one-liner) is:
[
{
"output" : #set ($pd = $['wd:Project_Data']) #set ($ed = $pd['wd:End_Date']) #if (${ed}) ${ed} #else null #end
}
]
I’m not well versed in VTL, so there’s likely something a little cleaner than the above.
- tstack7 years agoFormer Employee
You should be able to reference the other library through the
lib
variable. Is that not working?For example, if you this as the library
helper.expr
:{ chefify: x => x + ' bork! bork! bork!' }
You should be able to reference it from another library, like so:
{ msg: () => lib.helper.chefify('Hello, World!') }
Note that if the references are not in functions, but directly in the top-level expression, you’ll need to ensure the libraries are listed in the right order in the pipeline properties.
- ayush_vipul7 years agoNew Contributor III
I found a better way to achieve what i was look for.
But thanks for highlighting this.@tstack
- ayush_vipul7 years agoNew Contributor III
I have a use case where a child pipeline has multiple expr files.
I want to pass a value to the child pipeline using which my chiled pipeline would choose one of the expression library.
is there a way to do it ?- tstack7 years agoFormer Employee
In the child pipeline properties, add a parameter that you’ll use to specify the library to load. Then, in the “Expression Libraries” section, add a path that uses the parameter you just created. You’ll probably also want to set the name of the imported library using the “As” column. In the screenshot below, the parameter is
config
and defaults to the library filedev.expr
and the library can be referenced vialib.conf
in expressions:In the parent pipeline, you’ll pass the
config
parameter with the library paths that you want. In the screenshot below, there are two documents entering the PipeExec with “dev.expr” and “prod.expr” as the paths. So, the child will execute first with the “dev” library and then with the “prod” library.
- ayush_vipul7 years agoNew Contributor III
Is there a way to declare methods with global scope in expression library.
Is nesting multiple libraries together a good preactice ?- tstack7 years agoFormer Employee
Do you mean without the
lib.libname
prefix? No, libraries are always imported under thelib
object.I’m not sure what you mean by this, can you give an example?