LO76131: THE WELCOME PAGE SET BY POLICY OVERRIDDEN BY THE ONE FROM THE LOCATION DOCUMENT

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as unreproducible.

Error description

  • 1) The default welcome page can be dependent on the location:
    
    From my test I define 2 new welcome pages:
    
    One with the name "YuminPage1" created when the location is
    online.
    I create a new location called: Yumin_Online. While on this
    location, I create a new page called "Yumin_Online Page".
    
    In normal case, when I switch locations between online and
    Yumin_Online, the welcome page will not be changed accordingly.
    
    But after you change the location document, close down the
    bookmark.nsf and reopen it, then I'm able to see the home page
    when it was defined on that location.
    
    So the trick is to reopen bookmark.nsf.
    
    2) When I open Customer's bookmark.nsf via NotesPeek, I
    understand now what Customer means about the profile/location.
    
    See below screenshot from my bookmark.nsf: (the current page is
    basics +location is online)
    
    :
    
    in Profiles >> currentlayout, I only focus on 3 fields:
    
    1) $Onlinexxx which means the default page for the location
    "online",
    2) the CurrentLayoutKey field decides the current welcome page
    3) $23E2... which is probably the page pulled from the desktop
    policy
    
    Comparing the above screenshot with Customer's one:
    
    
    
    Customer realises the cause of the issue (default welcome page
    cannot be set via policy, though it's listed in the drop down
    list already) is:
    
    The value of $Office (Network)9A2 overrides the value of
    $23E2... which is probably the page pulled from the desktop
    policy
    
    Now it comes up customer's question:
    Do we have any way (or simple code) that can remove the $Office
    (Network)9A2 value so that the policy home page is the default?
    If the answer is yes, their issue is resolved.
    

Local fix

  • customer is working on the code, but would like IBM to provide
    any solution
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • This APAR is associated with SPR# YGAO99EDEU.
    The change team could not reproduce the problem or determined
     that the problem has already been corrected.
    

APAR Information

  • APAR number

    LO76131

  • Reported component name

    DOMINO SERVER

  • Reported component ID

    5724E6200

  • Reported release

    853

  • Status

    CLOSED UR5

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-07-08

  • Closed date

    2013-08-14

  • Last modified date

    2013-08-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Domino

Software version:

8.5.3

Reference #:

LO76131

Modified date:

2013-08-14

Translate my page

Machine Translation

Content navigation