Difference between revisions of "V1.4 SP2.1"

From FPDS-NG

(SPR Listing)
(SPR Listing)
Line 27: Line 27:
 
<tr>
 
<tr>
 
<td style="width:95px" valign="top">FPDSNG-3623</td>
 
<td style="width:95px" valign="top">FPDSNG-3623</td>
<td valign="top">Disabled users are able to submit data to FPDS-NG and create documents through Business Services.</td>  
+
<td valign="top">As of April 26th 2010, CCR has discontinued providing the following non-essential business types information of the Vendors.     
 +
1. Architecture and Engineering  (isArchitectureAndEngineering)
 +
2. Construction Firm  (isConstructionFirm)
 +
3. Research and Development (isResearchAndDevelopment)
 +
4. Service Provider (isServiceProvider)
 +
5. Other Business or Organization Type (isOtherbusinessOrOrganization)
 +
To maintain FPDS-NG data integrity, changes have to be made to the system.
 +
</td>  
 
<td valign="top">
 
<td valign="top">
*FPDS-NG shall perform authentication and authorization for all the requests through Business Services.  
+
FPDS-NG shall ignore the above mentioned CCR Flags for all the requests through Business Services.
*The new rule '''“Unauthorized user. Your FPDS-NG Service Originator User ID is disabled.  Please contact your FPDS-NG system administrator.”''' shall be fire when the Service Originator ID has been disabled.
+
FPDS-NG shall not send the above mentioned CCR flags for any responses through Business Services.
*Authorization error '''“Operation failed due to Authorization Failure”''' shall fire when the Service Originator ID does not have the privileges required or does not exist.
+
FPDS-NG shall not display the above mentioned CCR flags through the Web-Portal.
*Authentication error '''“Operation failed due to Authentication Failure”''' shall fire when the User ID does not exist or is disabled.
+
• Data Dictionary will be updated to remove the CCR flags.</td>
*User Locked error '''“For security purposes, user account '<<ID>>' has been disabled and locked from use because of five (5) unsuccessful log-in attempts. Please contact your FPDS-NG System administrator to have the user account unlocked.”''' Shall fire if the User ID or Service Originator ID is locked.
+
<td align="center">The 5 CCR flags mentioned above will not be sent in the XML responses.</td>
*Inactivity error '''“For security purposes, user account '<<ID>>' has been disabled due to ninety (90) days of inactivity. Therefore, access to FPDS-NG is not available, until the user account is re-enabled. Please contact your agency's FPDS-NG system administrator to have the user account re-enabled.”''' shall fire when User ID or Service Originator ID is inactive due to 90 days of inactivity</td>
 
<td align="center">No</td>
 
 
</tr>
 
</tr>

Revision as of 22:41, 6 May 2010

Schedule

DescriptionStart Date End Date
BETA Installation Friday May 07, 2010Friday May 07, 2010
Functional Qualification TestingFriday May 07, 2010Friday May 07, 2010
Installation in ProductionFriday May 14, 2010Friday May 14, 2010

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data Dictionary No
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesNo
Online HelpNo
Computer-Based TrainingNo
Report ManualNo

SPR Listing

SPR #ProblemSolutionImpact to Users and Integrators
FPDSNG-3623 As of April 26th 2010, CCR has discontinued providing the following non-essential business types information of the Vendors.

1. Architecture and Engineering (isArchitectureAndEngineering) 2. Construction Firm (isConstructionFirm) 3. Research and Development (isResearchAndDevelopment) 4. Service Provider (isServiceProvider) 5. Other Business or Organization Type (isOtherbusinessOrOrganization) To maintain FPDS-NG data integrity, changes have to be made to the system.

• FPDS-NG shall ignore the above mentioned CCR Flags for all the requests through Business Services. • FPDS-NG shall not send the above mentioned CCR flags for any responses through Business Services. • FPDS-NG shall not display the above mentioned CCR flags through the Web-Portal.

• Data Dictionary will be updated to remove the CCR flags.
The 5 CCR flags mentioned above will not be sent in the XML responses.