The result is always a boolean value (0 or 1) written into target_key.
The activity is designed to run within "shared workflows" and reads the data source configuration details from a config path. The default path is $interface.$server.eligible which can be changed by setting the config_path parameter.
Put this configutation into your server configuration:
eligible: value@: connector:your.connector args: - "[% context.cert_subject %]" - "[% context.url_mac %]" expect: - Active - Build
The check will succeed, if the value returned be the connector has a literal match in the given list.
If you do not specify an expect list, the return value is mapped to a boolean result by perl magic. Note: Perl magic might not work as expected if your data was transported in text format and has trailing newlines or any other "hidden" characters. Sanitize your input or use the match option.
Compare result using a RegEx
Instead of a static expect list, you can also define a regex to evaluate:
eligible: value@: connector:your.connector args: - "[% context.cert_subject %]" - "[% context.url_mac %]" match: regex: (Active|Build) modifier: ''
In cases where you just need a static value, independant from the actual request content, leave out the arguments section and use a literal value:
eligible: value: 1
Sidenote: You can use a connector here as well, but in static mode we always test for a literal "1" as return value!