Jump to content

Error messages this morning...


Paul Alexander
 Share

Recommended Posts

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

@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

@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

@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

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...