Known Software USABILITY Issues

The purpose of this file is to briefly identify known usability issues
found either through testing or through calls to the Helpdesk. A test
finding is documented as a Problem Report (PR). One method of closing a
PR is to develop a more formal Software Change Request (SCR) or Software
Problem Report (SPR) to be considered for a future software update.

Table 1 Known PDL Usability Issues and WorkArounds

+---------+------------------------------------------------+----------+
| **      | **Workaround**                                 | **As     |
| Issue** |                                                | sociated |
|         |                                                | SCR/     |
|         |                                                | SPR/     |
|         |                                                | PR**     |
+---------+------------------------------------------------+----------+
| *       |                                                |          |
| *Config |                                                |          |
| uration |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| Ma      | The Oracle Web Utility functionality that is   | PR 381/  |
| cintosh | used for File Transfers does not operate with  | SPR      |
| and     | Macintosh computers. This means that the file  | 7        |
| File    | transfer functionality to download reports     | 0-03890, |
| Tr      | from the Reports Framework \> My Reports       | PR 871   |
| ansfers | location, downloading Drawings, and            |          |
|         | downloading C&DH ASCII Reports (coming in PDL  |          |
|         | Release 17.0) generate an error. An Oracle     |          |
|         | Technical Assistance Request (TAR) -           |          |
|         | 4793283.993 - Unable to use WebUtil            |          |
|         | FileTransfer with Mac WUC-015 has been opened. |          |
|         | Workaround for Report Generation: When running |          |
|         | a report, display it after completion (a new   |          |
|         | browser window is opened); then the user can   |          |
|         | save the file to their Macintosh hard drive    |          |
|         | from the browser window. Workaround for        |          |
|         | Drawing Downloads does not exist. Call the PDL |          |
|         | Helpdesk.                                      |          |
+---------+------------------------------------------------+----------+
| M       | Using two PC monitors with PDL will not work.  | Help     |
| onitors | Dragging a PDL screen onto the second monitor  | Desk     |
| with    | will lockup all of the controls. Should you    | call     |
| PDL     | return the screen back to the primary monitor  |          |
|         | the system will still be locked up.            |          |
+---------+------------------------------------------------+----------+
| Browser | If you are having difficulty starting the PDL  | PR 424   |
| S       | tool, please first check your Browser Settings |          |
| ecurity | by referencing Configure Browser Settings on   |          |
| S       | the right side of the main PDL News Page.      |          |
| ettings |                                                |          |
+---------+------------------------------------------------+----------+
| Ma      | On the Macintosh, when your first run "My      | PR 438   |
| cintosh | Reports" from the Reports Framework, the       |          |
| Safari  | Safari browser will display a "Certificate"    |          |
| S       | window asking you to accept the security       |          |
| ecurity | certificate from the PDL site, verifying that  |          |
| Cert    | it is okay to trust files downloaded from PDL. |          |
| ificate | The user must click "OK". If you click         |          |
|         | "Cancel" the Safari browser will block the     |          |
|         | Oracle Web Utilities used to download files.   |          |
|         | The certificate will be active as long as the  |          |
|         | Safari browser window is still open. This      |          |
|         | behavior is specific to the Safari browser on  |          |
|         | the Mac.                                       |          |
+---------+------------------------------------------------+----------+
| S       | Ctrl + Up and Crtl + Down do not work when     | SCR      |
| hortcut | pressed from the MAC keyboard. However, they   | 33200/   |
| Keys do | do when when selected from the Record menu on  | PR 411   |
| not     | the MAN1 screen.                               |          |
| Work    |                                                |          |
| from a  |                                                |          |
| MAC     |                                                |          |
| K       |                                                |          |
| eyboard |                                                |          |
+---------+------------------------------------------------+----------+
| **P     |                                                |          |
| assword |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| P       | 1\. When a user\'s password has been used for  | SCR      |
| assword | 90 days, the Change Password screen will       | 32811,   |
| Exp     | appear with the following message: \"Error:    | SCR      |
| iration | Your password is about to expire. Please       | 32874    |
| and     | change it\". The screen contains fields for    |          |
| Notif   | the user to enter a new password. However, it  |          |
| ication | is not intuitive that the user can press       |          |
|         | Cancel to continue logging in and that they    |          |
|         | can change the password at a later time. The   |          |
|         | software does not inform the user that they    |          |
|         | have 30 days to change the password before it  |          |
|         | expires and they have to call the PDL Help     |          |
|         | Desk.                                          |          |
|         |                                                |          |
|         | 2\. When the user gets the message \"Error:    |          |
|         | Your password is about to expire. Please       |          |
|         | change it\" and the user changes the password  |          |
|         | at that time, the user logs in successfully.   |          |
|         | However, the next time the user logs in (it    |          |
|         | can be the same day or the next day - before   |          |
|         | 90 days), the following message appears:       |          |
|         | \"Error: You must change your password before  |          |
|         | you can continue\" appears. This should not    |          |
|         | happen because the user recently changed the   |          |
|         | password and the password should have another  |          |
|         | 90 days before the user starts receiving the   |          |
|         | warning. The user pressed the Cancel button,   |          |
|         | but it did not allow the user to continue with |          |
|         | logging in. The user is required to change     |          |
|         | their password again.                          |          |
|         |                                                |          |
|         | 3\. When the password has expired and the user |          |
|         | attempts to log in, the user types in the      |          |
|         | Username and Password. When the Login button   |          |
|         | is pressed, the Password field is clear and    |          |
|         | the cursor appears next to the username in the |          |
|         | Username field; the user is not allowed to     |          |
|         | login. The user can continue to type in a      |          |
|         | password and press the Login button, but same  |          |
|         | thing will happen. There is no indication on   |          |
|         | the screen why the user was not able t o log   |          |
|         | in (that the password has expired and the user |          |
|         | must call the PDL Help Desk).                  |          |
|         |                                                |          |
|         | 4\. If a user password expires and the user    |          |
|         | contacts the PDL Help Desk to reset their      |          |
|         | password, at the next log on, the user is      |          |
|         | redirected to reset their password. However,   |          |
|         | when the user exits PDL and logs in the next   |          |
|         | time, the user is still required to change     |          |
|         | their password (a second time).                |          |
+---------+------------------------------------------------+----------+
| **      |                                                |          |
| Adminis |                                                |          |
| tration |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| Admin - | When creating a team, the Class LOV is not     | SCR      |
| Class   | enabled. Workaround: The user must type in the | 33819/   |
| LOV is  | Class.                                         | PR 652   |
| not     |                                                |          |
| enabled |                                                |          |
+---------+------------------------------------------------+----------+
| Payload | A user must have the ISS Integration Read      | PR 395   |
| Sel     | privilege enabled by the Team Manager from the |          |
| ections | Administration Screen in order to see the list |          |
| from    | of payloads on the PRO1 screen.                |          |
| the     |                                                |          |
| Promote |                                                |          |
| /Demote |                                                |          |
| Screen  |                                                |          |
+---------+------------------------------------------------+----------+
| User    | In order to access the Bench Review Tab on the |          |
| Access  | Drawings screen, the user must be a member of  |          |
| to      | the Bench Review Team. Contact the PDL Help    |          |
| D       | Desk.                                          |          |
| rawings |                                                |          |
| Bench   |                                                |          |
| Review  |                                                |          |
| Tab     |                                                |          |
+---------+------------------------------------------------+----------+
| **PDL   |                                                |          |
| Desktop |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| Move    | Intermittent problems with entering a value    | SCR      |
| "N"     | into the No. of space field of the Move N      | 34003/   |
| spaces  | spaces popup.                                  | PR 869   |
| field   |                                                |          |
|         | Workaround: Close PDL Desktop windows and      |          |
|         | re-open and the problem usually disappears.    |          |
+---------+------------------------------------------------+----------+
| Adding  | When trying to add multiple datasets to a      | SCR      |
| m       | shell, sometimes the cursor does not go to the | 34004/   |
| ultiple | blank dataset field. This appears to be an     | PR 870   |
| d       | intermittent problem. If this occurs and you   |          |
| atasets | continue to add a new dataset, the following   |          |
| to      | message appears: "FRM-40105: Unable to resolve |          |
| shell   | reference to item                              |          |
|         | Shells_Label_blk.dummy_Shell_Name. ORA_01403:  |          |
|         | no data found." Click Ok to this message and   |          |
|         | the dataset popup appears. All datasets        |          |
|         | including those already selected for this      |          |
|         | shell are active. If you select cancel the     |          |
|         | following message appears: FRM-41805 Ambiguous |          |
|         | item name shell_ID ORA-01403: no data found."  |          |
|         | If you select OK, the popup goes away and      |          |
|         | nothing further happens.                       |          |
|         |                                                |          |
|         | Workaround: Make sure the cursor is in the     |          |
|         | field by clicking in the field more than once  |          |
|         | before continuing.                             |          |
+---------+------------------------------------------------+----------+
| **ICE   |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| ICE -   | A tester created a change package, updated an  | PR 637/  |
| "No     | Item part, added a new Item Part, and deleted  | SCR      |
| data    | an existing Item part. However, when the       | 33630    |
| found"  | delete action was performed, "no data found"   |          |
| popup   | popup message was displayed on the screen.     |          |
| message | Also, since the screen did not get refreshed,  |          |
| appears | the deleted Item Part was still displayed on   |          |
| intermi | the screen. This issue appeared to be          |          |
| ttently | intermittent.                                  |          |
| when    |                                                |          |
| user    | Workaround: Just acknowledge the popup error   |          |
| deletes | message. To verify the Item was deleted, a     |          |
| an Item | user should close the change package and       |          |
| part    | reopen the same package, the deleted Item part |          |
| inside  | will not be shown on the screen. When "no data |          |
| a       | found" message displayed, there will be        |          |
| change  | duplicate "Del" entries in From/To table.      |          |
| package |                                                |          |
+---------+------------------------------------------------+----------+
| C       | If you will be designated as a person to       | Helpdesk |
| EF/PIRN | approve CEF and/or PIRN changes in ICE, please | Call     |
| ICE     | contact the Help Desk. The Help Desk must add  |          |
| Ap      | your team identification to a table in PDL in  |          |
| provers | order for the all designated approvers on that |          |
|         | team to approve CEF/PIRN ICE changes.          |          |
+---------+------------------------------------------------+----------+
| ICE2    | Intermittently, the CEF portion of the ICE2    | PR 631/  |
| Screen  | screen fails to display the CEF data at the    | SCR      |
| Display | center of the screen. Workaround: Return to    | 33631    |
| of CEF  | the ICE1 screen, select a different change     |          |
| Data    | package, re-select the desired change package  |          |
|         | and return to the ICE2 screen.                 |          |
+---------+------------------------------------------------+----------+
| ICD     | The value of the Package ID number does not    | SPR      |
| Input   | display correctly. This only occurs when the   | 7        |
| Data    | selected report format is not the              | 0-04018/ |
| R       | Required/Optimal format (i.e., not Excel).     | PR 635   |
| eport - |                                                |          |
| From/To | Workaround: Select Report output in optimal    |          |
| Format  | format.                                        |          |
| (pdf)   |                                                |          |
+---------+------------------------------------------------+----------+
| Package | When the user selects the Package Closed Time  | SPR      |
| Closed  | Limit as a parameter for the report, an error  | 7        |
| Time    | message is received and the report is not      | 0-04019/ |
| Limit   | generated.                                     | PR 636   |
| Se      |                                                |          |
| lection | Workaround: Leave the Package Closed Time      |          |
| for ICD | Limit criteria for the report blank.           |          |
| Input   |                                                |          |
| Data    |                                                |          |
| Report  |                                                |          |
| and ICE |                                                |          |
| Input   |                                                |          |
| Data    |                                                |          |
| Report  |                                                |          |
| From/To |                                                |          |
+---------+------------------------------------------------+----------+
| Maximum | The ICE2 --Change Package Details screen does  | SCR      |
| Cha     | not accept the maximum amount of characters    | 33501/   |
| racters | that's required in Change Title and Impact     | SPR      |
| on ICE2 | Statement fields. The Change Title field       | 7        |
| Screen  | should accept 500 characters, but appears to   | 0-03998/ |
|         | only accept 250. The sub-fields of the Impact  | PR 611   |
|         | Statement should all be able to accept 500     |          |
|         | characters also, but appears to be 300 for     |          |
|         | each (except Hardware Configuration which      |          |
|         | accepted on 231).                              |          |
|         |                                                |          |
|         | This also affected the screen report, which    |          |
|         | appeared to not be capable of displaying all   |          |
|         | of the data that was entered.                  |          |
+---------+------------------------------------------------+----------+
| CEF     | The PTP Parent Name, Mass Allocation, and      | SCR      |
| Con     | Volume Allocation fields located on the MAN2   | 33478/   |
| trolled | Screen allow the user (with write privileges)  | PR 601   |
| Fields  | to update the data without automatically       |          |
| on the  | capturing the change as an ICE CEF change. The |          |
| MAN2    | ICE logic was not integrated with the MAN      |          |
| Screen  | form. Therefore, the software prompts the user |          |
|         | that a CEF is required for the field change    |          |
|         | only, and the software accepts the updated     |          |
|         | value. Workaround is human coordination until  |          |
|         | corrected.                                     |          |
+---------+------------------------------------------------+----------+
| MAN     | If a user adds an Ascent Item Part in a change | SCR      |
| Ascent/ | package, then reviews the proposed changes on  | 33479/   |
| Descent | the ICE2 change package details screen, the    | PR 603   |
| Item    | change automatically includes default values   |          |
| Parts   | for Descent only fields. This can be confusing |          |
| in an   | to the user. No workaround exists.             |          |
| ICE     |                                                |          |
| Change  |                                                |          |
| Package |                                                |          |
+---------+------------------------------------------------+----------+
| PTP     | If a change to an Item Part record exists in   | SCR      |
| Parent  | an ICE change package, the user is able to     | 33480/   |
| D       | delete the PTP Parent if the user has correct  | PR 610   |
| eletion | privileges. The software should automatically  |          |
|         | prevent the deletion of a record if there is a |          |
|         | pending change package against that record. No |          |
|         | workaround exists.                             |          |
+---------+------------------------------------------------+----------+
| ICE Ad  | The ICE1 Ad Hoc report does not sort on the    | PR 510   |
| Hoc     | change package ID logically because the List   |          |
| Report  | of Values is required to be a character field. |          |
| Sort    | For example, package IDs of 221 and 241 are    |          |
|         | listed prior to IDs of 61 and 81 when sorting  |          |
|         | IDs in ascending order. The sort is based on   |          |
|         | character (LOV) rather than an expected        |          |
|         | numeric sort. The workaround is to use the     |          |
|         | "Package Id Sort" field. The user can select   |          |
|         | this field for their report, create a sort for |          |
|         | it then click the "Hidden" checkbox next to    |          |
|         | it. This will sort the report by this field    |          |
|         | but it will not display this field on the      |          |
|         | report.                                        |          |
+---------+------------------------------------------------+----------+
| **      |                                                |          |
| Reports |                                                |          |
| Fr      |                                                |          |
| amework |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| Reports | Reports name in subfolders do not show when    | SCR      |
| Fr      | the subfolder is expanded. Report Framework    | 33842 /  |
| amework | hierarchy tree is displayed as depicted in the | PR 726   |
| Su      | screen shot below.                             |          |
| bfolder |                                                |          |
| Name    | Note: There is a possibility that this problem |          |
| Display | is generated when the Same user logs in        |          |
|         | multiple times and generates reports at the    |          |
|         | same time.                                     |          |
+---------+------------------------------------------------+----------+
| Reports | During test, it was discovered that if the     | SCR      |
| Fr      | user opens up the Reports Framework screen and | 32812    |
| amework | initiates running a report, then the user      |          |
| Error   | opens up an additional Reports Framework       |          |
| if Two  | screen to initiate additional reports, the     |          |
| Reports | system hangs . . .the mouse turns into an      |          |
| Fr      | hourglass and the report(s) never complete.    |          |
| amework | Only initiate reports from one Reports         |          |
| Screens | Framework at a time.                           |          |
| are     |                                                |          |
| Open    |                                                |          |
+---------+------------------------------------------------+----------+
| Reports | 1.  If the user selects multiple reports to be | PR 483   |
| Fr      |     run at a time, sometimes, not all of the   |          |
| amework |     reports in the selection complete          | PR 500   |
|         |     processing.                                |          |
|         |                                                | PR 503   |
|         | 2.  The Carrier LOV values on the Reports      |          |
|         |     Framework may contain extra values and     | PR 495/  |
|         |     will not match the list on the PTP Payload | SCR      |
|         |     Screen.                                    | 32916    |
|         |                                                |          |
|         | 3.  The Part Number and Part Name fields are   |          |
|         |     not the right size on the Reports          |          |
|         |     Framework screen when setting up the       |          |
|         |     report conditions for the Manifest and     |          |
|         |     Stowage Search report. These fields are of |          |
|         |     size 30 and should be size 80, which would |          |
|         |     match the size of the fields on the        |          |
|         |     Manifest and Stowage dataset screen.       |          |
|         |                                                |          |
|         | 4.  Sometimes when a report is selected via    |          |
|         |     double-clicking a Report from the Reports  |          |
|         |     Framework folder hierarchy, the user       |          |
|         |     receives this error: "FRM-92101: There the |          |
|         |     Forms Server during startup. This could    |          |
|         |     happen due to invalid configuration.       |          |
|         |     Please look into the web-server log file   |          |
|         |     for details." When the user clicks OK, the |          |
|         |     user is kicked out of the system**.**      |          |
+---------+------------------------------------------------+----------+
| Com     | The "Comp Reports" button available from       | Numerous |
| parison | Reports Framework supports the Manifest and    |          |
| Reports | Stowage data set. Numerous SCRs were written   |          |
| for M&S | against this functionality and the             |          |
| Data    | functionality is not delivered for the users.  |          |
| Set     |                                                |          |
+---------+------------------------------------------------+----------+
| Down    | If a user generates a report which results in  | SCR      |
| loading | no data, and an attempt to download it is      | 34023/   |
| Reports | made; the user will receive an error.          | PR 875   |
| with No |                                                |          |
| Data    | Workaround: Do not attempt to download reports |          |
|         | containing no data.                            |          |
+---------+------------------------------------------------+----------+
| **Ad    |                                                |          |
| Hoc     |                                                |          |
| Reports |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| D       | For the particular parameters below, the Ad    | SCR      |
| rawings | Hoc Drawing report did not generate any date.  | 34018/   |
| Ad Hoc  | The Report worked for other cases.             | PR 876   |
| Report  |                                                |          |
| d       | User: PL_RO                                    |          |
| isplays |                                                |          |
| no data | Payload: RMSTD                                 |          |
|         |                                                |          |
|         | Flight: FIN                                    |          |
|         |                                                |          |
|         | Category: AI                                   |          |
|         |                                                |          |
|         | Control Level: Final                           |          |
|         |                                                |          |
|         | Data on Drawings screen is seen by this user   |          |
|         | for the above criteria; however, the Ad Hoc    |          |
|         | report has no data in it.                      |          |
+---------+------------------------------------------------+----------+
| ICE Ad  | The ICE1 Ad Hoc report does not sort on the    | PR 510   |
| Hoc     | change package ID logically because the List   |          |
| Report  | of Values is required to be a character field. |          |
| Sort    | For example, package IDs of 221 and 241 are    |          |
|         | listed prior to IDs of 61 and 81 when sorting  |          |
|         | IDs in ascending order. The sort is based on   |          |
|         | character (LOV) rather than an expected        |          |
|         | numeric sort. The workaround is to use the     |          |
|         | "Package Id Sort" field. The user can select   |          |
|         | this field for their report, create a sort for |          |
|         | it then click the "Hidden" checkbox next to    |          |
|         | it. This will sort the report by this field    |          |
|         | but it will not display this field on the      |          |
|         | report.                                        |          |
+---------+------------------------------------------------+----------+
| Du      | If the user selects fields from the Ad Hoc     | SPR      |
| plicate | report templates for a data set or             | 70-03891 |
| Rows in | functionality, depending on the fields         |          |
| Ad Hoc  | selected, the report may produce duplicate     |          |
| Reports | rows of data. The user can select the "Hide    |          |
|         | Duplicate Rows" button in the Ad Hoc tool.     |          |
+---------+------------------------------------------------+----------+
| M       | When running the Manifest and Stowage Ad Hoc   |          |
| anifest | report template, the Flight Phase List of      |          |
| and     | Values (LOV) selector does not work. The       |          |
| Stowage | workaround is to type in ASCENT or DESCENT in  |          |
| Ad Hoc  | all upper case. This issue was discovered      |          |
| Report  | during final checkout on the Production        |          |
| Tem     | Server; it did not occur during Functional     |          |
| plate - | Testing on the Test Server. It is believed the |          |
| Flight  | LOV for this parameter is corrupted.           |          |
| Phase   |                                                |          |
| as a    |                                                |          |
| Pa      |                                                |          |
| rameter |                                                |          |
+---------+------------------------------------------------+----------+
| Cal     | See the following to update field decimal      | SPR      |
| culated | places in the Ad Hoc Reporting Tool.           | 7        |
| Ad Hoc  |                                                | 0-03907, |
| Report  |                                                | PR 460   |
| Fields  |                                                |          |
| not     | ![](                                           |          |
| Showing | media/image1.png){width="2.2368055555555557in" |          |
| D       | height="1.9548611111111112in"}                 |          |
| ecimals |                                                |          |
+---------+------------------------------------------------+----------+
| Oracle  | During the testing of the Ad Hoc Reporting     | SPR      |
| Dis     | Tool software, the Oracle Discoverer Ad Hoc    | 70-03845 |
| coverer | Tool toolbar disappeared on occasion after     |          |
| Ad Hoc  | entering parameters on a pre-defined Ad Hoc    |          |
| Tool    | Report template. The workaround is to log out  |          |
| Toolbar | and log back in.                               |          |
| Dis     |                                                |          |
| appears |                                                |          |
+---------+------------------------------------------------+----------+
| **      |                                                |          |
| Promote |                                                |          |
| /Demote |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| P       | During testing, the tester promoted KSC        | PR 854   |
| romote/ | Offline Processing Activities to the Submitted |          |
|         | control level and verified that the Payload    |          |
| Demote  | Processing control level was changed to        |          |
| Mixed   | "Mixed" on the Promote/Demote screen. When     |          |
| Control | Offline Processing Activities were demoted to  |          |
| Level   | the Private control level, the tester observed |          |
|         | that the KSC Data Set and Payload Processing   |          |
|         | current control level changed to "Submitted".  |          |
|         | This was unexpected; KSC Data Set level should |          |
|         | have remained at "Mixed" and Payload           |          |
|         | Processing was expected to change to "Private" |          |
|         | control levels.                                |          |
+---------+------------------------------------------------+----------+
| Payload | A user must have the ISS Integration Read      | PR 395   |
| Sel     | privilege enabled by the Team Manager from the |          |
| ections | Administration Screen in order to see the list |          |
| from    | of payloads on the PRO1 screen.                |          |
| the     |                                                |          |
| Promote |                                                |          |
| /Demote |                                                |          |
| Screen  |                                                |          |
+---------+------------------------------------------------+----------+
| **M     |                                                |          |
| anifest |                                                |          |
| and     |                                                |          |
| Stowage |                                                |          |
| Data    |                                                |          |
| Set     |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| MR      | The MR Loader for a CEF report does not        | SCR      |
| Loader  | display the correct from/to values when an ICE | 33926    |
| for CEF | change package includes multiple parent/child  |          |
| Report  | item parts. It appears that the \"To\" values  |          |
|         | from the last item part in the change package  |          |
|         | is used as the \"To\" value for any prior      |          |
|         | changes made to other item parts contained in  |          |
|         | the same change package. It also appears that  |          |
|         | this affects the Add/Delete rows since these   |          |
|         | rows displays the same values as the last      |          |
|         | Add/Delete item part. In this situation,       |          |
|         | changes to a serial number are also not shown  |          |
|         | and values for delta mass/volume up and down   |          |
|         | are not correct. The Parent/Child              |          |
|         | relationships are not displayed in the correct |          |
|         | order when there are at least two parents with |          |
|         | children under each (the Parent/Child          |          |
|         | reference to each other in columns A and B is  |          |
|         | displayed correctly).                          |          |
+---------+------------------------------------------------+----------+
| MR      | The MR Loader for a CEF report was not         | SCR      |
| Loader  | generated as expected by IE, DSM, and CM       | 34021/   |
| for CEF | users. With payload and flight at private      | PR 877   |
| Report  | control level, the expected blank report       |          |
| with    | failed to generate for users IE and DSM (the   |          |
| User    | report was indicated on the My Reports screen  |          |
| Logins  | as "terminated with error"). With the data at  |          |
|         | submitted and then draft control levels, the   |          |
|         | expected data-filled report again terminated   |          |
|         | for users IE, DSM and CM. Only Author was able |          |
|         | to generate report at private, submitted and   |          |
|         | draft control levels. CM was able to generate  |          |
|         | a blank report at private.                     |          |
+---------+------------------------------------------------+----------+
| Drawing | The Drawing Number field only accepts 40       |          |
| Number  | characters; the requirement is for a 60        |          |
| Field   | character field. Workaround: Try to limit      |          |
| Size on | Drawing Numbers to 40 characters or less.      |          |
| MAN1    |                                                |          |
| Screen  |                                                |          |
+---------+------------------------------------------------+----------+
| MAN1    | When new values for Carrier Compatibility are  | PR 630/  |
| Carrier | added on MAN2, the new values do not show up   | SCR      |
| Compat  | on the Carrier Compatibility LOV on the MAN 1  | 33627    |
| ibility | screen. No workaround exists.                  |          |
| Does    |                                                |          |
| not     |                                                |          |
| Update  |                                                |          |
+---------+------------------------------------------------+----------+
| Limi    | PDL users are allowed to map records within    | PR 633/  |
| tations | the same payload, flight and flight phase with | SCR      |
| when    | the following limitations:                     | 33629    |
| Mapping |                                                |          |
| Data    | -   The user cannot unmap the mapped record(s) |          |
| within  |                                                |          |
| the     | -   The user cannot delete a record without    |          |
| Same    |     deleting the associated mapped record(s)   |          |
| P       |                                                |          |
| ayload, | Workaround:                                    |          |
| Flight  |                                                |          |
| and     | -   Copy the record(s) to another location     |          |
| Flight  |     (Workspace or ISS Integration environment) |          |
| Phase   |                                                |          |
|         | -   Delete the source record(s) from the       |          |
|         |     original location                          |          |
|         |                                                |          |
|         | -   Copy the record(s) from the Workspace or   |          |
|         |     ISS Integration environment to the         |          |
|         |     original location)                         |          |
+---------+------------------------------------------------+----------+
| ICD     | The value of Record Identifier field displays  | SPR      |
| Input   | different values even when the report is       | 7        |
| Data    | generated with the same settings.              | 0-04017/ |
| Report  |                                                | PR 634   |
| Record  | Workaround: Disregard the value for Record     |          |
| Ide     | Identifier (no requirement exists to show this |          |
| ntifier | value).                                        |          |
| Display |                                                |          |
+---------+------------------------------------------------+----------+
| ICD     | The value of the Package ID number does not    | SPR      |
| Input   | display correctly. This only occurs when the   | 7        |
| Data    | selected report format is not the              | 0-04018/ |
| R       | Required/Optimal format (i.e., not Excel).     | PR 635   |
| eport - |                                                |          |
| From/To | Workaround: Select Report output in optimal    |          |
| Format  | format.                                        |          |
| (pdf)   |                                                |          |
+---------+------------------------------------------------+----------+
| MAN2    | MAN2 screen report does not show private data  | SPR      |
| Screen  | for DSM users. The MAN2 form had the same      | 7        |
| Report  | problem until just prior to EB6. The MAN2 form | 0-04003/ |
| Showing | was modified to access the database table      | PR 618   |
| Private | directly instead of via the view because the   |          |
| Data    | view implements the standard security model    |          |
| for DSM | but the MAN2 has different needs. Probably     |          |
|         | also occurs for IE users.                      |          |
|         |                                                |          |
|         | Work-around: Do a screen print.                |          |
+---------+------------------------------------------------+----------+
| PTP     | MAN2 screen sometimes does not show PTP Parent | SCR      |
| Parents | records. The MAN2 form does not display PTP    | 33503/   |
| on MAN2 | Parents records when the PTP Parent record     | PR 617   |
| Screen  | Carrier field contains a value that is not in  |          |
|         | the current Carrier list located at the bottom |          |
|         | of the MAN2 screen and is managed by the IEs   |          |
|         | and DSMs. This probably also occurs for the    |          |
|         | Sys_Subsys field.                              |          |
|         |                                                |          |
|         | Work-around: Manually ensure all Carrier       |          |
|         | values for all required PTP Parent records are |          |
|         | present in the Carrier list. The PDL Helpdesk  |          |
|         | can manually inspect PTP Parent records and    |          |
|         | add them to the table man_carrier_list.        |          |
+---------+------------------------------------------------+----------+
| MAN1 -  | Entered "1" into Actual Mass field, then       | SCR      |
| Control | entered ".9" into the Control Mass field,      | 33499/   |
| vs.     | tabbed out of the field, and then performed a  | PR 597   |
| Actual  | save. A pop-up message stating that the Actual |          |
| exceed  | exceeds Control did not pop-up. This seems to  |          |
| message | be the only field that this occurs on and it   |          |
| for     | seems to work okay with other values.          |          |
| Mass    | Workaround: Re-query the data the pop-up       |          |
| field   | message does occur for this field and the      |          |
|         | background goes red at that time.              |          |
+---------+------------------------------------------------+----------+
| CEF     | The PTP Parent Name, Mass Allocation, and      | SCR      |
| Con     | Volume Allocation fields located on the MAN2   | 33478/   |
| trolled | Screen allow the user (with write privileges)  | PR 601   |
| Fields  | to update the data without automatically       |          |
| on the  | capturing the change as an ICE CEF change. The |          |
| MAN2    | ICE logic was not integrated with the MAN      |          |
| Screen  | form. Therefore, the software prompts the user |          |
|         | that a CEF is required for the field change    |          |
|         | only, and the software accepts the updated     |          |
|         | value. Workaround is human coordination until  |          |
|         | corrected.                                     |          |
+---------+------------------------------------------------+----------+
| PTP     | If a change to an Item Part record exists in   | SCR      |
| Parent  | an ICE change package, the user is able to     | 33480/   |
| D       | delete the PTP Parent if the user has correct  | PR 610   |
| eletion | privileges. The software should automatically  |          |
|         | prevent the deletion of a record if there is a |          |
|         | pending change package against that record. No |          |
|         | workaround exists.                             |          |
+---------+------------------------------------------------+----------+
| Disapp  | Unexplained behavior when testing on the PC    | SCR      |
| ear-ing | and Macintosh was experienced. Workaround:     | 32815/   |
| M       | User can select Clear Form button from the     | PR 427   |
| anifest | horizontal Tool Bar and re-query the data. For |          |
| and     | some reason, the Carrier Compatibility data    |          |
| Stowage | does not re-query.                             |          |
| Data on |                                                |          |
| MAN1    |                                                |          |
| Form    |                                                |          |
+---------+------------------------------------------------+----------+
| MAN1 -- | When navigating from Core Admin screen to      | SCR      |
| Un      | Manifest and Stowage Data screen to verify     | 33112    |
| handled | custom configuration settings, the following   |          |
| ex      | message is displayed "WHEN-NEW-FORM-INSTANCE   | PR 369   |
| ception | trigger raised unhandled exception ORA-01403." |          |
| m       | After clicking OK to the message the MAN1      |          |
| essages | screen appeared. The message below appeared    |          |
|         | when selecting Data Manipulation Delete to     |          |
|         | delete Item Part record, "WHEN-BUTTON-PRESSED  |          |
|         | trigger raised unhandled exception ORA-00060.  |          |
|         | Clicked OK"                                    |          |
|         |                                                |          |
|         | Logged out and logged back in. Re-ran steps    |          |
|         | and Item Part record was deleted. Message 1403 |          |
|         | means no data found.; message 0060 is a        |          |
|         | deadlock waiting for resources. This is an     |          |
|         | intermittent problem. Related to PR 378.       |          |
+---------+------------------------------------------------+----------+
| Row     | The following reports sometimes generate       | Numerous |
| Dupl    | duplicate rows of output *even though the      |          |
| ication | database does not have duplicate rows*:        |          |
| in M&S  |                                                |          |
| Custom  | \(1\) MR Loader, (2) Pre-defined Manifest and  |          |
| Reports | Stowage Fields, (3)Trash Report by Increment,  |          |
|         | (4)Trash Report for Disposal Flight/ (5)       |          |
|         | Disposal Increment, (6) Engineering            |          |
|         | Configuration List (ECL), (7) Standard Orbiter |          |
|         | Crew Compartment ICA                           |          |
|         |                                                |          |
|         | These reports are output as Excel files        |          |
|         | (optimal format). The user may delete          |          |
|         | duplicate rows in the Excel output file.       |          |
+---------+------------------------------------------------+----------+
| M       | During test, three part number records existed | SCR      |
| anifest | for a PTP Parent. When the cursor was on one   | 32815    |
| and     | of the part number records, and the user       |          |
| Stowage | clicked the PTP Print field in the row under   |          |
| MAN1    | the Generic PTP Parent, the part number        |          |
| Part    | records disappeared. The row under the Generic |          |
| Number  | PTP Parent was clicked and the part number     |          |
| Records | records were visible again.                    |          |
| So      |                                                |          |
| metimes |                                                |          |
| Di      |                                                |          |
| sappear |                                                |          |
+---------+------------------------------------------------+----------+
| MAN 1   | The following error message was noted during   | SCR      |
| Error   | 16.1 testing: FRM-40654: Record has been       | 33477/   |
| Message | updated by another user. Re-query to see       | PR 572   |
|         | change. ORA-01403 no data found. The user can  |          |
|         | select "Ok" and continue without impact.       |          |
+---------+------------------------------------------------+----------+
| Com     | The "Comp Reports" button available from       | Numerous |
| parison | Reports Framework supports the Manifest and    |          |
| Reports | Stowage data set. Numerous SCRs were written   |          |
| for M&S | against this functionality and the             |          |
| Data    | functionality is not delivered for the users.  |          |
| Set     |                                                |          |
+---------+------------------------------------------------+----------+
| Working | If a payload exists in the ISS Integration     |          |
| M&S     | Environment, and the M&S data for Ascent and   |          |
| with    | Descent phases is at differing Control Levels, |          |
| Data    | data manipulation requests from the PDL        |          |
| Sets    | Desktop environment may be denied because the  |          |
| having  | software cannot differentiate between ascent   |          |
| Mixed   | and descent phase data from the PDL Desktop.   |          |
| Control | However, if the user maneuvers to the M&S Main |          |
| Levels  | screen (MAN1) and selects the proper flight    |          |
|         | phase (ascent or descent), data manipulation   |          |
|         | actions are permitted if the user has          |          |
|         | appropriate data access privileges at the      |          |
|         | existing data control levels.                  |          |
+---------+------------------------------------------------+----------+
| The M&S | There is one M&S data set Ad Hoc Report        |          |
| Ad Hoc  | Template defined for the users. It contains    |          |
| Report  | all of the fields and has the parameters set   |          |
| T       | up just like the MAN1 screen.  The template    |          |
| emplate | can be updated by users to remove unwanted     |          |
|         | fields, change sorts, add/remove parameters    |          |
|         | and then saved as the users own report.        |          |
|         |                                                |          |
|         | There is one data field not included in this   |          |
|         | pre-built template that does exist on the MAN1 |          |
|         | screen.  This field is the Carrier             |          |
|         | Compatibility field, and is not included on    |          |
|         | the template because of the structure of the   |          |
|         | data in the M&S Tables.  When this field is    |          |
|         | combined on a report with any of the fields    |          |
|         | from the IMS/Barcode folder an error will      |          |
|         | occur.  Only one or the other can exist on a   |          |
|         | report at a time without causing an error      |          |
|         | called a "fan-trap" error.  The reason for     |          |
|         | this is because an item part can have several  |          |
|         | barcode/serial numbers and it can also have an |          |
|         | unrelated number of carrier certifications,    |          |
|         | when combining this information into one       |          |
|         | report, you will get one line of data for      |          |
|         | every barcode/serial number \*AND\* one line   |          |
|         | of data for every carrier certification number |          |
|         | causing an incorrect number of records on the  |          |
|         | report.                                        |          |
|         |                                                |          |
|         | If it is imperative that both of these appear  |          |
|         | on a report together, there is a way to work   |          |
|         | around the error by disabling the fan-trap     |          |
|         | detection.  To do this, select the options     |          |
|         | button from the edit workbook window, select   |          |
|         | the advanced tab and click the check box to    |          |
|         | disable fan-trap detection.                    |          |
+---------+------------------------------------------------+----------+
| **D     |                                                |          |
| rawings |                                                |          |
| Data    |                                                |          |
| Set     |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| D       | For the particular parameters below, the Ad    | SCR      |
| rawings | Hoc Drawing report did not generate any date.  | 34018/   |
| Ad Hoc  | The Report worked for other cases.             | PR 876   |
| Report  |                                                |          |
| d       | User: PL_RO                                    |          |
| isplays |                                                |          |
| no data | Payload: RMSTD                                 |          |
|         |                                                |          |
|         | Flight: FIN                                    |          |
|         |                                                |          |
|         | Category: AI                                   |          |
|         |                                                |          |
|         | Control Level: Final                           |          |
|         |                                                |          |
|         | Data on Drawings screen is seen by this user   |          |
|         | for the above criteria; however, the Ad Hoc    |          |
|         | report has no data in it.                      |          |
+---------+------------------------------------------------+----------+
| User    | In order to access the Bench Review Tab on the |          |
| Access  | Drawings screen, the user must be a member of  |          |
| to      | the Bench Review Team. Contact the PDL Help    |          |
| D       | Desk.                                          |          |
| rawings |                                                |          |
| Bench   |                                                |          |
| Review  |                                                |          |
| Tab     |                                                |          |
+---------+------------------------------------------------+----------+
| Viewing | The user cannot view Excel files by selecting  |          |
| Excel   | the Drawings View button. If the user          |          |
| Files   | downloads the Excel file to their local        |          |
|         | computer, it can be viewed.                    |          |
+---------+------------------------------------------------+----------+
| E       | When the user enters and event title, revision | SCR      |
| ntering | and uploads and image and saves, and then      | 33876/   |
| Drawing | enters an identical second event title and     | PR 840   |
| Data    | revision and saves, the user is informed that  |          |
|         | the image and revision already exist and a new |          |
|         | revision number must be entered. The user      |          |
|         | updates the revision, then pushes the upload   |          |
|         | button. The image is uploaded to the first     |          |
|         | record, even though the second record is       |          |
|         | select and the second record is the record     |          |
|         | that was being updated. Workaround: the user   |          |
|         | should select Save after entering and          |          |
|         | uploading to each record.                      |          |
+---------+------------------------------------------------+----------+
| D       | To delete a Drawing record, the user must      |          |
| eleting | first delete the image record, SAVE, then      |          |
| Drawing | click the Drawing record, delete it, then SAVE |          |
| Data    | again.                                         |          |
+---------+------------------------------------------------+----------+
| Drawing | On the new DRW1 Drawing Screen, the user       |          |
| Data    | should verify the Drawing Category             |          |
| Set --  | Applicability for each drawer record prior to  |          |
| C       | copying Workset or Shell data to other         |          |
| ategory | Worksets or Shells. For later use, if the      |          |
| Applic  | Drawing Category Applicability is modified by  |          |
| ability | the user, the category update is only          |          |
| Check   | applicable to the currently selected Workset   |          |
| Boxes   | or Shell. Mapped Worksets/Shells do not        |          |
|         | reflect the category selection change.         |          |
+---------+------------------------------------------------+----------+
| Ma      | The Oracle Web Utility functionality that is   | PR 381/  |
| cintosh | used for File Transfers does not operate with  | SPR      |
| and     | Macintosh computers. This means that the file  | 70-03890 |
| File    | transfer functionality to download reports     |          |
| Tr      | from the Reports Framework \> My Reports       |          |
| ansfers | location, downloading Drawings, and            |          |
|         | downloading C&DH ASCII Reports (coming in PDL  |          |
|         | Release 17.0) generate an error. An Oracle     |          |
|         | Technical Assistance Request (TAR) -           |          |
|         | 4793283.993 - Unable to use WebUtil            |          |
|         | FileTransfer with Mac WUC-015 has been opened. |          |
|         | Workaround for Report Generation: When running |          |
|         | a report, display it after completion (a new   |          |
|         | browser window is opened); then the user can   |          |
|         | save the file to their Macintosh hard drive    |          |
|         | from the browser window. Workaround for        |          |
|         | Drawing Downloads does not exist. Call the PDL |          |
|         | Helpdesk.                                      |          |
+---------+------------------------------------------------+----------+
| **KSC   |                                                |          |
| Support |                                                |          |
| Data    |                                                |          |
| Set     |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| KSC     | -   When placing the maximum characters in     | SCR      |
| Su      |     each data field, the report contains blank | 34019/   |
| pport - |     pages for at the beginning of the          | PR 866   |
| Whole   |     Facilities, Equipment, Commodities and     |          |
| Dataset |     Services sections. Each page contains the  |          |
| Report  |     header and footer information, but no data |          |
|         |     appears on the page. The correct data for  |          |
|         |     each section begins on the following page. |          |
|         |                                                |          |
|         | -   The report also split the numbers          |          |
|         |     contained in the Launch To field. The      |          |
|         |     value of R+220 was split with "R+22" on    |          |
|         |     the first line and the remaining "0"       |          |
|         |     appeared on the second row (under Services |          |
|         |     section). Appears that the 220 should be   |          |
|         |     together on the first or second row (the   |          |
|         |     value 220 all appeared on first row in     |          |
|         |     other parts of this report).               |          |
|         |                                                |          |
|         | -   Under the KSC-Required Customer            |          |
|         |     Deliverable Documents section, the word    |          |
|         |     "need" was truncated on the last line in   |          |
|         |     the Template Submittal column. The field   |          |
|         |     should have read "up to 45 days prior to   |          |
|         |     need".                                     |          |
+---------+------------------------------------------------+----------+
| Deliv   | The Deliverables Screen is blank the first     |          |
| erables | time the screen is accessed after the payload  |          |
| Screen  | is manifested. The user must hit the execute   |          |
| Data    | query button to display the template as shown  |          |
| Query   | if Figure 14.5-1. The next time the screen is  |          |
|         | accessed the template displays correctly as    |          |
|         | shown in Figure 14.5-2.                        |          |
+---------+------------------------------------------------+----------+
| **KSC   |                                                |          |
| Te      |                                                |          |
| chnical |                                                |          |
| Data    |                                                |          |
| Set     |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| KST -   | The KST OMRS Report is missing the last two    | SCR      |
| OMRS    | characters from A: Effectivity Code when this  | 34015/   |
| Report  | field is maxed out in the form.                | PR 873   |
+---------+------------------------------------------------+----------+
| KST -   | The KST Dataset on the TGHR Table Entry screen | SCR      |
| TGHR    | needs the insertion of a record changed to     | 34014/   |
| Table   | insert at the end of existing records instead  | PR 872   |
| Entry   | of between existing records. When inserting a  |          |
| Insert  | record in PDL 17.0 there is sometimes          |          |
|         | duplication of the No. (P1, P2, etc.).         |          |
|         | Workaround: Put cursor on last record before   |          |
|         | inserting a new record.                        |          |
+---------+------------------------------------------------+----------+
| KST     | The user will have to select the "Utilities"   |          |
| Data    | option on the main menu and then select the    |          |
| Copy    | "PDL Desktop" function in order to copy\*\*    |          |
|         | the whole dataset records.                     |          |
|         |                                                |          |
|         | \*\*The copy for KSC Technical is unique in    |          |
|         | that the user must go back through the newly   |          |
|         | copied screens to reclick the Requirements     |          |
|         | Subsets checkboxes for the 3 OMRS screens and  |          |
|         | the Notes fields checkboxes for the Time       |          |
|         | Critical Ground Handling Requirements screens. |          |
|         | These relationships were not able to be        |          |
|         | copied.                                        |          |
+---------+------------------------------------------------+----------+
| KST     | On the KSC Technical dataset screen, after the | SCR      |
| Control | user presses Clear Form and queries a          | 33867/   |
| Level   | payload/flight option, the Control Level field | PR 851   |
| Display | at the top of the form is blank. Workaround:   |          |
|         | Click the Revert icon and the Control Level    |          |
|         | will display.                                  |          |
+---------+------------------------------------------------+----------+
| KST     | The Payload Name in the header of the KST      |          |
| Whole   | Whole Data Set report is incorrect, but the    |          |
| Data    | data is correct for the payload/flight         |          |
| Set     | selected in the Reports Framework.             |          |
| Report  |                                                |          |
+---------+------------------------------------------------+----------+
| *       |                                                |          |
| *Safety |                                                |          |
| Data    |                                                |          |
| Set     |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| S       | The "Element Acronym" and "Element Name"       | SCR      |
| afety - | fields are 'gray' fields in the following      | 33990/   |
| Write   | screens: FDS, FDS Pics, Haz Cont Pics, Crew    | PR 859   |
| access  | Procs, Crew Train, Flt Rules, PL Comp Train,   |          |
| to gray | Tox, Tox Pics, MHA and Haz Cont.               |          |
| field   |                                                |          |
| \"      | These fields should be read only data          |          |
| Element | auto-populated from the Element screen.        |          |
| Ac      | However, the toolbar Delete Record and Insert  |          |
| ronym\" | Record are enabled when the cursor is in these |          |
|         | fields, allowing users with write privilege to |          |
|         | delete the record, and in some cases, allowing |          |
|         | them to insert a record.                       |          |
|         |                                                |          |
|         | Workaround: Advise users not to modify these   |          |
|         | fields.                                        |          |
+---------+------------------------------------------------+----------+
| S       | The "Report Number" field is a 'gray' field in | SCR      |
| afety - | the following screens: Haz Cont Pics, Crew     | 33991/   |
| Write   | Procs, Crew Train (SCR 33827 reports problem   | PR 860   |
| access  | on this screen only), Flt Rules andPL Comp     |          |
| to gray | Train.                                         |          |
| field   |                                                |          |
| \       | These fields should be read only data          |          |
| "Report | auto-populated from the Haz Cont screen.       |          |
| N       | However, the toolbar Delete Record and Insert  |          |
| umber\" | Record are enabled when the cursor is in these |          |
|         | fields, allowing users with write privilege to |          |
|         | delete the record or displaying error messages |          |
|         | when trying to insert.                         |          |
|         |                                                |          |
|         | Workaround: Advise users not to modify this    |          |
|         | field.                                         |          |
+---------+------------------------------------------------+----------+
| S       | The scrollbar for the "Report Number" and      | SCR      |
| afety - | "Control Number" fields does not work on the   | 33992/   |
| Sc      | PL Comp Train.                                 | PR 861   |
| rollbar |                                                |          |
|         | Workaround: The user must use the keyboard     |          |
|         | arrow down/up keys or the toolbar First,       |          |
|         | Previous, Next, and Last Record buttons to     |          |
|         | navigate through the records.                  |          |
+---------+------------------------------------------------+----------+
| S       | The Tox Pics screen has the incorrect screen   | SCR      |
| afety - | title. The title is "SAF4 -- Fire Detection    | 33993/   |
| Tox     | and Suppression". The title should be "SAFx -- | PR 863   |
| Pics:   | Toxicology Pictures".                          |          |
| Screen  |                                                |          |
| title   |                                                |          |
| and tab |                                                |          |
| label   |                                                |          |
| text    |                                                |          |
+---------+------------------------------------------------+----------+
| Safety  | In the Workspace Common Navigation Area (CNA)  | SCR      |
| -- Team | at the top of each Safety screen, the Team     | 33994/   |
| Wo      | Workspace field displays the Team Name in some | PR 864   |
| rkspace | screens and the Team ID in other screens.      |          |
| CNA     |                                                |          |
+---------+------------------------------------------------+----------+
| Safety  | The tester was entering data for EXPRESS Rack  | SCR      |
| --      | on flight 13P. The usser saved data and then   | 33995/   |
| Error   | changed the flight to 7S. The following        | PR 865   |
| when    | message appeared: "FRM-40738: Argument 1 to    |          |
| c       | builtin FIND_TABPAGE cannot be null.           |          |
| hanging | ORA-01403: no data found." The flight changed  |          |
| Flights | to 7S, but the data on the screen was still    |          |
| in CNA  | the data for flight 13P.                       |          |
|         |                                                |          |
|         | Workaround: Click on another screen (i.e. Crew |          |
|         | Train) and then click back on Flt Rules to     |          |
|         | display 7S data (using Clear Form did not      |          |
|         | work; more error messages appeared).           |          |
+---------+------------------------------------------------+----------+
| Safety  | Users should have write access to the \'Safety | SCR      |
| Cert    | Cert\' screen depending on their individual    | 33823/   |
| Tab     | ISS and Workspace Write privilege. During 17.0 | PR 719   |
|         | testing, it was determined that write          |          |
|         | privilege to this screen was based on the      |          |
|         | user\'s Team Member flag. If the Team Member   |          |
|         | flag is checked, the user will have write      |          |
|         | access to the screen, regardless of their ISS  |          |
|         | and Workspace privileges. If the Team Member   |          |
|         | flag is not checked, the user will not have    |          |
|         | write access to the screen, regardless of      |          |
|         | their ISS and Workspace privileges. In         |          |
|         | addition, when the Team\'s Write flag for the  |          |
|         | Safety dataset is not checked, and the user\'s |          |
|         | Team Member flag is checked, the user is able  |          |
|         | to write to this screen.\                      |          |
|         | \                                              |          |
|         | Per requirements, the only screen that should  |          |
|         | grant/prohibit Write access based on the Team  |          |
|         | Member flag is the \'Con Log\' screen.         |          |
+---------+------------------------------------------------+----------+
| Copy    | The Copy functionality was not implemented in  | SCR      |
| functi  | 17.0 for the Safety dataset however DMM tool   | 33825    |
| onality | bar buttons are enabled in WSP1 and ISS1 when  |          |
| not     | selecting SAF in a Workset or Shell. The       |          |
| de      | buttons that are enabled are Copy, Paste,      |          |
| livered | Delete, and Unmap. The user can press these    |          |
| for the | buttons as if performing the function, and no  |          |
| Safety  | error message is displayed, but the software   |          |
| dataset | functions are not actually performed (i.e. no  |          |
|         | data is actually copied).                      |          |
+---------+------------------------------------------------+----------+
| S       | Tester selected \"Payload Hazard Control       | SCR      |
| afety - | Matrix - All Payloads\" reports. Selected      | 33828/   |
| PHCM    | Flight UNMANIFESTED1. Pressed Run Selected     | PR 788   |
| Report: | Reports. The report opened in Adobe Reader 6.0 |          |
| Error   | in Internet Explorer browser. When the mouse   |          |
| c       | was placed over the \"Flight: Master\" column, |          |
| licking | the mouse pointer turns into a \"hand with the |          |
| in the  | pointer finger\" (it\'s called Link Select).   |          |
| report  | The tester clicked in the \"Flight: Master\"   |          |
|         | column (to move the page up), and another      |          |
|         | screen opened in the IE window. The screen     |          |
|         | says, \"Oracle Reports...Error...No such       |          |
|         | command (BLANKPAGES=NO)\". When tester pressed |          |
|         | the OK button, the report opens up again.      |          |
+---------+------------------------------------------------+----------+
| S       | The \"Associated Hazard\" fields (\"Report     | SCR      |
| afety - | Number\" and \"Control Number\") are           | 33829/   |
| MHA     | grayed-out. However, they were not grayed-out  | PRs 796, |
| tab:    | in 15.3 Production. Even though users cannot   | 828      |
| \"Ass   | type data into these fields, users can double  |          |
| ociated | click the fields to get an LOV and make a      |          |
| H       | selection. The functionality of the fields is  |          |
| azard\" | correct, the only problem is that they         |          |
| fields  | background color of the fields is gray instead |          |
| are     | of white. Also, the screen does not allow the  |          |
| gray    | user to click on the \"Element Name\" field to |          |
|         | see data for other Elements. The user must     |          |
|         | click on the \"Element Acronym\" field. All    |          |
|         | other screens allow users to click the         |          |
|         | \"Element Name\" field to see data for other   |          |
|         | Elements.                                      |          |
+---------+------------------------------------------------+----------+
| S       | The data on the Con Log screen and the Safety  | SCR      |
| afety - | Cert screen does not clear when you switch     | 33832/   |
| Con Log | between the ISS and the Workspace, where the   | PR 834   |
| and     | latter does not have selected parameters.\     |          |
| Safety  | Workaround: Select the Payload/Flight or       |          |
| sw      | Workspace/Workset to query the data. For       |          |
| itching | example, if the user selected a Payload/Flight |          |
| between | to view ISS data, and then the user clicked on |          |
| ISS and | the Workspace tab, the ISS data will remain on |          |
| Wo      | the screen. Select the Workspace/Workset of    |          |
| rkspace | the data the user wants to view and the data   |          |
|         | will be displayed on the screen.               |          |
+---------+------------------------------------------------+----------+
| S       | In the Element screen the tester selected      | SCR      |
| afety - | EXPRESS Rack / 13P. When switching to          | 33835    |
| Flt     | Workspace SAFETY TEAM / SAF-WS-1, the tester   |          |
| Rules,  | saw all appropriate data. Then the tester      |          |
| PL Comp | navigated to Flt Rules screen and received a   |          |
| Train:  | \"data access denied\" message. The tester     |          |
| get     | clicked on PL Comp Train, and received the     |          |
| data    | same message. Workaround: In order to see the  |          |
| access  | data, the user must click on Haz Cont Pics and |          |
| error   | select EXPRESS Rack / 13P in ISS. Then, when   |          |
| message | the user clicks on Flt Rules and PL Comp Train |          |
|         | all appropriate data is present.               |          |
+---------+------------------------------------------------+----------+
| S       | In the Crew Train screen, the user is supposed | SCR      |
| afety - | to be able to double-click the \"First Name\"  | 33837    |
| Crew    | or the \"Last Name\" field to see a list of    |          |
| Train   | available crew members. This list is based on  |          |
| and PL  | what was entered in the Flight/Crew            |          |
| Comp    | Maintenance screen. However, in the Workspace  |          |
| Train   | tab, double-clicking these fields sometimes    |          |
| tabs:   | does not display a list even though data has   |          |
| Crew    | been entered in the Flight/Crew Maintenance    |          |
| Member  | screen. When it does display a list, the data  |          |
| LOVs    | in the list contains ISS data. When the user   |          |
|         | is in the ISS Integration tab, the list will   |          |
|         | display Workset and ISS data. This is not      |          |
|         | correct behavior; the list should display      |          |
|         | Workset only or ISS only data, depending if    |          |
|         | you are on the Workspace or ISS Integration    |          |
|         | tab.\                                          |          |
|         | Workaround for Crew Train:\                    |          |
|         | - In the ISS Integration, it seems that one    |          |
|         | can see the data needed, but will see extra    |          |
|         | data too; the user will have to know which     |          |
|         | data is ISS vs Workspace data.\                |          |
|         | - In the Workspace, you cannot see all the     |          |
|         | Workspace data; there doesn\'t seem to be a    |          |
|         | workaround.\                                   |          |
|         | \                                              |          |
|         | The PL Comp Train screen works similar to the  |          |
|         | Crew Train screen in that double-clicking the  |          |
|         | \"First Name\" and \"Last Name\" fields will   |          |
|         | display the list of crew members that contains |          |
|         | ISS and Workspace data, regardless of which    |          |
|         | tab (ISS Integration or Workspace) is          |          |
|         | selected. Also, on the PL Comp Train tab, the  |          |
|         | user can press the \"Insert Entire Crew\"      |          |
|         | button, and all of the crew members entered in |          |
|         | the Flight/Crew Maintenance tab will be        |          |
|         | inserted on this screen, but it seems to be    |          |
|         | inserting ISS and Workspace data, regardless   |          |
|         | of what tab (ISS Integration or Workspace) is  |          |
|         | selected.\                                     |          |
|         | \                                              |          |
|         | Workaround for PL Comp Train:\                 |          |
|         | It seems that pressing the \"Insert Entire     |          |
|         | Crew\" button will insert all Workspace and    |          |
|         | ISS data, regardless of what tab (ISS          |          |
|         | Integration or Workspace); users can delete    |          |
|         | the records they don\'t want, but they will    |          |
|         | have to know which belong to ISS vs Workspace. |          |
+---------+------------------------------------------------+----------+
| **C&DH  |                                                |          |
| Data    |                                                |          |
| Set     |                                                |          |
| I       |                                                |          |
| ssues** |                                                |          |
+---------+------------------------------------------------+----------+
| C&DH    | If help is selected from the C&DH Main Menu,   | SCR      |
| Main    | the C&DH Section of the PDL User's Guide       | 34009/   |
| Menu    | should be displayed. Currently, the PSCP       | PR 858   |
| Help    | website is returned instead.                   |          |
| Option  |                                                |          |
|         | Workaround: Access the PDL User's Guide from   |          |
|         | the PDL web site.                              |          |
+---------+------------------------------------------------+----------+
| PSIV    | If the user is logged in as an ISS read only   | SCR      |
| Reports | user, and C&DH data is above the Private       | 34017/   |
| contain | Control Level, the following reports contain   | PR 862   |
| no data | no data when generated:                        |          |
| for ISS |                                                |          |
| Re      | -   PSIV Commands                              |          |
| ad-Only |                                                |          |
| Users   | -   PSIV Files                                 |          |
|         |                                                |          |
|         | -   PSIV Limits                                |          |
|         |                                                |          |
|         | -   PSIV Payloads                              |          |
|         |                                                |          |
|         | The data does exist because IE and DSM users   |          |
|         | can generate the same reports with valid data. |          |
|         | Workaround: Use a different login when         |          |
|         | generating these reports.                      |          |
+---------+------------------------------------------------+----------+
| Pr      | Records in the CDH_TL_BUNDLE table do not      | SCR      |
| omotion | promote correctly. If there is a record in     | 34010/   |
| of      | that table for a sub-element being promoted,   | PR 867   |
| records | the promotion will not complete successfully.  |          |
| in the  | Workaround: Call the PDL Helpdesk.             |          |
| CDH_TL  |                                                |          |
| _BUNDLE |                                                |          |
| table   |                                                |          |
+---------+------------------------------------------------+----------+
| Error   | When initiating C&DH custom reports for        | SCR      |
| when    | screens A-3, A-4 and A-5 and selecting the     | 34012/   |
| Se      | CPCG_V payload on the Reports Framework, the   | PR 868   |
| lecting | tester received error message "FRM-40734: WHEN |          |
| C&DH    | BUTTON PRESSED trigger raised unhandled        |          |
| Reports | exception ORA:01422. ORA-01422: exact fetch    |          |
| from    | returns more than requested number of rows".   |          |
| the     | Workaround: Click Ok, enter all report setup   |          |
| Reports | parameter, and the report will generate fine.  |          |
| Fr      |                                                |          |
| amework |                                                |          |
+---------+------------------------------------------------+----------+
| C&DH    | -   Inconsistency in the sort order for        | SCR      |
| Data    |     A-15\\Linear screen report (pdf) and       | 32051,   |
| Set     |     custom reports (pdf and ASCII) Table A-15, | SCR      |
| Open    |     C&DH, screen A-44. Records on the screen   | 31925,   |
| Issues  |     report generated for screen A-15/Linear    |          |
| and     |     are sorted differently than the sorting on | SCR      |
| Known   |     the actual screen and on the custom report | 31983,   |
| Limi    |     generated from screen A-44.                | SCR      |
| tations |                                                | 31922    |
|         | -   The majority of LOVs on most of the        |          |
|         |     screens are partially visible. Command     |          |
|         |     buttons are not accessible. User must drag |          |
|         |     the LOV box upward.                        |          |
|         |                                                |          |
|         | -   Oracle 10g software behaves differently    |          |
|         |     for ASCII reports that contains no data.   |          |
|         |     If a report is generated for a screen that |          |
|         |     has no data and an ASCII report is         |          |
|         |     generated, the message "Your report        |          |
|         |     "\_\_\_\_\_\_\_\_\_.txt contains no data"  |          |
|         |     is received. On Oracle10g system, report   |          |
|         |     is created and then given a name. User     |          |
|         |     must perform multiple steps to find out    |          |
|         |     that the report generated has no data.     |          |
|         |                                                |          |
|         | -   When trying to generate a comparison       |          |
|         |     report for screen A-2 RACK DATA for        |          |
|         |     flights 12A.1 and 12A, received the        |          |
|         |     message "here diff". The correct should be |          |
|         |     "Under Development".                       |          |
+---------+------------------------------------------------+----------+
| Report  | When navigating to screen A-28/TLM             | SCR      |
| Option  | Verification and data is populated, the Report | 33844/   |
| on C&DH | option, POIC/Remote, and Field Def are grayed  | PR 728   |
| Main    | out. The Execute button is active. The Enter   |          |
| Menu is | button should be active, not Execute button.   |          |
| i       | This problem does exist on new but not on old  |          |
| nactive | production.                                    |          |
| on      |                                                |          |
| screen  |                                                |          |
| A-28    |                                                |          |
| (Te     |                                                |          |
| lemetry |                                                |          |
| Ve      |                                                |          |
| rifier) |                                                |          |
+---------+------------------------------------------------+----------+
| **      |                                                |          |
| General |                                                |          |
| Record  |                                                |          |
| Manip   |                                                |          |
| ulation |                                                |          |
| Tips**  |                                                |          |
+---------+------------------------------------------------+----------+
| Adding  | Insert Record Functionality. If a user enters  | SCR      |
| Records | data for a record, fails to enter data for a   | 32798    |
| with    | required field and attempts to save the        |          |
| R       | record - they will get an error.               |          |
| equired |                                                |          |
| Data    | Normal/ Standard Behavior - There are several  |          |
|         | different constraints that can be defined for  |          |
|         | a column. The NOT NULL constraint is discussed |          |
|         | here. Defining a column as NOT NULL means that |          |
|         | the field must have a value. When creating     |          |
|         | records through a form, if the form does not   |          |
|         | check, the database will check for a value. If |          |
|         | there is no value being input for a NOT NULL   |          |
|         | field, the record will not save, an error      |          |
|         | message will inform the user that the record   |          |
|         | can not be inserted. On the Help Menu, select  |          |
|         | Display Error. The message that is displayed   |          |
|         | will show you which fields are required to     |          |
|         | have a value. If the error message states that |          |
|         | the record cannot be inserted, after clearing  |          |
|         | the message, either insert a value into the    |          |
|         | required field(s), or press Delete Record      |          |
|         | (clears the partial record and allows the user |          |
|         | to continue to work). Pressing Clear Form will |          |
|         | not clear the partial record.                  |          |
+---------+------------------------------------------------+----------+
| In      | If a user inserts a record, then attempts to   | SCR      |
| serting | delete it before the record is saved, Oracle   | 31999    |
| and     | will generate an error. The workaround is to   |          |
| D       | select the Clear Form button on the horizontal |          |
| eleting | tool bar to remove the record data. Clear Form |          |
| a       | is also on the Menu under File selection.      |          |
| Record  |                                                |          |
+---------+------------------------------------------------+----------+