MQSeries.net :: View topic - Automated Activity Expirations and Notifications

ptazbaz · Posted: Tue Jul 23, 2002 4:43 am Post subject:

Hello All,

The way my current fdl is designed, if an automated activity expires, it is moved off the upes_user list to error handler list and is set to a notification state. The idea was that in order to resume, I would simply need to transfer the item back to the upes_user list and issue a restart command using the windows admin client. The problem is that because the activity is now in a notification state, I cannot resume. I have to terminate and then issue a restart. My initial thinking was that a restart would resume at the expired activity. It does not. It re-starts the process instance at the beginning. This is not an option for me. I need to resume and restart in the activity that expired. Can someone please confirm if this is how worklfow administration operates? If so, I would need another solution. Rather than expiring and creating a notification, is it possible in the fdl to make the activity suspend after a certain duration? That way, I could fix whatever problem caused the activity to expire and simply resume the activity when ready. Does anyone recommend an alternate solution? Any input is much appreciated. Thanks.