Resource Query not finding email...sometimes

 4 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
sfischer
Basic Member
Posts: 9
Basic Member
    Hi,

    I have been fighting with this situation for a day and would love to hear that someone else has run into this before.

    I have a flow that is based on the downloaded Solution reqapproval2.  In the flow are Resource Queries that look up the email (attribute) on the LDAP table for a particular REQUESTER (which is found on a previous node).

    Basically, a work unit is created when a requisition is released on RQ10.  If a user clicks "reject" from their inbasket, the flow goes to the Resource Query and finds the email of the Requestor.  This is where the error occurs, the Resource Query returns "*****" instead of the email address from LDAP.

    However, if I call up a work unit that was created by RQ10 from within the designer via Run --> Work unit, the Resource Query has no problem  finding the email address on the LDAP record and sending an email. 

    Does anyone know if this is some sort of firewall or security issue, since the flow is being run from the server and not my Designer?

    Thanks,
    KK - Infor
    Veteran Member
    Posts: 61
    Veteran Member
      Hi sfischer,
      In this case, I would check the pfconfig on your server. Just retype the user name and password for RM attribute and recycle your services.

      This shoudl resolve the issue.

      KK
      John Henley
      Posts: 3353
        Is this a newly-installed flow or what is migrated from Env 8.0.x ??
        Thanks for using the LawsonGuru.com forums!
        John
        John Henley
        Posts: 3353
          I have seen a couple of issues with using ResourceQuery nodes in requisition approval flows to lookup email addresses: - Because the ResourceQuery returns/iterates as a loop, you can have problems if you have more than one RMID assigned to the same requester. This is usually an anomoly due to setup/migration, etc. and isn't usually a problem once it's figured out. - If you have multiple requester identities for similar product line names, e.g. PROD8_REQUESTER vs. PROD_REQUESTER, that also causes ResourceQuery to return erroneous results. However, since you're seeing '***' that makes me think (like KK) that it's security-related. Check the user you are using to run the flow in the designer vs. the user setup to run the flows on the server via 'pfserv config'...
          Thanks for using the LawsonGuru.com forums!
          John
          sfischer
          Basic Member
          Posts: 9
          Basic Member
            Thank you all for your responses. Our system admin is fighting a few other fires right now, so he hasn't had a chance to look at this yet. l let you know how this turns out.

            Thanks again.

            As an answer to John Henley - this are newly installed flows to 9.0.