GSA / ITDB-schema

IT Dashboard submissions schema, documentation and example files.
19 stars 24 forks source link

Which schema should we be using for business case monthly submission? #411

Open KellyHarrisT opened 4 years ago

KellyHarrisT commented 4 years ago

Are we using the "master/archive" or "master/src"?

https://github.com/GSA/ITDB-schema/blob/master/archive/FY2021-Docs/FY2021-Schema/BusinessCase/Examples/monthlySubmission example:

a b yes

https://github.com/GSA/ITDB-schema/blob/master/src/BusinessCase/Examples/monthlySubmission.xml example:

2 no a 1970-01-01 IT WCF 2.0 This is a text field 4. This is a text field 5.

Thank you

KellyHarrisT commented 4 years ago

Probably a better question, why is it that we are getting validation errors:

Error 1871: Element '{http://www.itdashboard.gov/service}projectName': This element is not expected. Expected is one of ( {http://www.itdashboard.gov/service}projectGoal, {http://www.itdashboard.gov/service}softwareProject ). on line 64

Error 1871: Element '{http://www.itdashboard.gov/service}activityName': This element is not expected. Expected is one of ( {http://www.itdashboard.gov/service}projectedStartDate, {http://www.itdashboard.gov/service}actualStartDate, {http://www.itdashboard.gov/service}projectedTotalCost, {http://www.itdashboard.gov/service}actualTotalCost, {http://www.itdashboard.gov/service}projectedCompletionDate, {http://www.itdashboard.gov/service}actualCompletionDate ). on line 78

The definition files (XSD) say that those fields are expected.
Thank You

DEV2020_Jan_Treasury_Monthly_DEV.zip

samanthathomas20 commented 4 years ago

Hi Kelly,

Thanks for reaching out. To answer your first question, please use the example files located in the "src" folder "https://github.com/GSA/ITDB-schema/tree/master/src/BusinessCase/Examples". As for your second question, the reason you are receiving the error is because of the baseline requirements which have been re-instated for Project Name, Activity Name, and Activity description. In order to update those fields you will need to leverage the "reviseUpdateProject" XML.

Please let us know if you have any further questions.

Thanks, Sam ITDB Support

KellyHarrisT commented 4 years ago

Thanks Sam, We did not have any problem submitting last month. Were there changes that we did not hear about or what has changed?

Thank You, Kelly

From: Sam Thomas notifications@github.com Sent: Thursday, January 30, 2020 2:57 PM To: GSA/ITDB-schema ITDB-schema@noreply.github.com Cc: Harris, Kelly Kelly.Harris2@treasury.gov; Author author@noreply.github.com Subject: Re: [GSA/ITDB-schema] Which schema should we be using for business case monthly submission? (#411)

This message is from an EXTERNAL SENDER - be CAUTIOUS of links and attachments. THINK BEFORE YOU CLICK.

Hi Kelly,

Thanks for reaching out. To answer your first question, please use the example files located in the "src" folder "https://hyperlink.services.treasury.gov/agency.do?origin=https://github.com/GSA/ITDB-schema/tree/master/src/BusinessCase/Examples". As for your second question, the reason you are receiving the error is because of the baseline requirements which have been re-instated for Project Name, Activity Name, and Activity description. In order to update those fields you will need to leverage the "reviseUpdateProject" XML.

Please let us know if you have any further questions.

Thanks, Sam ITDB Support

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://hyperlink.services.treasury.gov/agency.do?origin=https://github.com/GSA/ITDB-schema/issues/411?email_source=notifications&email_token=ALE6BHXJ5EPDQDOL4BIM7CLRAMWHLA5CNFSM4KNZVWJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKMJZ3Q#issuecomment-580426990, or unsubscribehttps://hyperlink.services.treasury.gov/agency.do?origin=https://github.com/notifications/unsubscribe-auth/ALE6BHW77Q44W5UGVRO4OKDRAMWHLANCNFSM4KNZVWJA.

samanthathomas20 commented 4 years ago

Hi Kelly,

The update was deployed to the BY 2021 Production environment on Friday, January 3rd, and an email was sent out to the vendor community following the deployment that evening. We also informed the vendor community that this action was coming in advance via email and it was discussed on the vendor community tagups, since this was implemented based on OMB's approach. Also, the GitHub front page has a mention about this as well.

Thanks, Sam ITDB Support