HR11 form transfer to Design Studio form transfers employee information

 4 Replies
 1 Subscribed to this topic
 12 Subscribed to this forum
Sort:
Author
Messages
Nabil
Veteran Member
Posts: 61
Veteran Member

    Hello,

     

    I have a custom HR11 form that displays an employee's own data, OnInit(). My question is, if an employee has access to the regular HR11 and transfers back to the custom HR11 they see the other employee data.

     

    Is there a way to force the custom HR11 not to take a previous employee from another form and display it?

    Kwane McNeal
    Veteran Member
    Posts: 479
    Veteran Member
      Short Answer: yes... but you have to clone the invoked programs and possibly the libraries.

      Why?

      Long Answer: due to the way LSF passes data to other parts of itself (IPCs) and the way LATM tracks programs (via a global heap), a users session into a program is essentially just a set of pointers into heap space and an IPC message queue back to the db driver.

      Since it’s Global (or that user), any program that uses the same libs to make the invoke can get the same data (it’s not exactly that simple, but this is the gist)

      In the olden days you could set USELATM to OFF/FALSE, but that was another lifetime ago, product-wise

      ...Your other option (that I can think of) is to use LS security to restrict the form to only that user's data, but you don’t clarify if the custom form is DS-only or an actual cloned 4GL form

      How badly do you want it to work, will dictate the effort
      Ragu Raghavan
      Veteran Member
      Posts: 476
      Veteran Member
        at the ONIT (or if needed in the BEFORE_TRANSACTION), can you not capture the EMP_EMPLOYEE and if not = the EMPLOYEE# on the profile, force in the Profile_emp#?
        Kwane McNeal
        Veteran Member
        Posts: 479
        Veteran Member
          Ragu makes a great point. I guess a question I have is what and where is the incorrect data being returned? Is it happening when the form paints (in the jscript) or after a transaction.

          Also, since you know the custom is supposed to ALWAYS be their own data, can you just force an Inquire?
          Nabil
          Veteran Member
          Posts: 61
          Veteran Member
            Thanks guys! I was able to always pass the portalWnd.oUserProfile.getAttribute("employee") into the field and URL that links to OnBase documents.
            The key is not to have Data Src populated and just have Default point to LAW_WEB_USR.employee

            Nabil