ID 99950 - AttributeScript nodes set up an "applyWhen" opArg, but this is not used by the AttributeScript Op

Follow

Problem summary
AttributeScript nodes, when constructing opArgs for the AttributeScript Op, adds a "applyWhen" op arg, but this is not used by the AttributeScript Op.
When an AttributeScript node is set to run in deferred mode, this op arg is visible to users who inspect attributes. It has the potential to mislead users who wish to run the AttributeScript in unintended ways.

Customer reported version
katana.2.1v1

Customer reported platform
centos6

Steps to reproduce
1. Set up a deferred AttributeScript node
2. View the attributes at location the AttributeScript is applied
3. Observe that a "ops.AttributeScript.opArgs.applyWhen" attribute exists. 

Workaround
Using an OpScript instead appears to work as expected.
Rebuild your AttritbuteScript code to work with OpScript instead.

Reproduced by support

This bug has been reproduced in:

Katana2.6v4 - CentOS6.9 - Windows 7
Katana2.6v1 - CentOS6.9 - Windows 7
Katana2.5v7 - CentOS6.9 - Windows 7
Katana2.5v1 - CentOS6.9 - Windows 7
Katana2.1v6 - CentOS6.9
Katana2.1v1 - CentOS6.9

Earliest version tested
- This issue appears to be in all versions of the product

Expected behaviour
The AttributeScript should defer as it is intended in the script.

Actual behaviour
The AttributeScript is not being calculated and performed properly.

 

    We're sorry to hear that

    Please tell us why