UI enhancement in automation signature

-1) Create deployment topology with the following.
Windows 2008 server>MQ installation>Queue Manager>Local Queue> Sender Channel
All units to be in an 'installed state' except the Sender channel which is to be in a 'to be installed state'
Make sure there are no errors in the deployment toplogy by ensuring
dependecies are met by using the appropriate links and by supplying required data.

-2) Double Click on the Local queue unit and open the capabilities. Check the 'get' and
'put' check boxes to initiate get and put parameters for the local queue.

-3) Create automation signature with the following elements.
Queue Manager > Local Queue > Sender Channel.
Make sure Queue Manager and Local Queue are in an 'installed state' and make sure the Sender Channel is in a 'to be installed state'.
Make sure all dependency links are connected so that automation signature topology
has no errors.

-4) Publish the Sender Channel unit.

-5) Make sure the Local queue unit does not have the 'get' and 'put' capabilities checked in the automation signature topology


-6) Click on 'Analyse topology for possible automation signature matches' in the deployment
topology.

-7) Notice the error in matching- "get=true" for deployment topology and "get=false" for automation signature topology.

The behavior is working as designed. Attribute matching occurs for units in the signature regardless of their install state. However if an attribute value is not specified, matching is not enforced.

An enhancement request raised by user that UI should be improved since from a user perspective it is not clear once an automation signature has been created, what state the boolean attribute is in, without actually checking with the underlying XML description.