The Global Binding Value for literal autoscript variables should allow nulls

You requested an example.

Say we develop an autoscript to update the changeby / changedate attributes. Since the actual names of those attributes can vary, we will have LITERAL ALN variables to pass the names of those attributes from the script's object launch points. Today, Maximo 7.6.1.2 will force me to supply global binding values for those variables. It forces me to supply some garbage data, like . or n/a or none or null . What it should do is let me leave the global binding values blank / null, allowing me to force the launch point to provide a value.

Alternately, consider that autoscripts can be thought of as being functions. The Variables defined for a script are like the parameters of the function. I have yet to hear of a programming language that forces the developer to supply default arguments for every parameter a function takes, but this is what Maximo is requiring us to do with autoscripts. It would be absurd for Java to force IBM to supply a default string and instance of UserInfo when they declared MXServer.getMboSet(objectName, userInfo). It is equally absurd for IBM to force me to supply a value when I declare that an autoscript takes a variable.

Thank you for your submission - it would be helpful if you could give an actual example of what you are trying to achieve with this null variable request.