Flow action with null value does not evaluate correctly with gs.nil statement in action script - Known Error

Flow action with null value does not evaluate correctly with gs.nil statement in action script Description Quebec Issue: Flow action with null value does not evaluate correctly with gs.nil statement in action script

Steps to Reproduce

For sample example to create the issue: - Create a flow action with a reference type pointing to cmdb_ci_win_server record - Add a script step with an input value set to the owned_by field from the cmdb_ci_win_server record - Check whether the owned_by input is null or not using the below script for reference: (function execute(inputs, outputs) { // ... code ... var initOwner = inputs.owner; if (!gs.nil(initOwner)) { gs.info('test2'); outputs.approvuser = initOwner; outputs.approvtype = 'user'; } else { outputs.approvtype = 'nil'; } })(inputs, outputs); - create the output variables accordingly for approvtype as string and approvuser as reference.user type - test the action and provide a windows server record as input that does not have a value for owned_by field - the script still evaluates to true and the approvtype is set to 'user' in the action operations.

Workaround For a workaround of this particular scenario using the gs.nil() against a GlideRecord variable consider to evaluate to use the field GlideRecord.sys_id rather that the GlideRecord object

E.g.: gs.nil(initOwner.sys_id)