Hi @gmullins,
It looks like your questions here is a continuation of our previous conversation. Unfortunately, I don’t think we have a perfect solution to this right now. The information is technically sent in the payload but not in an easily consumable format.
The RelatedDocumentIds contains the Release-Id which can be used in the API to the full release object which has the version associated. Furthermore, the Message value mentions the release number, but this is designed as a human readable sting and doesn’t directly help in this situation.
I don’t have much ServiceNow experience, but I’m wondering if there are any options to integrate scripting with the payload value Octopus is sending it? If so, then you could use the Release-Id mentioned above to get the API results for that specific release and grab the value out.
I’m going to run this by the developers and see if there’s a reason we don’t put the release version in this payload. However, even if it’s an oversight, I can’t guarantee a quick turnaround on getting it added in.
Let me know if you have any questions on this.
Best regards,
Daniel