Difference between revisions of "FAADC Version 1.2"
From FPDS-NG
Line 172: | Line 172: | ||
<td align="center">Yes</td> | <td align="center">Yes</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</table> | </table> |
Revision as of 22:59, 20 June 2024
Schedule
Description | Start Date | End Date |
---|---|---|
Beta Deployment | July 01, 2024 | July 01, 2024 |
Government Acceptance Testing | July 08, 2024 | July 19, 2024 |
Production Deployment | November 16, 2024 | November 16, 2024 |
Document Changes
Documentation | Changes Required |
---|---|
XML Specifications | Yes |
Web Services | Yes |
Data Dictionary | Yes |
NASA Specific Data Dictionary | No |
Use Case Summary | Yes |
Validation Rules | Yes |
ezSearch | Yes |
Atom Feeds | Yes |
Online Help | Yes |
User Manual | Yes |
*Note: In addition to the release notes content below, more detailed information regarding the FAADC V1.2 Version Change can be found at the following link: https://www.fpds.gov/downloads/FAADC/FAADC_Webservice_Integration_Specifications_V1.2.pdf
This link contains:
- Version change summary
- Changes to Web Services (WSDL Changes)
- WSDL Mapping for new elements
- XML Specification Changes
- and more
SPR Listing
SPR # | Enhancement/Problem | Solution | Impact to Users and Integrators |
---|---|---|---|
IAEMOD-9905 | Version 1.1 genericTag Data Elements created with new XML tags in Version 1.2 and resetting of genericTags |
The FAADC application shall be updated as part of the genericTag maintenance during a version change, data elements utilizing genericTags in Version 1.1 will be given their own XML tags for future use in Version 1.2. The genericTags will be reset to nullify existing logic so they can be used for future purposes. The following data elements utilized genericTags in Version 1.1 and will have new XML tags in Version 1.2:
|
Yes |
IAEENH-885/IAEMOD-9907 | Enable FAADC to collect multiple CFDA Numbers/Descriptions | The FAADC application shall be updated to permit the collection of up to 5 Assistance Listings Numbers and Descriptions on a single award. The Assistance screen will be updated to include a new ‘Assistance Listings and Amounts’ section that will include all Assistance Listing information, their dollar amounts, as well as a ‘Predominant Assistance Listing’ checkbox, a ‘Remove Assistance Listing’ button, and an ‘Add Assistance Listing’ button.
Please click here to see the updated V1.2 Assistance user screen A new version of the ASSISTANCE and ASSISTANCEDELETED Atom Feeds will be created to reflect the multiple Assistance Listings. The 1.1 Atom Feeds will be decommissioned 6 months after (April 16, 2025) V1.2 Atom Feeds are implemented. A new Version 1.2 WSDL will be deployed. WSDL Version 1.1 will be retired and will only allow ‘Correct’ and ‘Get’ actions to be performed. Data Elements 2K: ‘Correction Delete Indicator’, 2L: 'Correction Delete Indicator Description' and 2M: ‘FABS Sent Date’ will be tracked at the Individual Assistance Level instead of at the previous record level. Data Element 7A will change XML tag name from ‘CFDANumber’ to ‘ALNumber’. Data Element 7B will change XML tag name from ‘CFDAProgramTitle’ to ‘ALProgramTitle’. The following data elements will now be auto calculated and will no longer allow input from the user:
The FAADC application shall be updated with these new data elements:
The FAADC application shall be updated with the following validation rules:
The FAADC application shall be updated with the following validation rules which are now based on the auto calculated dollar amounts. The rule verbiage shall also be updated as follows:
| Yes |
IAEENH-1228/IAEMOD-27666 | New "Discretionary" data element in FAADC required due to DATA Act requirements related to funding opportunity numbers | The FAADC application shall be updated to add a new data element named “Discretionary” which will have values “Yes” and “No” only.
The FAADC application shall be updated with the following validation rules to require a selection be made for this data element on all Grants and Cooperative Agreements, and to ensure that when values are provided for “Funding Opportunity Number” and “Funding Opportunity Goals Text," the Grant or Cooperative Agreement is discretionary, competitive, or both:
|
Yes |
IAEENH-1229/IAEMOD-27667 | FON Format new mandatory requirements for October 1st, 2023 per OMB memo M22-02 | The FAADC application shall be updated to require acceptable values be provided for both “Funding Opportunity Number” and “Funding Opportunity Goals Text” on all discretionary, competitive Grants and Cooperative Agreements. Additionally, the “Funding Opportunity Number” data element shall be disabled on non-Grants and non-Cooperative Agreements (AssistanceType = 06, 07, 08, 09, 10, or 11).
The FAADC application shall be updated with the following validation rules to ensure values are provided for both “Funding Opportunity Number” and “Funding Opportunity Goals Text” or for neither data element, and to require acceptable values for both data elements on discretionary, competitive Grants and Cooperative Agreements:
|
Yes |
IAEMOD-25630 | Validation rule for FICE incorrectly fires on Amendment | The FAADC application shall be updated to prevent this validation rule from firing incorrectly on Amendments:
This affects Assistance Amendment record requests including Validate(isComplete)/Correct/Approve. |
Yes |