[Date fields showing as UTC in 'HTTP Request' post to Microsoft Teams]

Thanks.  Sent you a DM.

[Date fields showing as UTC in 'HTTP Request' post to Microsoft Teams]

Hi @Steve G, that does work better but I may have found a bug.

In the Human Task where I was asking for a date/time to be recorded, I had this tick-box ticked to prefill the variable with the current date/time.

If when completing this task they don't change that date/time value, despite having the fix in place you suggested above, the BPM still fails with the same error.  If they use the date/time picker to choose a date/time, everything works perfectly.  For now I have just un-ticked that tick-box so that the field is blank and they have to use the date/time picker to set a date/time.

So essentially the API call does not like the system generated date/value as a seedtime.

Any chance this can this be looked into please?

Cheers.

[Info on a recent fix to Service Manager]

Thanks, we will apply & observe.

Much appreciated.

[Info on a recent fix to Service Manager]

Thanks @David Hall, We will get the update applied and see if this fixes what we are seeing.  It sounds very similar.

Will this work for requests that are already raised or only for new requests raised post the update?

[Info on a recent fix to Service Manager]

Hi, where can I see more info please on the fix highlighted below?

I'm keen to see if this fixes something we are seeing also.

Thanks

[Date fields showing as UTC in 'HTTP Request' post to Microsoft Teams]

Thanks @Steve G, I see what you mean.  I thought the variables were stored, associated with the running instance of that request.

I have updated the BPM to pull the Task answers.  I will see how that works and post an update.

Thanks again.

[Date fields showing as UTC in 'HTTP Request' post to Microsoft Teams]

Morning @Steve G,

This is the section of the BPM

The seed time is being captured on completion of the 'Start Change Implementation' activity... (see below)

and injected here ...

It looks similar to what you are doing so confused why this isn't working.

Can we chat about this maybe?

Cheers.

[Date fields showing as UTC in 'HTTP Request' post to Microsoft Teams]

On 9/16/2019 at 6:12 PM, Steve G said:

Hi @Steven Cotterell,

Rather than providing an iBridge utility to perform this, I've written a new BPM node in Hornbill Collaboration to perform this instead (which is a much better method of providing a utility of this type). Timezone and Seed Time are both optional, and if not provided then it'll provide the current date/time of the session timezone.

It will be available in the next update Hornbill ESP. Keep an eye on the announcements forum to see when this goes live

Cheers,

Steve

Hi @Steve G,

We are seeing a problem with this API.

When the seed time is set behind current time, we get this error thrown...

Is this something you can take a look at please as all the requests which have the seed time set to not the current time are failing.

Cheers

Steve.

[Remedy Force Integration]

Thanks @Steve G, much appreciated.

[Bulk modify to 90 Change Request Details Forms]

On 12/6/2019 at 8:48 AM, Steven Cotterell said:

Good morning @Victor, were you able to make any headway into investigating why we cannot get the fields to stay in the order I put them?  I'm forever getting questions asked when this is going to be corrected.

Thanks in advance.

Steve.

@James Ainsworth, is there anything you could help with here maybe?  Cheers.

@Victor, were you able to carve any time out to look into this please?  This continues to be an issue for us.

If not is there anyone else that can look into this?

[Remedy Force Integration]

Has anyone else been successful in setting up two-way integration between Hornbill & Remedy? 

We have a customer who is really keen on making this work (and it would greatly help us too).

[Version number mismatch?]

This looks to be almost a 'visual issue' as the version of the BPM indicated as available to Publish is actually the most recent saved version, its just the 'version number' and the 'Updated on' fields are showing incorrect values.

Confusing. 

[Hornbill domains 'down' in South Africa]

@Keith Stevenson As of 13:20 UK time, they are still having the issue.

[Version number mismatch?]

13 minutes ago, Victor said:

@Steven Cotterell ... 

 

@Victor - Thanks  - I did obscure the one screenshot but missed the second one.  I have a new screenshot but now cannot edit the entry?  Can this be unlocked so I can edit and replace the screenshot?

On a side note, do you have any idea why my edited version of the BPM is not available to publish?

[Version number mismatch?]

I'm seeing the same issue @Deen.  I have just saved & validated a BPM but am unable to publish it as it is not showing as available to Publish.

This is the saved version.....

 

however this newly saved version is not there for me to Publish....

Ideas anyone..... ????

 

[Hornbill domains 'down' in South Africa]

https://www.cloudflarestatus.com/ is showing the following:-

I'm guessing it is all in their hands now?  Presume there is no way that Hornbill sites can be accessed without using the Cloudflare service?

[Hornbill domains 'down' in South Africa]

Its just been reported that its working fine for one of their customer in Johannesburg.  Looks to be an issue isolated to Cape Town.

[Hornbill domains 'down' in South Africa]

The issue is affecting the Anana guys in Cape Town office, also the Service Manager who is still at home in Cape Town and also one of their customers in a completely different location in Cape Town so this seems to be ruling out browser based issues.  They are going to get one of their customers in Johannesburg to check also.

I connected my VPN to Johannesburg server and I was able to connect ok.

[Hornbill domains 'down' in South Africa]

Checking now.  Thanks for what you've done so far.

[Hornbill domains 'down' in South Africa]

@Steven Boardman We only have the Community Support (free support plan).

Figured it would be more linked with Cloudflare and a local'ish issue in that part of the world, traffic not being able to maybe resolve to the Hornbill domain successfully?

Error is saying to contact Hosting provider, which would be you guys?

[Hornbill domains 'down' in South Africa]

Morning @Steven Boardman, are you able to assist with the above please?

[Hornbill domains 'down' in South Africa]

Can anyone assist please?

Our colleagues in Cape Town are are unable to get to the 'live.hornbill.com' or 'community.hornbill.com' or 'customer.hornbill.com' domains.

They are getting the following error.

and 

Our South Africa customers cannot log in to the Portal and the Support Team cannot also log in to the 'live.hornbill.com' URL to handle any requests.

Any help appreciated.

Thanks.

[Email replies not being added to Request]

@Victor, thanks for responding.  I will get you some examples.  Do you want the logs too?  If they are recent enough I'm guessing if you had an API key you could grab the relevant ones yourself.  Let me know what you want to do.

 

@Martyn Houghton, thanks for your reply too.  Yes, the messages that are not being processed are staying in the Inbox, which kinda indicates some sort of failure, but then the emails go there anyway don't they before being parsed by the Routing Rules?  AFAIK, this issue has been there for a long time, at least 6 months, we were just able to manage the few that used to evade the rule, but seeing a lot more now, hence me following up the issue.  I can do some tests on attachments.

[Email replies not being added to Request]

Hi,

I've spotted something happening in our Instance that I cannot explain.

We have this setting enabled in the Service Manager Settings...

, however when an email reply is received where the sender is not the 'Customer', the email is not being attached to the Request.

Where the sender IS the 'Customer', the email gets attached.

If the sender is the 'Customer' but the "To:" field contains our email address AND another/other recipient/s, these emails are also not being attached to the Request (this may be down to the routing rule though - if anyone more knowledgeable on Routing Rules can validate this that would be great).

Any help would be greatly appreciated.

Thanks

 

 

[Error when putting Incidents on-hold]

9 minutes ago, Ehsan said:

@Steven Cotterell, @PeterL,

Did you restart the Request's process for the affected Requests or are these new Requests? The patch has definitely taken affect.

Hi @Ehsan,

We've experienced it today during testing of Service Requests (only seen it so far for this request type) when the team complete a task whilst the request is on-hold - the outcome, when chosen, proceeds to set the status to 'Open' and we got this error

"Xmlmc method invocation failed for BPM invocation node 'stage-45048add/flowcode-00d3b0dc': 0200 apps updateReqStatus FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_bpm/updateReqStatus): nodeName: API Call: Clear Request Sub-status; nodeId: f3c2399f-f23a-4177-970c-0b74017039c9; At 184/1: "Uncaught EspMethodCall::invoke: Operation[data::updateRecord] There are no values to update" throw(e); _fc_node_exec_f3c2399f_f23a_4177_970c_0b74017039c9"