Prev
Next
Forums Integration / Customization IPA/ProcessFlow

LSF WFWORKUNIT not getting a status

 6 Replies
 3 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Terrie
New Member
Posts: 3
New Member
5/22/2015 1:17 PM

    We have upgraded to Lawson 10.0.5 and IPA.

    We have a processflow that is Triggered when a PA52 action is keyed as immediate.  It is to update some HR11 Userfields and a couple of other fields on HR11.

    Since we have upgraded, the flows are triggered on LSF side and move to the IPA side to run the flows and the data is updated, except for the Personnel actions where we are updating the Termination Date.  They get a workunit on the LSF side, but no status, so they don't get moved to IPA. 

    Has anyone any idea why this would happen on when the action involves updating the termination date? 

    Tim Cochrane
    Veteran Member
    Posts: 154
    Veteran Member
    5/29/2015 1:26 PM
      When you say "workunit created on the LSF side, but with no status" is there actually NO status (which I've never seen) or is it really in status 1 "Ready"??
      Does the same PA, updating a different value, port to IPA??
      Are you using a different Service name for the "term date" PA?? if so, is the corresponding service setup in Rich Client AND is the BPM Service name = Rich Client Service name??
      Tim Cochrane - Principal LM/IPA Consultant
      JimY
      Veteran Member
      Posts: 510
      Veteran Member
      5/29/2015 1:49 PM
        I am not sure if this is the same, but when testing the webrun node to run MM280 I needed it to pass the status back to the work unit so I could check to see if it completed correctly. When I view the log file it shows an "unknown error" where the status should be. I opened a ticket with Infor Support and they were able to duplicate it. They have created a JT for this and said it will be fixed in a future Landmark CU. We are on LSF 10.0.6 and Landmark/IPA 10.1.1.14.
        Terrie
        Basic Member
        Posts: 4
        Basic Member
        6/3/2015 6:58 PM
          We have the same SERVICE -- TERM.
          When I query the WFWORKUNIT table in Logan, The WF-STATUS field is blank, if the PA52 is immediate action with the Termination Date being updated.
          If the PA52 action is immediate and the termination date is not updated, then the WF-STATUS = 25 and I can see that it passed to IPA and a work unit was created and the flows completed and the other data that we have the flow update are updated.

          All our workflows worked fine in Lawson 9, PFI. We just had had this weird issue since moving to Lawson 10 and IPA.
          Tim Cochrane
          Veteran Member
          Posts: 154
          Veteran Member
          6/5/2015 10:47 AM
            ...not sure why Term Date would drive whether a flow is used or not, ESPECIALLY when you indicated that both scenarios were "immediate"...could you have some custom code that's driving ProcessFlows based on Term date or other fields??
            What does the "use workflow" flag show on PA50 have for the TERM Action (PA50>Setup>Use Workflow)??
            Tim Cochrane - Principal LM/IPA Consultant
            Terrie
            Basic Member
            Posts: 4
            Basic Member
            6/18/2015 4:55 PM
              So looking at the wpai log, it seems that a Service named "S3HREndAch" is being triggered. However, we don't have this Service, so nothing happens. Does anyone know why this service would be triggered or heard anything about it?
              David Williams
              Veteran Member
              Posts: 1127
              Veteran Member
              6/18/2015 5:09 PM
                Do you have a PA50 Action with that name? It looks like a Personnel Action.
                David Williams