Search the Community
Showing results for tags 'auto close'.
Found 3 results
Hi, After been running live now for a couple of weeks I have noticed that we have an awful lot of requests still sat in a 'Resolved' state despite them being resolved for more than 5 days. In our BPMs we have the following logic... The logic in the 'Suspend wait for status change node' is as follows... Should I have a 'Get Request Information - Request Details' node between the 'Suspend' node and the 'Decision' node? The logic on the 'north-bound' arm of the 'Decision' node is... The build of this part of the BPM was lifted directly from a sample BPM provided to us by during our 'Switch-On' which looks identical to the logic in the Example BPMs. Is anyone else having problems with their requests not auto closing after the expire period time? Thanks Steve.
Hi all, I remember some chatter about the auto close node not working correctly but as far as I was aware this had been fixed. At the moment it seems that in our instance it is not working and the auto close isn't kicking in. I did have the timer set incorrectly to start (I had it set to two days, which I assume was keeping them open for 48 working hours or approx. 5 working days so have now set it to 20 hours for 2 working days) but have since changed that but it is still not closing the calls. Any ideas what may be going wrong here? Thanks Dan
Good Morning, It has been raised to me by every one of out teams have noticed that their calls are not closing after the standard 5 days. We applied a auto close node to the BPM when we started using hornbill - Daniel helped us build our BPM's I have checked both the Incident and Service Request BPM's and they both have the auto close node set up to close after 5 days. But as you can see below no calls have been closed since the very beginning. Are the Nodes set up incorrectly or is this a known error? Many thanks Hayley.