Bookmarks Missing for ESS Users

 7 Replies
 0 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
trueblueg8tor
Advanced Member
Posts: 41
Advanced Member
    In our test Lsf environment some of our ESS users who have are being secured with 9.0 security are missing bookmarks. - They are a member of a bookmark group that has been granted access to the ESS bookmarks - They have a portal role where I've locked the ESS bookmarks (Subscription and Layout) - They all have an "EssRole" that has a Security class that has a rule that grants access to the Logan productline. - My ESS id works fine but the only difference I can see is that I have an OSID defined and the missing ones don't (due to 1,000 max per RMID) - We all have our XXX_EMPLOYEE service set up the same way. Any ideas?
    John Henley
    Posts: 3353
      - Do these folks perhaps have another role assigned to them which denies that access (i.e. to LOGAN)? - Although the users don't need to be assigned to a unique OSID, they do need to be assigned to either a generic one (e.g. essuser) or you need to have a default one set up. - The "1000 users per OSID" restriction was removed with LSF9 SP2.
      Thanks for using the LawsonGuru.com forums!
      John
      trueblueg8tor
      Advanced Member
      Posts: 41
      Advanced Member
        All ESS users (the ones with and without bookmarks) have the same Role. I thought that LS Security has a "greater access" methodology? Ie in the event two rules conflict the greater access wins out. Even if I had a rule denying it they should still get bookmarks right? Is access to the Logan PDL the only thing needed for bookmarks to appear?
        jojo.serquina
        Veteran Member
        Posts: 63
        Veteran Member

          there could be quite a few reasons as to why some of your users aren't getting the bookmarks they're supposed to.
          but...

          first thing I would check is to make sure that the users have been assigned the lawson delivered "PortalBookmarkAdminRole"

          Next, I'll make sure the users are given the 'appropriate group' you 'might' (or might not) have assigned to the Portal Role (xml file)

          Next, I'll make sure that users are assigned the 'appropriate' portal role, IF you created specific portal role (for ESS), that is.

          hope that tidbit helps...

          trueblueg8tor
          Advanced Member
          Posts: 41
          Advanced Member

            I figured it out- kind of. When the ESS users were logging in a userid.xml file was not being created in the $LAWDIR/persistdata/lawson/content/data/users directory. Guess I'll have to write something create them and ftp them until Lawson Support fixes it - whenever that might be...

            Joe O'Toole
            Veteran Member
            Posts: 314
            Veteran Member
              We had a similar problem on 8.03 - it had to do with required content, bookmark locks and the default.xml file we were using. If you didn't make any changes to default.xml, the content is assigned to the user and the bookmark locks are set properly, it should create their lefthand menu and a user.xml file in persistdata at thie initial login. We have 2 ESS menu versions on 8.03 and manually copy the other version to .xml if they need the larger menu. So far in my testing it appears LSF behaves the same way.

              andrew5499
              Veteran Member
              Posts: 100
              Veteran Member

                Not too sure if this would work, but if they are ONLY ESS users, can you create a new default.xml file for them, like defaultess.xml ?

                Joe O'Toole
                Veteran Member
                Posts: 314
                Veteran Member

                  The default.xml file should assign these. You can customize this if you have std content you want assigned or use a role assignment. For special case users, you can also overlay their user.xml file which will give them the new menu options.