WFWK

 6 Replies
 2 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
ALW
Basic Member
Posts: 8
Basic Member

    How do I give a Lawson user access to the WFWK form?  I am a Lawson user with the Admin role and I can access the form without a problem.  Another user who tries to access the WFWK for gets the following error:

     

    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
      The same way, through security, that you give them access to any other system form. This form exists within the same product line as your other forms. The system code should be WF.
      David Williams
      ALW
      Basic Member
      Posts: 8
      Basic Member

        Can you show me an example please.

        Thank you!

        ALW
        Basic Member
        Posts: 8
        Basic Member
          Here's what I'm not understanding. I login to the Lawson Portal, in the Search Box on the right Side I enter WFWK, hit the magnify glass and it brings up Workflow Trigger Screen/Form WFWK.1 I then enter my required parameters and click on Add and then my Workflow Process kicks off using the parameters I entered. That is exactly what I want to happen. My Lawson User account is set up where I am a Lawson Admin.

          Now a regular Lawson User who has the following roles: ALLFILES, BATCH, InforMingle, APINQUIRY, COMPANY311ACCESS logs into the Lawson Portal, in the Search Box on the right side, enters WFWK, and hits the magnify glass. Instead of the WFWK.1 Screen/Form coming up, an error message is displayed that says:

          Search Results:
          No programs or bookmarks were found were found for 'wfwk'.

          I am not sure what Lawson Functional Role I need to give the user in order for the user to be able to access the form WFWK. Someone replied with the following:

          The same way, through security, that you give them access to any other system form. This form exists within the same product line as your other forms. The system code should be WF

          I do not understand the reply and am looking for a better explanation AND an example. We don't want every user to be able to access this form.

          Thank you in advance!!!

          ALW
          Kwane McNeal
          Veteran Member
          Posts: 479
          Veteran Member
            ALW,
            The info you got from David was about the best you you'll see, since we don't know your security configuration.
            You list the roles you've assigned, but we don't know your role setup.

            you need to look at your setup for the user in question, see if there is an appropriate role to assign a security class that contains the WF/WFWK/WFWK.1 security objects, or you'll need to create such a class and possibly role to contain those security objects.

            Then, as David as stated, this should work for you.

            Kwane
            JimY
            Veteran Member
            Posts: 510
            Veteran Member
              I have had that problem with other forms before and the only way that I have found to resolve it is to go to Book Mark Manager and assign the user to the form. Not sure why it is a problem for some forms and not others. Good Luck.
              edison
              Advanced Member
              Posts: 23
              Advanced Member
                ALW,

                use the lawson Security Administrator > Reports > Report Maintenance
                ObjSecReport (Object Security Report) WFWK.1 run the report and view the result (i prefer html)

                - you will see all the users that has access to WFWK.1
                - the Role that gave them this access
                - the security class that the role has that gave that role the access.

                in security administrator > User Maintenance

                you can pick a role and give it to the user (easy)
                pick a role that the user already has and assign the security class to that role (medium)
                create a custom role and assign the security class to that role (complicated)
                create a custom security class... (complicated x2)

                note: these things i figured out by trial+error. it might not be in accordance with standard practices.