Is there any way that an executing decision service can access its own meta data?
Here’s the reason:
You may have lots of different versions of a decision running (in dev, test and prod)
And even In prod they may be deployed on many different servers.
When you look at the audit trail of rule messages you cannot tell which particular version it is or which server it ran on.
Now of course you could ask rule authors to add this info to their rule statements but that’s not reliable.
It might be nice to have some extended operators to capture this info so that it can be incorporated into the rule messages.
Possible an initial rule sheet that reports all the meta data?
I think the decision service name, version number and the server come back in the response payload automatically.
The old 4.3 messages included the name of the calling application.
But it would be nice to include this as necessary