Prev
Next
Forums Human Capital Management Lawson S3 HR/Payroll/Benefits

Securing Delete action within PA22

 8 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
Lee
Posts: 37
11/30/2010 2:11 PM
    We are rolling out additional functionality to the PA community locally; however, we do not wish to allow 'Delete' functionality within the PA22 FC Pairs except to a very select few users. We are considering using the HR related security (codes 1 through 9) on the form - requireing that the 'delete' functionality be available only to those select folks in our HR office.
    How can this be completed? Which API, if any, can force this issue to be completed only by an HR security level of '1'?
    Karen Ploof
    Veteran Member
    Posts: 118
    Veteran Member
    11/30/2010 7:10 PM
      I'm curious about why you chose not to do this using normal security set up. Are you using PA22 in a process flow?
      Lee
      Posts: 37
      11/30/2010 9:14 PM
        We are still using laua security - and the only available options on the form itself are CINP+- (PA22.1), however, within the form, the detail FC is ACD - and we desire to have the non corporate personnel not to have the access to the 'D' capability that is in the form. We plan to be able to track the certifications and their updates/priors, etc. When we get to Lawson Security, hopefully this will be easier, but for now, we need to eliminate the 'Delete' function.
        Mark A
        Basic Member
        Posts: 8
        Basic Member
        12/1/2010 12:21 PM
          You should still handle this within LAUA but it will require a new security class for those users whom you do not want to have delete access. This is assuming everyone with access to PA22 can see all employees.
          stephanie
          Veteran Member
          Posts: 330
          Veteran Member
          12/1/2010 1:11 PM
            Sorry I don't have a solution for you - but it's very interesting when I look at the form ID security for PA22 which is not secured at all here, I, too, see only the options you list, Lee - there is NO add or delete option to secure. Wonder if that relates in any way to ESS and Career Management? It's looking like the only option you have with laua is to secure the form change function - not what you need, I know. Good luck with this one!
            Mark A
            Basic Member
            Posts: 8
            Basic Member
            12/1/2010 1:44 PM
              You can delete the 'D' under FCPair for the Change action in LAUA.
              stephanie
              Veteran Member
              Posts: 330
              Veteran Member
              12/1/2010 2:15 PM
                Found it - thank you Mark. Buried a little deeper than I'm used to looking - That's what I love about these sites - I learn something new every day!
                Lee
                Posts: 37
                12/1/2010 8:15 PM
                  Thanks for all of the thoughts! Part of the problem is 1260+ users with full access to the PA22 - and needed only 5 with Delete capability. With LAUA as our current primary means of security, we opted to use the FC pairs as our vehicle for the 1260 users vs creating a new security class in addition to our existing 2040 security classes. That is why we were attempting to utilize the API coding in order to use the HR related security level(s) (i.e. 1,3,5,7,9 presented on the HR11).
                  Mark A
                  Basic Member
                  Posts: 8
                  Basic Member
                  12/1/2010 8:32 PM
                    Another option...
                    If you are using Design Studio, you could script it and not allow a 'D' to be entered in the function code for all but the 5 users.