Loop case creation to start new case upon resolution of a previous case
We have a process that creates a case/flow when a navigational menu item is selected. This creates a new case that the user then completes. The requirement is that when the case is complete/resolved the user does not want to have to click the navigational menu item again to start another of the same case.
Basically, they want the process to loop from the resolution of the last case to the creation of a new/next case without the extra menu click. To exit the loop they would click a cancel button that cancels the current case flow, but they don't want to have to click to create a new case each time.
Pegasystems Inc.
FR
Hello,
I'm not sure to get your exact business need here. But I don't quite see why this would be impossible with a custom activity to automatically start your new case creation.
Have you tried that already? Do you have any error message?
Living Direct
US
Marc,
Forgive the delay. This process seems to be much more complicated than I first asked, but I will try to outline the process to discribe what is involved.
- For a set of users we have a portal that when open has a menu.
- The user selects the appropriate menu item
- A new case is created and a new tab is opened in the portal that has the new case ID as the text
- Client fills out the data and submits
- Flows complete, case closes and the tab closes.
- User is returned back to the main screen.
This is the way it works currently. Now to do another entry, they have to start all over at 1 and click the menu item, etc. etc. They want the process such that when they submit on the entry screen, it completes the case and then opens up a new case/tab (such as SHP-13047 in this case) and allows them immediately begin entering data again. They want to reduce the need to move their hand from the keyboard, move the mouse to click a menu item, and then return to keyboard for entery.
I looked at the process and the navigation menu kicks off the flow using a Create Work Ajax call like this:
Marc,
Forgive the delay. This process seems to be much more complicated than I first asked, but I will try to outline the process to discribe what is involved.
- For a set of users we have a portal that when open has a menu.
- The user selects the appropriate menu item
- A new case is created and a new tab is opened in the portal that has the new case ID as the text
- Client fills out the data and submits
- Flows complete, case closes and the tab closes.
- User is returned back to the main screen.
This is the way it works currently. Now to do another entry, they have to start all over at 1 and click the menu item, etc. etc. They want the process such that when they submit on the entry screen, it completes the case and then opens up a new case/tab (such as SHP-13047 in this case) and allows them immediately begin entering data again. They want to reduce the need to move their hand from the keyboard, move the mouse to click a menu item, and then return to keyboard for entery.
I looked at the process and the navigation menu kicks off the flow using a Create Work Ajax call like this:
The pyStartCase then creates the new case and tab and is ready for entry. When the case is finished (the end of the last stage is reached) the case auto resolves and closes parent and child.
What I can't figure out is how to insert another activity between when the case closes and before it goes back to the home screen/menu. I thought about doing this at the end of the flow where I added in a "Close and New" activity:
And then have an activity that forces the case closed and then starts a new work object:
However, all this does is resolve the case to "Resolved-Closed" and then turns around and reopens the same case number. So if my first case number was SHP-13046. Instead of closing SHP-13046 and making a new tab SHP-13047, it leave SHP-13046 tab open and brings the entry screen up with all the data from the SHP-13046 entry instead of blank and ready for new data.
I've tried several combination of methods to close and create new, but they all result in the same tab reopening the old case.
I don't know if this explaination confuses things more, but there you go.
FusionAIx
NL
Hi,
I don't think using the AJAX-container is the correct way to go.
Probably you can you add a click action to a button which does the following:
- Finishes the current assignment
- Closes the work-object (or make sure that in the Flow Action, the review harness is not shown)
- Create Work with Target Default
But when thinking about this requirement, wouldn't it be more effective to create 1 (temporary) case which spins-off multiple new cases given certain inputs? This would eliminate the need for the screen to reload constantly.