You can use output properties in component processes and generic processes.
def exitCodeChecker = { exitCode ->
if (exitCode == 0) {
outputProps.setProperty("blaExists", "true");
exitValue = 0;
}
else if (exitCode == 30) {
outputProps.setProperty("blaExists", "false");
exitValue = 0;
}
else {
outputProps.setProperty("blaExists", "unknown");
exitValue = 1;
}
outputProps.setProperty("url", "http://example.com");
Then, you can refer to these output properties in other steps in a process. To do so, you must know the name of the step that contains the output property that you use. For example, your process might require different actions if a BLA exists. In this case, you could use a Switch step to branch the process for each case. In the following figure, the Switch step checks the value o f the blaExists output property by using the code ${p:Check If BLA Exists/blaExists}:
You can use output properties in other postprocessing scripts, step preconditions, step properties, or the code of steps themselves. Passing property values among processes, resources, and steps helps limit the requirement to provide input manually and to maintain accuracy and reliability.