Jump to content

Steve Giller

Hornbill Staff
  • Posts

    6,498
  • Joined

  • Last visited

  • Days Won

    268

Everything posted by Steve Giller

  1. The Lane should be populated from the Assessment node, not the Suspend (Wait for Impact Assessment) node. You will need to ensure you use a unique Result Reference value - if you use the (old) default of ResultRef the values may conflict with another node. The Add to Board node does not have to be immediately after the Assessment node, as long as the result from the Assessment node is still valid.
  2. This should be as simple as ensuring the Lanes' names match the possible outcomes of the Assessment node, and passing that variable as the Lane Name.
  3. Details on Service Manager Business Process nodes are documented on the wiki. As far as I'm aware neither of these are changes that are being considered.
  4. This can be easily achieved with Routing Rules. No, this must be done when a Request is raised. This is available from a Get Request Information -> Source Email Details node for Requests that are raised from emails. The information could be stored in a date/time Custom Field and reported against.
  5. With the information above it's difficult to comment on what may be happening. I would suggest reviewing the Service Level Rules Builder wiki page (and any related pages you're not familiar with) and if that doesn't answer your questions post back here.
  6. This would be against the BP that each individual (linked) Request is running against. Let's say we have a system that has failed which has triggered the MI, and this is preventing Users from signing in - but Users who are already signed in can continue to work but can't save their documents. You will have two types of Incident - Can't log on, and Can't Save. These will likely have different Workflows associated and a different clean-up between resolution and closure, so it is important that the Linked Requests continue to follow their own workflows despite being part of the same MI.
  7. Are they from h_custom_a - h_custom_o, by any chance? These are VARCHAR/255 fields, see the notes: VARCHAR custom fields a - o each suitable for holding up to 255 characters of any type. See the Mapping Fields from Customised Forms wiki page for more details.
  8. Any User with a Service Manager Role must be a Full User. Basic Users are visible under the Platform Configuration section.
  9. @Alisha {{user.phone}} and {{user.mobile}} are both working for me, I can see forum posts from 2 years ago where it was available, but I don't have a link to the Release Notes where they were implemented I'm afraid.
  10. You can Resolve linked Requests in the BPM - then the Linked requests can follow their own Resolve->Close procedure in their own Workflows.
  11. Neither of those, however there are many criteria for accepting a suggestion and even more for prioritising it, and it's likely that only if/when one makes it into active development a response will appear on the Forums.
  12. The Database Asset Relationship Import tool seems like a good fit here - with the caveat that I haven't used this tool personally and I'm basing that assumption on the name alone.
  13. What field are you storing the date/time in? You may wish to review the page on Mapping Fields and ensure that you are using a Date/Time field for this.
  14. What are you expecting it to do? REGEX_MATCH will return true or false depending on whether it finds a match. It will not do anything else. Routing Rules do not manipulate the email, they simply perform the required operation (move to folder, raise request etc.) if the expression matches and pass the email to the next rule if it doesn't.
  15. @AlishaYou're welcome to request an Enhancement, to do so please start a fresh thread, use the "Enhancement" tag, and give as complete and clear description of what you're requesting so that it can be considered. i.e. Simply tagging this as Enhancement wouldn't work as you're specifying Operating System so that's all that would be on the Enhancement should it be accepted.
  16. If I'm understanding what you're doing (and I'm not an expert at regex) this https://regex101.com/r/FIDaEc/1 might show you why you're getting unexpected results.
  17. You can always put in a request for an Enhancement - just start a fresh thread with the Enhancement tag, giving your requirements as clearly and completely as possible.
  18. The details are on the Customer Feedback wiki page. Feedback can be enabled per request type (Incidents and Services Requests) and per service where it is required. The Expiry here is for the node (i.e. how long the Workflow waits) not the Feedback itself - the feedback expiry is set in the Service Portfolio.
  19. @Giuseppe IannaconeIn that case the &[global["flowcoderefs"]["getCustomerInformation"]["manager"]] value will return the Manager ID, which you can use in a Core->Application->Users->Get User Custom Attributes node.
  20. If they are created and added manually then they will need to be completed and removed manually. Unless you have multiple Tasks from the same Request being placed on the board (from the description I can't see that being likely) then it would be better to add the Request to the Board via the BPM or an AutoTask, then you will have a reference available to remove it later.
  21. I've tagged this as an Enhancement Request for you. Please note that does not mean it will be accepted, however it will be spotted by Development.
  22. If the User is the Request Customer then I would expect a Requests->Get Request Information->Customer Details node to return the value in &[global["flowcoderefs"]["getCustomerInformation"]["custom3"]]
×
×
  • Create New...