Jump to content

ArmandoDM

Hornbill Developer
  • Content Count

    433
  • Joined

  • Last visited

  • Days Won

    9

ArmandoDM last won the day on July 29 2020

ArmandoDM had the most liked content!

Community Reputation

60 Excellent

About ArmandoDM

  • Rank
    Hornbill Developer

Profile Information

  • Gender
    Male

Recent Profile Visitors

1,739 profile views
  1. Hi @Paul Alexander not sure why it took so long, but glad to hear that's sorted now. Regards Armando
  2. Hi @Paul Alexander the same issue has already been fixed in the past, so I suspect you're displayed a cached value. May I ask you trying to remove/add the Get request information node and see if the issue is fixed ? This is the thread where the same issue was reported a while ago Thank you Armando
  3. Hi @Nikolaj yes, the issue has been fixed and it will be available with the next build. Thank you Armando
  4. Hi @Paul Alexander can you please try reloading the BPM after clearing the cache as we cannot replicate this issue. Regards Armando
  5. Hi @Nikolaj the issue has been reported and the fix is being worked, so its not available in the last update. I rekon it will be available with the next update. Apologies for the inconvenience. Regards Armando
  6. Hi @Nikolaj the max allowed size for Device Name is 64. I will report the issue you mentioned for fix. Apologies for the inconvenience. Regards Armando
  7. Hi @Adrian Simpkins, sorry my mistake, the notices on requests may also be set outside the suspend nodes. May you please post a screenshot of the 'Set notice on Request' node ? Ideally I can replicate the issue and investigate. By the look of the error, it looks like the node does not receive the request ID. Regards Armando
  8. @Adrian Simpkins the bpm operation addNotice is only used in suspend nodes. Is there any suspend node configured in the autotask ? Regards Armando
  9. Hi @LouiseT I will mention your request to the relevant people. Regards Armando
  10. Hi @LouiseT I don't think this is currently possible. Nonetheless, once the request has been logged you may add in your BPM process a node to lock the asset action (Access Control) so no assets can be linked to the request. Here is some documentation about the asset action on the request and the BPM operation to lock the asset action: https://wiki.hornbill.com/index.php?title=Assets_Action_Item https://wiki.hornbill.com/index.php?title=Service_Manager_Business_Process_Workflow#Access_Control Hope this helps Regards Armando
  11. @Dave Longley I will mention this to the relevant people
  12. Ciao @Giuseppe Iannacone Glad to hear that's sorted out now.
  13. @Jeremy if the issue presents occasionally, then we'd need deeper investigation on that. Ideally an use case where the issue can be replicated.
  14. Hi @Jeremy the timeline entry shows that either the user does not belong to the team or the user is not enabled for assignment. Have you checked that the user is enabled for assignment ? Regards Armando
×
×
  • Create New...