IPA users, tasks, and user tasks

 9 Replies
 2 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
steve finger
Veteran Member
Posts: 47
Veteran Member

    The users who would be in charge of maintaining these tables for RQ approval flow don't want to do it and is insisting we automate the process.  Is anyone doing this?   the users are the approvers, the tasks are the approval levels, the filters are the requesting locations, and the user tasks are approval actions.  I haven't found anyone who is maintaining these tables automatically.  I have several ideas on ways it can be accomplished, but are all monsters.

    Kwane McNeal
    Veteran Member
    Posts: 479
    Veteran Member
      I know of a few clients who were automating this in PFI/PFX. It was easy, because you could write to the LOGAN and PRODLINE tables using either SQL or using some sort of COBOL calling program.

      I'd imagine that the setup is still the same for the LSF side, but perhaps someone who does IPA on regularly can tell you how to extend that process to update the Landmark side.
      David Williams
      Veteran Member
      Posts: 1127
      Veteran Member
        I have done this for HR approvers but what criteria/settings would you use to auto-setup RQ approvers? If you can define who would approve with what Task/Filter then it would be easy to automate the user setup. It's a matter of comparing who should be setup with who is already setup and updating the PFI tables in IPA/Landmark.
        David Williams
        steve finger
        Veteran Member
        Posts: 47
        Veteran Member
          > but what criteria/settings would you use to auto-setup RQ approvers

          that is a burning question. The data is not naturally in lawson. the main issue seems to be how do you determine who is a manager or director for any given requesting location. there is no natural place to store this info. The data warehouse folks claim to be able to produce a spreadsheet with all the relevant info - only a claim at this point with no evidence.

          So...suppose you have a CSV with the all the needed data (from this magical data warehouse routine).... which way would you go? we're going to assume that users are in IPA and that the tasks are defined as well. how to maintain the other tables? spreadsheet designer? a new flow? use of the utilities available in IPA/configuration console?
          David Williams
          Veteran Member
          Posts: 1127
          Veteran Member
            If "IF" they produce a Spreadsheet CSV file, you can read that into IPA and assign the records to an array variable.
            Then use a Landmark Transaction (query) to retrieve your current approval setup and assign to another array variable.
            Then use a JavaScript Expression (with an Assign) to compare the two array variables and create new array variables (oldApprovers & new Approvers) and then use these (with a DataIterator) to delete or add the approver setup.
            David Williams
            steve finger
            Veteran Member
            Posts: 47
            Veteran Member
              just for giggles....how many hours do think it would take to produce such a flow? you think that would be easier than spreadsheet designer given a CSV?

              btw....so...we still don't know anyone who is doing it automatically already?
              steve finger
              Veteran Member
              Posts: 47
              Veteran Member
                say something Kwane...you ALWAYS have good ideas and are never at a loss for words
                Kwane McNeal
                Veteran Member
                Posts: 479
                Veteran Member
                  The power of my good ideas is knowing when Other people have better ones. David Williams is by far more an expert than I at this.

                  As far as clients who have done it, I can think of two who I have consulted for who have done so. As I wasn't involved with the automation (it was setup before my involvement), I don't have a ton of details, other than what I recall seeing in a review.

                  With that said, David W is correct in the basic approach, as this is essentially what I recall seeing. the key is what will be the trigger to both distinguish user as an approver, and does the automation process need to be event- or schedule-based?
                  David Williams
                  Veteran Member
                  Posts: 1127
                  Veteran Member
                    4 hours should be enough. I don't know anyone doing this for Requisition approvals and have only done it for HR in the past. I have created Design Studio forms to make the data entry easier. It would then trigger a flow to do the actual updates.
                    David Williams
                    Kwane McNeal
                    Veteran Member
                    Posts: 479
                    Veteran Member
                      Steve, David is on the money, as usual. I'd take his counsel here, and turn it into either a plan to execute or an engagement for David, since it would most likely be a simple task for him to accomplish (barring complicated requirements from the client), and quick turn around for the client... Which is always for your reputation with the client.