Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
  • 1.  Workflow Assignments fail before table changes have been committed to the database

    Posted Wed August 11, 2021 03:57 PM
    We have a workflow that initiates automatically via Organizations - Workflow Options - Purchase Requisitions on Reorder for our PR Approval workflow. With this setup, our PR Approval workflow will start when an MR is submitted via Desktop Requisitions. The workflow itself is determining the correct person to approve the PR. We had a request to modify the workflow so we can assign the workflow to a user based on a value from PRLINE table. The issue I am running into is that the workflow is initiated before the PRLINE data is committed to the database. So when I submit the MR, I get an error that the workflow does not have an owner for the task. I have verified the relationship is correct on the PR table and that it will only return 1 row from PRLINE table. Also, I have verified that the workflow works properly if I initiate it from a PR I enter directly. Has anyone run into this issue where database changes haven't been committed and what did you do to fix the issue? 


    ------------------------------
    Tim Jones
    Software Engineer
    Kaiser Aluminum
    Sherman TX
    (903) 892-5821
    ------------------------------

    #Maximo
    #AssetandFacilitiesManagement


  • 2.  RE: Workflow Assignments fail before table changes have been committed to the database

    Posted Thu August 12, 2021 12:19 PM

     

    Usually that type of problem is handled by using the objects in memory, i.e. :PRLINE as opposed to PRLINE, :PRNUM as opposed to PRNUM, etc.

     

    Can you post your code?

     

     

     






  • 3.  RE: Workflow Assignments fail before table changes have been committed to the database

    Posted Fri August 13, 2021 11:37 AM
    I have a simple relationship on the PR table to PRLINE. It is just a relationship hard coded to PR line 1. 



    My role for the assignment is using that relationship to get the PR line 1 requestedby. 

    The workflow itself is auto initiated when a user submits an MR, which I set in the Org options. 

    The spot where it fails is during the assignment in the PR APPROVAL workflow. 


    When I submit an MR that would hit this node, I get this error. 


    Thanks for the help. Hopefully you see something I don't. 


    ------------------------------
    Tim Jones
    Software Engineer
    Kaiser Aluminum
    Sherman TX
    (903) 892-5821
    ------------------------------