Reminder Emails in ProcessFlow

 3 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
pfguy
Basic Member
Posts: 14
Basic Member
    I have placed a variable in the user section for reminders, and the clickled on user. The send reminders to all userd that did not take an action is checked. Without this checked, the default email on the white space, properties is what is sent. When checked it sends the reminder msg as the body for the email.

    The variable is enclosed ie: . I'm finding that its sending an email to more users than just the userid in the variable. Eevn without the, "ALL users that did not take an action box", unchecked.. Does anyone have any experience with Reminder notices for LSF9.... We go live shortly....

    Thank You in advance.
    TBonney
    Veteran Member
    Posts: 281
    Veteran Member
      sorry pfguy...

      We do use reminders in LSF9, but we've never tried using a vaiable to designate only certain recipients. We simply take advantage of the option "remind all users that did not take action", based on the rationale that if none of the original recipients has acted on it yet, all of them should know that it is still awaiting their approval/rejection action.
      Shane Jones
      Veteran Member
      Posts: 460
      Veteran Member
        I had to think about this one a bit but I have a thought.

        Is the variable defined in the SERVICE or just in the start node and then how is it assigned within the flow? In other words is the value stored in "PF Admin" as a workunit variable... If the value is determined in the flow and then used dynamically while the flow is running you might be losing the value when it is needed. Flows can not use dynamic variables after a USERACTION node. If you do not "store" the value within the workunit variables it will not know the value when you are trying to use it. Check one of the Workunits that did not work to see if the workunit variables in PF Admin shows the correct value.

        Hope this is the issue - because it is easy to fix with a node to store/save the value to the variable within PF Admin. This is all I could think of because we have a flow where we needed to write the value to the Workunit because the flow would lose the value after it waits at a UserAction node........
        Shane Jones
        Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
        Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
        ** Teach others to fish...
        KK - Infor
        Veteran Member
        Posts: 61
        Veteran Member
          pfguy,
          I agree with what Shane has said above.
          One more thing you would like to check, is how are the user id's formatted in the variable.
          I would test it in two ways
          - just the comma separated RMIDs
          - RMID+'('+ NAME+')' - Since this is the format that is picked up if you click on Search in Select Users Window.

          Hope this helps!
          KK