Difference between revisions of "V1.5 SP 22.0"
From FPDS-NG
(Created page with "__NOEDITSECTION__ ==Schedule== <TABLE id="box-table-a" border=2> <tr><th width=30% align="center"><b>Description</b></th><th width=34% align="center"><b>Start Date</b></th> <...") |
|||
| Line 32: | Line 32: | ||
<td valign="top">Contracting Office Selection screen does NOT return results if Active Offices Only box is unchecked | <td valign="top">Contracting Office Selection screen does NOT return results if Active Offices Only box is unchecked | ||
<td valign="top">The FPDS application shall be updated to return all Contracting Office IDs (active and inactive) when the “Ellipses” button for the Contracting Office ID field is clicked, and the ‘Active Offices Only’ box is unchecked. | <td valign="top">The FPDS application shall be updated to return all Contracting Office IDs (active and inactive) when the “Ellipses” button for the Contracting Office ID field is clicked, and the ‘Active Offices Only’ box is unchecked. | ||
| + | |||
| + | |||
</td> | </td> | ||
| Line 41: | Line 43: | ||
<td valign="top">FPDS is not displaying complete OT Order information on Search Results page | <td valign="top">FPDS is not displaying complete OT Order information on Search Results page | ||
<td valign="top">The FPDS application shall be updated to display complete details for each Other Transaction Award/IDV listed on the <i>‘Search Results’</i> page when the FPDS “Advanced Search” feature is executed. | <td valign="top">The FPDS application shall be updated to display complete details for each Other Transaction Award/IDV listed on the <i>‘Search Results’</i> page when the FPDS “Advanced Search” feature is executed. | ||
| + | |||
| + | |||
<td align="center">Yes</td> | <td align="center">Yes</td> | ||
| Line 49: | Line 53: | ||
<td valign="top">Entity Address not updating on subsequent Award mods | <td valign="top">Entity Address not updating on subsequent Award mods | ||
<td valign="top">The FPDS application shall be updated so that when an Award modification is created or corrected, and the “Reason for Modification” is “Entity Address Change,” the updated address shall propagate to each existing modification with a later “Date Signed.” | <td valign="top">The FPDS application shall be updated so that when an Award modification is created or corrected, and the “Reason for Modification” is “Entity Address Change,” the updated address shall propagate to each existing modification with a later “Date Signed.” | ||
| + | |||
| + | |||
</td> | </td> | ||
| Line 59: | Line 65: | ||
<td valign="top">The FPDS application shall be updated to prevent the following validation rule from displaying on the first modification after a Transfer Action when no "Reason For Modification" is selected, and the “Date Signed” on the mod is after the date of the Transfer Action. | <td valign="top">The FPDS application shall be updated to prevent the following validation rule from displaying on the first modification after a Transfer Action when no "Reason For Modification" is selected, and the “Date Signed” on the mod is after the date of the Transfer Action. | ||
The "Date Signed" on a modification created after the "Transfer Action" cannot be earlier than the "Date Signed" on the "Transfer Action" modification. | The "Date Signed" on a modification created after the "Transfer Action" cannot be earlier than the "Date Signed" on the "Transfer Action" modification. | ||
| + | |||
</td> | </td> | ||
<td align="center">Yes</td> | <td align="center">Yes</td> | ||
Revision as of 16:12, 14 August 2024
Schedule
| Description | Start Date | End Date |
|---|---|---|
| Beta Deployment | October 07, 2024 | October 07, 2024 |
| Government Acceptance Testing | October 15, 2024 | October 18, 2024 |
| Production Deployment | October 26, 2024 | October 26, 2024 |
Document Changes
| Documentation | Changes Required |
|---|---|
| XML Specifications | No |
| Web Services | No |
| Data Dictionary | Yes |
| NASA Specific Data Dictionary | No |
| Use Case Summary | No |
| Validation Rules | No |
| ezSearch | No |
| Atom Feeds | No |
| Online Help | Yes |
| User Manual | Yes |
SPR Listing
| SPR # | Enhancement/Problem | Solution | Impact to Users and Integrators |
|---|---|---|---|
| IAEMOD-29106 | Contracting Office Selection screen does NOT return results if Active Offices Only box is unchecked | The FPDS application shall be updated to return all Contracting Office IDs (active and inactive) when the “Ellipses” button for the Contracting Office ID field is clicked, and the ‘Active Offices Only’ box is unchecked.
|
Yes |
| IAEMOD-30988 | FPDS is not displaying complete OT Order information on Search Results page | The FPDS application shall be updated to display complete details for each Other Transaction Award/IDV listed on the ‘Search Results’ page when the FPDS “Advanced Search” feature is executed.
| Yes |
| IAEMOD-31091 | Entity Address not updating on subsequent Award mods | The FPDS application shall be updated so that when an Award modification is created or corrected, and the “Reason for Modification” is “Entity Address Change,” the updated address shall propagate to each existing modification with a later “Date Signed.”
|
Yes |
| IAEMOD-32580 | Incorrect Date Signed rule triggered on First mod after Transfer action | The FPDS application shall be updated to prevent the following validation rule from displaying on the first modification after a Transfer Action when no "Reason For Modification" is selected, and the “Date Signed” on the mod is after the date of the Transfer Action.
The "Date Signed" on a modification created after the "Transfer Action" cannot be earlier than the "Date Signed" on the "Transfer Action" modification. |
Yes |