Is there way to create global variable?

@chmurray88 - if you place the expression library in a specific project, then any pipeline in that project can use it. If you place it in the project space / shared folder, then any pipeline within the project space (across all projects) can use it. If you place the file in the root shared (above all project spaces), then any pipeline within the org could use it.

When the expression file is migrated to other orgs, you could update the values specific to that org. For example, if you use the expression file to define SMTP properties for your Email snaps, those are probably fairly static; as opposed to AWS S3 buckets / directories that should be different between you dev/qa/prod orgs.

Unfortunately no such thing as global variables.

There are a few ways to accomplish what I think you’re looking for though:

• You could have your value as a pipeline parameter. Have a first pipeline that gets your token, and then executes a second pipeline, passing the token as a pipeline parameter. Then that second pipeline will have access to the parameter (like a global variable) for all of his steps (calling other pipelines, etc.)

• You can keep passing the token along from snap to snap. In your example, the pipeline execute snaps should have output documents with an “original” array containing the data that was passed in to the snap. if your token was part of that, you should be able to use a mapper to put the value back where you want it for the next downstream snaps, etc.

@dmiller - Are global variables supported yet? If not, do you know when they will be supported? We have lots of use cases for this.

Thanks!

Chris

@chmurray88 This has not been implemented. Product Management would need to decide if this is to be implemented.

@chmurray88 - have you looked at Expression Libraries yet?

You can’t update the values stored, but they can be referenced anywhere an expression is available.