Is it possible to have a field driven input to a batch macro optional? i.e. if no field is mapped to the input a null (or other default) value is passed through the tool?
To give some context I'm using a macro to add data to a database, creating an event log as my workflows run, logging events that are worth capturing. My table has the following fields:
Workflow Name
Event Type
Event date time
File Name
For events such as 'workflow start' the file name would be NULL. For events such as 'file written' I would want to capture the file name.
Ideally the File Name macro input would only be populated for file specific events and could be left blank for non-file events - in other words populating the input would be optional.