Ok, I see. So there are couple of ways you can refer key objects in a "dynamic way". However, this requires you to use JOSE recipient/key id header with JSON Web Security decryption or Keyinfo element following the XML encryption standard.
The third option is to customize the standard template store://decrypt.xsl and through the advanced tab of decrypt processing action change the stylesheet. However, this is not a simple task as the template xsl includes store://dp/decrypt-node.xsl that defines the decrypt key as dpconfig parameter. In order to achieve your goal, I think you might also have to customize decrypt-node.xsl file. To make things even more difficult the dp folder is hidden so basically you cannot see (anymore) the template calls that decrypt-node.xsl has. So basically, the third option probably isn't worth the effort if you already have a working Gatewayscipt to decrypt the message. You can just check the contents of the AAA file in GW script and decide what key to use for the decryption.
Long and complicated explanation, but hope it gives you an idea what is feasible.
--HP
#DataPower#Support#SupportMigration