Major Business Case Validation Errors: Project Name, Activity Name, Activity Description

[kengineer]

We've been testing submissions against the UAT environment and notices when submitting a major business case annual submission that we are getting the following validation errors:

<sr:operationResults xsi:schemaLocation="http://www.itdashboard.gov/serviceResponse serviceResponse.xsd" xmlns:sr="http://www.itdashboard.gov/serviceResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <sr:schemaValidationError>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}projectName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectGoal, {urn:us:gov:businessCase-update}softwareProject ). on line 96</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 112</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 124</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 136</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 148</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 160</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 172</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 184</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}projectName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectGoal, {urn:us:gov:businessCase-update}softwareProject ). on line 199</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 216</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 226</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 236</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 245</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 255</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 265</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 274</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 286</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 296</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 305</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 314</sr:message>
      <sr:message level="error">Error 1871: Element '{urn:us:gov:businessCase-update}activityName': This element is not expected. Expected is one of ( {urn:us:gov:businessCase-update}projectedStartDate, {urn:us:gov:businessCase-update}actualStartDate, {urn:us:gov:businessCase-update}projectedCompletionDate, {urn:us:gov:businessCase-update}actualCompletionDate, {urn:us:gov:businessCase-update}projectedTotalCost, {urn:us:gov:businessCase-update}actualTotalCost ). on line 326</sr:message>
   </sr:schemaValidationError>
</sr:operationResults>

Here's a sample of what we're submitting

<businessCase-update:projects>
    <businessCase-update:updateProject>
        <businessCase-update:projectId>17207</businessCase-update:projectId>
        <businessCase-update:agencyProjectId>888</businessCase-update:agencyProjectId>
        <businessCase-update:updateProjectDetail>
            <!-- Causes Validation Error -->
            <businessCase-update:projectName>Implementation of eBilling</businessCase-update:projectName>
            <businessCase-update:projectGoal>Provide NRC Licensees with online bill pay for monthly, quarterly and annual license fee billing activity.</businessCase-update:projectGoal>
            <businessCase-update:softwareProject>yes</businessCase-update:softwareProject>
        </businessCase-update:updateProjectDetail>
        <businessCase-update:updateProjectMetric>
            <businessCase-update:newOrExisting>existing</businessCase-update:newOrExisting>
            <businessCase-update:existingMetric>
                <businessCase-update:metricID>24160</businessCase-update:metricID>
                <businessCase-update:agencyMetricID>62</businessCase-update:agencyMetricID>
            </businessCase-update:existingMetric>
            <businessCase-update:deploymentTarget>99.00</businessCase-update:deploymentTarget>
        </businessCase-update:updateProjectMetric>
        <businessCase-update:updateProjectActivities>
            <businessCase-update:updateProjectActivity>
                <businessCase-update:activityId>119490</businessCase-update:activityId>
                <businessCase-update:agencyActivityId>326</businessCase-update:agencyActivityId>
                <!-- Causes Validation Error -->
                <businessCase-update:activityName>Project Management</businessCase-update:activityName>
                <!-- Causes Validation Error -->
                <businessCase-update:activityDescription>Overall Project Management of the eBilling Initiative</businessCase-update:activityDescription> <!-- Causes Validation Error -->
                <businessCase-update:projectedStartDate>2018-10-01</businessCase-update:projectedStartDate>
                <businessCase-update:actualStartDate>2018-10-01</businessCase-update:actualStartDate>
                <businessCase-update:projectedCompletionDate>2019-09-30</businessCase-update:projectedCompletionDate>
                <businessCase-update:actualCompletionDate>2019-09-30</businessCase-update:actualCompletionDate>
                <businessCase-update:projectedTotalCost>0.146319</businessCase-update:projectedTotalCost>
                <businessCase-update:actualTotalCost>0.129781</businessCase-update:actualTotalCost>
            </businessCase-update:updateProjectActivity>
        </businessCase-update:updateProjectActivities>
    </businessCase-update:updateProject>
</businessCase-update:projects>

It seems that project name, activity name, and activity description are no longer expected when doing an update. Is this an error or something we need to change to accommodate with our submissions?

Thanks, Ken Nehring Supporting NRC

[samanthathomas20]

Hi Ken,

Hi Ken,

Thanks for reaching out. Per OMB guidance, Project Name, Activity Name, and Activity Description were submitted as regular updates for Pre-Decisional Submissions but are now back to being baselined fields. These changes have been reflected on both Production and UAT environments. To bypass the validation errors, please submit a rebaseline to update your project and activity fields.

Please let us know if you have any further questions.

Thanks, Sam ITDB Support

[kengineer]

Just to clarify, these fields are always allowed for submission in the Pre-Decisional submission, or was it just one time exception for the September 2019 submission? To put it another way, come September 2020, will we be able to submit these fields in the pre-decisional submission without a rebaseline?

[mayuri-khatri]

Hi Ken,

Thank you for your question. Relaxing the baseline requirements for those three fields was a one-time decision for the 2019 Pre-Decisional submission, due to the fact that field length requirements were truncated, allowing the necessary updates to be made without having to rebaseline all of the data for those fields.

Please let us know if you have any questions.

Regards, Mayuri ITDB Support