Update data and close task based on input from a different part of the process?

Comments

8 comments

  • Avatar
    Loren Bratzler

    Gwen - I am curious:  How does the "all inclusive form" work?  If someone opens that form and edits data or marks one of the individual tasks complete, do they then submit the "all inclusive form"?  And if so, does the process then loop back around so that the "all inclusive form" is generated again for making further changes?

    0
    Comment actions Permalink
  • Avatar
    Gwen Wilson

    Hi Loren, that's correct. The "all inclusive form" is a start task (they either enter the form ID or do a filter search to select one, then I run a sql query to pull everything from the database). They can make changes, then submit. I haven't finished the process yet, but then I set some field values, convert dates etc, and write back to sql and the process ends. Then someone else can do it. I know there is a risk that 2 people could open the same form id at the same time. Then I guess the last to click submit wins (would overwrite any previous submits). I don't see anyway around that (thoughts?), but in this scenario, I don't think it would happen (but I'll make the users aware).

    What I have to learn is since I can't do the action item tasks in the "normal" task way. I need to build another process that "listens" for a trigger that gets sent to sql and then kick off emails to the task assignee. I've only ever made processes that started with start tasks... so I get a new learning experience LOL.

    0
    Comment actions Permalink
  • Avatar
    Loren Bratzler

    It sounds like what you might need to do is kick off a sub-process for each new task that is created by the "all inclusive form".  That way each of those tasks will have its own unique Process Instance ID.  You would then need to save that Process ID in the SQL table that contains all the other data about that task.  When you kick off the sub-processes, you can set the main (parent) process to not wait for completion of the sub-processes.  That way you don't have to keep that parent process active and the child sub-processes can live on as long as needed.

    Then if the supervisor initiates the parent process again and updates data on one of the existing sub-tasks, you would update the SQL data for that sub-task using the Process Instance ID as a key field for that sub-process.  Then on the sub-task form itself, you would need an Auto Lookup that executes on Form Load so that it pulls in the most current data.  The only danger there would be if a user had that sub-task open while the supervisor is updating something for that task.

    For your second requirement where the supervisor can mark the task complete:  You should be able to use a REST API call to cancel the child process.  So if the supervisor wants to cancel one of the tasks, you would get the Process Instance ID for that child task and execute the REST API call to cancel that process.  Documentation on the "Cancel Process Instance" API call can be seen here:

    https://documentation.agilepoint.com/11/developer/restmethodCancelProcInst.html

    Hope this makes sense and helps.

    0
    Comment actions Permalink
  • Avatar
    Gwen Wilson

    Thank you, Loren! That sounds like exactly what I need. I'll have to see what I can do with the 2nd step. Setting up REST API's are outside my abilities, but maybe I can muddle through :). I know I need to learn how to do it eventually.

    I really appreciate it!

    Gwen

    0
    Comment actions Permalink
  • Avatar
    Loren Bratzler

    Setting up the AgilePoint REST API calls is actually pretty easy.  Easier than setting up some other API calls I have done!

    I would be willing to do a Webex or Zoom meeting with you one day next week if you would like to see some examples of what I am talking about.

    0
    Comment actions Permalink
  • Avatar
    Gwen Wilson

    Thanks for the offer!  Let me see who far I can get on my own and if I get stuck, I'll let you know. I appreciate it!.

    0
    Comment actions Permalink
  • Hi all,

    just for your information: almost all REST API from AgilePoint could be also executed as WCF API calls, that are much easier to handle.

    Regards,
    Alexey

    0
    Comment actions Permalink
  • Avatar
    Gwen Wilson

    Loren, I hope the offer to show me how to set up an AgilePoint REST API call is still good :). I'm at that point (sorry it's been so long, I got pulled onto another project for about a month). I actually need to do a "cancel", "reassign" and "update" call to handle 3 different situations. I'm at a total loss. My email is gwen.wilson@everpack.com  Send me an email when you get time. Thanks!

    0
    Comment actions Permalink

Please sign in to leave a comment.