Jump to content

sprasad

Hornbill Users
  • Content Count

    133
  • Joined

  • Last visited

  • Days Won

    5

sprasad last won the day on November 3 2020

sprasad had the most liked content!

Community Reputation

25 Excellent

1 Follower

About sprasad

  • Rank
    Senior Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

1,722 profile views
  1. @AlexTumberthanks for letting me know. We already record our time manually as per your screen shot so was looking to see if this could be automated. I'll let the users know that there are no current plans, to make any such changes.
  2. Is it possible for Workspace posts have an 'in-post' time recording facility please? Our users post fairly regularly and some are large announcements so they would find not having to record these posts' time elements as separate timesheet updates beneficial. Below is an artist impression of what we would like to achieve, so you click on the Timer button, as soon as you start to compose your post and then stop it, once finished.
  3. We are capturing a lot of information under the Questions section, as part of progressive capture but the Search option does not query this table. Will it be possible to add this to the searching profile, and include questions text as part of the results?
  4. +1 from us also as this has been asked by a number of our users. Thanks.
  5. Hi @James AinsworthPlease cam I check if there has been any progress on this Change Request? Thanks.
  6. Full Error: Xmlmc method invocation failed for BPM invocation node '585d6fbe-21a1-8429-7be9-b722f46e52bd/flowcode-2541abd7-91f1-429d-e7d7-3c33a9de9cc7': 0200 apps updateReqStatus FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_bpm/updateReqStatus): nodeName: API Call: Close Request; nodeId: f3b58229-7c80-40b7-81c8-9fe5aec41275; At 575/1: "Uncaught EspMethodCall::invoke: Operation[apps/com.hornbill.servicemanager/Requests::systemCloseRequest] FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_ops/systemCloseRequest): nodeName: Set 'appOptions'; nodeId: be4
  7. All our requests are failing to close successfully with a broken head up display and failing BPM. We get the below error:
  8. Hi @Ehsan Many thanks for the update. Further to this, I asked for an update on a related Topic and I was advised to also raise with Customer success team. As a result, Hornbill Expert Services Ref: SR00165781 has been created. Thanks.
  9. Will do @Steven Boardman - thanks for your prompt reply.
  10. Hi @Ehsan - Can I ask if there has been any further discussion on this matter please? We are promoting the Portal to our customers but are having difficulties persuading them to use it, where a contact from an External IT Section looks after 4 different organisations and for him to review their requests, needs 4 different login ID's/password. Thanks.
  11. @Steven Boardman- Hi, Can I ask if there has been any further discussion on this matter please? We are promoting the Portal to our customers but are having difficulties persuading them to do so, where a contact from the IT Section looks after 4 different organisations and for him to review their requests, needs 4 different login ID's/password. Thanks.
  12. Can the 'Apply to Request' action from Shared Mailbox, be updated so when the email is attached to the timeline in the Service Manager request, the update includes the From Address (Sender), so it is consistent with the way emails sent from Service Manager are displayed in the timeline. This will help analyst identify any new connections which need to be added as well as save time as they will not have to use the 'View Email' option to see this information. Currently, to verify who sent the email and to show the email address, you have to click the 3 dots, then open email then copy the
  13. @James Ainsworth- As there has been no updates on this RFC, please let me know if you want me to re-log this under Service Manager.
×
×
  • Create New...