Deployment Report Submission Confirmation Validation

In reviewing the validations and XML related to the "Deployment Report", I am looking to confirm two items:

1. Does the term "Deployment Report" generally refer to all of fields #14-#20 in the activity table, or does it exclude the end user fields - #19-#20?
2. Is #14 - Software Development Activity with Multiple Releases - reported anywhere other than the new deployment report schema?

I mainly ask these questions because of the new Submission Confirmation validation, which reads "# Deployment Reports must be submitted for Active or Future Top Level Activities with multipleReleases = "Yes"."

This validation appears to be circular in that, in order to indicate multiple releases, the activity must submit a deployment report, unless there is a plan to also add this field to the business case and standard investment schemas. In effect, it would mean that no activity needs to submit a deployment report because none could have reported multiple releases.

Additionally, it seems like the logic is potentially inconsistent with the guidance and other validations in that even if the activity does not have multiple releases, it appears the end user mode of engagement and results (which can be blank if mode is none) are required and are - at least as the XSD is defining it - part of the deployment report.

Hopefully this is just a matter of clarifying the submission confirmation error message as it does appear the other validations and the XSD are consistent with the guidance and what we expected for required reporting.

Thanks,

Bill