Notes/Domino Fix List
 |  |
| SPR # YJIO6PM9XP | Fixed in 7.0.2 release |  |
Product Area: Client Technical Area: Access for SAP Solutions Platform: Cross Platform
SPR# YJIO6PM9XP - Fixed a problem where Quick Time Entry would not appear in the Report Time wizard. A workaround to this problem is as follows. After you use the Quick Entry dialog you can click the Back button (taking you back to Step 1) and then click the Next button (returning you to Step 2). If you do this, the new Time Entry is displayed in the table. See Technote No. 1237788 for more information.
Technote Number: 1237788
Problem:
This issue has been reported to Quality Engineering as SPR# YJIO6PM9XP and was
fixed in NaSs 7.0.2.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
Prior to 7.0.2, there are two workarounds for this problem. One involves
changing code, and one does not.
Workaround #1:
After you use the Quick Entry dialog, click the Back button (taking you back to
Step 1). Then, click the Next button (returning you to Step 2). After doing
this, the new Time Entry is displayed in the table.
Workaround #2:
If you are adventurous, you can implement the following code. NOTE: MAKING THIS
CHANGE IS NOT SUPPORTED BY IBM. It is NOT recommended that you make this change
if you are not proficient in LotusScript or if you do not feel uncomfortable
making changes to production template code:
Open Domino Designer.
Make a backup copy of the agent (ReportTimeWizard.AddTime).
Open the original version of the (ReportTimeWizard.AddTime) agent.
Go into the Initialize event. At or around line 12 you should see the following
code:
"If retflg = False Then Exit Sub". It is located immediately below the
DialogBox call.
Comment out the line listed in step 4 and add the following code right below it:
On Error 4091 Goto getOut
Set trdoc = thisdb.GetDocumentByUnID(timedoc.UniversalID)
If trdoc Is Nothing Then
Exit Sub
Else
Set timedoc = trdoc
End If
On Error 4091 Goto errHandler
Save and close the agent.
Test.
Supporting Information:
This bug is caused by unusual behavior from a dialog box when an
@Command([FileSave]) is called in the OK button. @Command([FileSave]) is used
in the OK button to cause the validation formulas to execute, as well as to
cause the needed code in the QuerySave and PostSave events to execute. However,
when @Command([FileSave]) is used in the OK button it causes two things to
happen:
The return value of the NotesUIWorkspace.DialogBox method will always be False,
indicating the dialog was canceled when in fact it was not.
The values entered into the dialog are written immediately to disk, and the
in-memory version of the document is NOT updated with the fields from the
dialog box. So, the NotesDocument object is not in sync with the on-disk
version of the document.
Therefore, the document is successfully and correctly created in the database,
but because the DialogBox method returns a False, the Table in the Report Time
wizard, Step 2, is not updated and that document will not be submitted to SAP. More >
Last Modified on 12/01/2011
Go back
|