Guest Paul Alexander Posted September 27, 2019 Share Posted September 27, 2019 After updating to v1694 this morning we're getting a few errors on requests: I can press the 'restart last step' on the request and it works ok, but I'd like it to stop happening! thanks Link to comment Share on other sites More sharing options...
Guest Ehsan Posted September 27, 2019 Share Posted September 27, 2019 Hi @Paul Alexander, Thank you for bringing this to our attention. On behalf of Team Hornbill, I would like to apologise for the inconvenience that this has caused. I have investigated this issue and I can confirm that the Status is indeed changed, so please rest assured that the data remains up to date. This problem is caused by the step which attempts to update the Last Modified Date in a Request - This error is shown as the Last Modified Date is already up to date but the operation had not catered for this scenario. We have addressed this issue and this will be patch directly to your instance shortly. Thanks, Ehsan Link to comment Share on other sites More sharing options...
nasimg Posted September 27, 2019 Share Posted September 27, 2019 @Ehsan can you see if we need our instance patched as we are running this build. Nasim Link to comment Share on other sites More sharing options...
Guest Ehsan Posted September 27, 2019 Share Posted September 27, 2019 @nasimg The patch will be applied to your instance shortly. Link to comment Share on other sites More sharing options...
nasimg Posted September 30, 2019 Share Posted September 30, 2019 @Ehsan Has this latest update modified the way the smGetRequest API outputs the date field - we had some dashboards which have stopped working since applying build 1694. Nasim Link to comment Share on other sites More sharing options...
Guest Ehsan Posted September 30, 2019 Share Posted September 30, 2019 @nasimg, smGetRequests API is used to load the Requests in the Requests List - I can see that date fields such as "Last Updated Date" are shown as expected. What exactly are you seeing? Could you provide an example? Is there an error message that you can share with us? Link to comment Share on other sites More sharing options...
nasimg Posted September 30, 2019 Share Posted September 30, 2019 @Ehsan smGetRequests does have the dates, but they are appearing in a different format - I'll ask @carlt to get an example Nasim Link to comment Share on other sites More sharing options...
Dan Munns Posted September 30, 2019 Share Posted September 30, 2019 @Ehsan I think we may need this patch as well: @nasimg thanks for the heads up Link to comment Share on other sites More sharing options...
Steven Cotterell Posted September 30, 2019 Share Posted September 30, 2019 @Ehsan, we also need the patch please - we've seen the same error as experienced by @Paul Alexander. Link to comment Share on other sites More sharing options...
Guest Ehsan Posted October 1, 2019 Share Posted October 1, 2019 @Steven Cotterell @Paul Alexander @Dan Munns, I'm currently preparing a new Service Manager build to address 2 reported bugs. I'll post back as soon as a new build is available. Ehsan Link to comment Share on other sites More sharing options...
Jack_Podmore Posted October 2, 2019 Share Posted October 2, 2019 Hi @Ehsan, We are also experiencing this issue across the majority of our tickets on this build. Is it possible to apply this patch to our instance or give us an ETA on the release? Thanks in advanced, Jack Link to comment Share on other sites More sharing options...
Guest Ehsan Posted October 2, 2019 Share Posted October 2, 2019 @Jack_Podmore - We've just completed testing the build and I'm currently going through the process of making it available in the App Store. Estimating to have this build available in the next hour. Once again, apologies for the inconvenience that this issue has caused, this is at the top of our priority. Link to comment Share on other sites More sharing options...
Guest Ehsan Posted October 2, 2019 Share Posted October 2, 2019 @Jack_Podmore @Steven Cotterell @Paul Alexander @Dan Munns, A new build of the Service Manager application is now available. Please update to this version. Ehsan Link to comment Share on other sites More sharing options...
Dan Munns Posted October 2, 2019 Share Posted October 2, 2019 Thanks @Ehsan I'll give it a go now. Link to comment Share on other sites More sharing options...
Jack_Podmore Posted October 2, 2019 Share Posted October 2, 2019 Hi @Paul Alexander I am interested to know more about the 'restart last step' within the request you mentioned in initial post. Is this something you have configured yourself in a BP? Thanks, Jack Link to comment Share on other sites More sharing options...
Guest Ehsan Posted October 2, 2019 Share Posted October 2, 2019 @Jack_Podmore, Within a Request with a failed BPM, you can choose to restart the last step. For details and prerequisites, please refer to "How to restart a failed workflow" section in the document below: https://wiki.hornbill.com/index.php/Business_Process_Designer Ehsan Link to comment Share on other sites More sharing options...
Jack_Podmore Posted October 2, 2019 Share Posted October 2, 2019 @Ehsan thank you for this. Also thanks again for the patch release, we have had no more issues reported of error's so fingers crossed this is all resolved! Link to comment Share on other sites More sharing options...
Guest Ehsan Posted October 2, 2019 Share Posted October 2, 2019 Great to hear @Jack_Podmore 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