Rohit Govind Posted April 25, 2017 Share Posted April 25, 2017 Hi, We have several BP workflows setup for Incidents and SR's and each process has been setup with a "Reopen request" human task which has a Lifespan setting set to expire after 2 days. I've attached a screen shot for review. When we setup the process and tested it the workflow worked as defined and tickets we're closing automatically after the 2 day lifespan had expired but I've recently noticed that this is not the case and I'm having to manually close tickets. Just wanted to know if anyone else has had any issue when setting up lifespan settings? Thanks, Rohit. Link to comment Share on other sites More sharing options...
Victor Posted April 25, 2017 Share Posted April 25, 2017 @Rohit Govind setup looks correct and it should work as designed... do you have any recent examples (request references) where this failed? Link to comment Share on other sites More sharing options...
Rohit Govind Posted April 25, 2017 Author Share Posted April 25, 2017 Yes, a whole bunch of them I manually closed this morning. Below is a couple of examples: IN000001449 SR00001790 Link to comment Share on other sites More sharing options...
Victor Posted April 25, 2017 Share Posted April 25, 2017 @Rohit Govind thanks, I'll have a look and see if I can spot anything obvious why they failed to do as told! Link to comment Share on other sites More sharing options...
Rohit Govind Posted April 25, 2017 Author Share Posted April 25, 2017 How dare they disobey.... Thanks, Link to comment Share on other sites More sharing options...
Victor Posted April 25, 2017 Share Posted April 25, 2017 @Rohit Govind I know !!! They should know better!!! ... I think on this occasion the requests are not at fault...nor the BP configuration... I ran some tests and I suspect the "Close after a period of time" action is not triggering the closure after 1 min (as configured)... I asked dev team if they have any thoughts as I suspect a defect at this point... Link to comment Share on other sites More sharing options...
Steve Giller Posted April 25, 2017 Share Posted April 25, 2017 I fear you may be correct - I have some Requests set to close 2 (working) days after resolution which should have been lunchtime today, but they're still sat as resolved. Link to comment Share on other sites More sharing options...
Guest Ehsan Posted April 25, 2017 Share Posted April 25, 2017 @Rohit Govind, @DeadMeatGF, Thanks for bringing this to our attention. We have identified the cause of this. This will be fixed in the next update of Service Manager app, currently estimated to be available towards the end of next week (week commencing 1st May). Thanks, Ehsan Link to comment Share on other sites More sharing options...
Rohit Govind Posted April 25, 2017 Author Share Posted April 25, 2017 Thanks, role on 1st May.... There nothing more mind numbing then manually closing dozens of tickets. Link to comment Share on other sites More sharing options...
Guest Ehsan Posted April 26, 2017 Share Posted April 26, 2017 @Rohit Govind, Please accept my sincere apologies for the inconvenience that this is causing. Although I understand that this manual intervention is not ideal, this is considered a viable short term workaround and hence we do not have a case for publishing an emergency update for the Service Manager app. We have a process for publishing updates for the Service Manager app and the fix for this reported problem is scheduled to be available in the week commencing 1st May. This allows us to follow through regression tests to confirm that this area is not going to cause any further disturbance to your Service Desk operations in the future. You may be interested in subscribing to our Premier Success Plan (details can be found here - https://wiki.hornbill.com/index.php/Premier_Success_Plan) where you can contact us directly to report problems, such as the one in this forum post. This then provides you with an extended support service function. This success plan includes a service level for reported problems and we provide regular updates through our support function on the progression of those. This plan also qualifies for determining whether a reported problem requires an emergency update to the Service Manager app. Your organisation is subscribed to the Essential Success Plan, which does not qualify you for extended support service function and there are no service levels for responses or bug fixes on the forum I am afraid. Please contact us if you would like any further information on this. Thanks, Ehsan Link to comment Share on other sites More sharing options...
Rohit Govind Posted May 8, 2017 Author Share Posted May 8, 2017 Hi Ehsan, Do you know if the fix has been applied to the latest update? Thanks, Rohit. Link to comment Share on other sites More sharing options...
Victor Posted May 8, 2017 Share Posted May 8, 2017 @Rohit Govind the fix (for this issue) is included in the next Service Manager update. However we have not yet deployed this update in live instances. It is scheduled for mid-end of this week (look for SM build > 956). The deployment is posted in the "Announcements" section of the forum as well. Link to comment Share on other sites More sharing options...
Rohit Govind Posted May 9, 2017 Author Share Posted May 9, 2017 great thanks for the update. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now