Looping through all records while adding some to the inbasket

 5 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Mona
New Member Send Private Message
Posts: 3
New Member

I have a scheduled process flow that will read the data stored on BS31 and determine which records needs an EOI and which ones does not.  Processflow adds the record that need an EOI to the inbasket to either approve/deny. 

The problem we are having is when the first record goes to the inbasket the processflow is held up until somebody takes action. How do I put the record in the inbasket and move on to the next record so that all records will be read.  And have all records that either should be approved/denied in the inbasket.

Michael Thedford
Advanced Member Send Private Message
Posts: 19
Advanced Member
Not knowing how your flow is currently setup, here's one suggestion to do this - you may need to have multiple process flows. The first flow will loop thru the records and perform your testing to identify the ones in question, and inside this loop it will kick off a work object to start another processflow for each record that you need approval.
Deleted User
New Member Send Private Message
Posts: 0
New Member
You will have to have two flows for two reasons, one the fact that it does wait for the approval, and the other is it would only process the first record anyway because when a flow pauses for an inbasket entry it loses the results from DME calls.

You should never put a User Action inside a DME loop.
Tim Cochrane
Veteran Member Send Private Message
Posts: 154
Veteran Member
Not sure why you've got a User Action within a query, but you're getting exactely what I would expect.

My suggestion - Replace the User Action with a Msg builder node. This will let the flow gather all the data you want to present, THEN send to the User Action after you break out of the query.
Tim Cochrane - Principal LM/IPA Consultant
Mona
New Member Send Private Message
Posts: 3
New Member
The problem is that we need to run the processflow after open enrollments ends. And for some elections the processflow must determine if the user is required to provide an EOI for the election. Once the employee turns in the EOI, Benefits must approve or deny the election based on the EOI. If the EOI is denied then the employee previous selection (prior to open enrollment) will be added. If the EOI is approved then the new election is added and the prior election is ended. Some of these selections can be going from one plan to another plan.

I have everything working but because there has to be user interaction to either approve or deny those EOI records (could be 1000's) the flow stops on the first record needing approval until an action is taken.

David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
Instead of going to a UserAction, create a new Service and a flow for the UserAction and then trigger that new Service with a WorkObject. That way you can loop through your records and create Inbasket tasks from the 2nd flow.
David Williams