Steve Giller

If you click the "X" top right corner that should* clear the box and remember your preference: *Should - this is Edge, after all ...

I'm not aware of any planned changes in this area, however I have tagged this as an Enhancement request.

I'm not aware of any plans to implement this at present. If this changes we'll update this forum post.

This will be implemented in an upcoming Service Manager Release. Keep an eye on the Release Notes for further information.

To close this one off, the Data Chart option does not cater for table Joins in this way, and the query itself is not a suitable one for producing a graph.

This should have been fixed in a recent update, can you confirm you no longer have this issue?

@DRiley I'm sure this is just a typo, but should there be a back-tick in the URL? It stands out as an unusual character to be using in that context, but I'm not familiar with InTune so apologies if that's the expected syntax.

When I have a long list of Tasks the view is paginated - there is nothing to scroll for me. Where are you seeing this issue?

Whereabouts would you expect to see these - are you referring to the Draft Version Notes? If I was looking at having document-style formatted version notes for Captures/Processes I'd be looking into having a proper process of creating the notes in Document Manager and using the Versioning functionality (along with review dates) to keep the Document and Workflow/Capture in line and up to date.

This is a known browser issue, and is, unfortunately, out of our control.

There may be some misunderstanding about how Suspend nodes operate here. Without seeing the configuration, and the Requests in question it's difficult to understand what went on here, but I would expect this to have been either a Suspend -> Wait for Status Change or a Suspend -> Wait for Request Closure node. The Expire Period parameter here only comes into effect if the Status Change/Request Closure has not happened, i.e. it is the maximum time for the Workflow to suspend. If the Workflow was passing straight through the node it could suggest that the Request was already Closed, or that the Expire Period parameter is incorrectly populated.

The log you're showing indicates that the Report has not run since the 7th March - is there anywhere else that the emails may be originating, e.g. a report with the same/similar name?

It's not really clear what you're describing here. My initial suggestion from the limited information above would be to ensure that all Suspend Nodes had unique ResultRef values. I would also suggest that you review your Workflow and how it is constructed - if, as it appears, you are using multiple Suspend -> Await Expiry nodes in a Workflow that suggests that there would be a more efficient way to build the Process.

I have asked if any Developers could comment on this. I am, of course, honour-bound to point out that this is the whole point of Hornbill Collaboration - it allows your Users to see everything in one place without needing to resort to emails etc.

I'm not sure what the expectation is here? If the customer can see the list of potentially relevant documents from the Summary field, they can simply open the matching one in their browser while/after raising the Request. Adding the additional steps of selecting a Document to be emailed, switching to an email client, opening the email, downloading the attachment, and opening the attachment doesn't seem to bring additional value for me.

Unfortunately there isn't a "Wait for anything" option available. The initial difficulty that springs to mind is that the definition of "anything" will vary from Customer to Customer. I've tagged this as an Enhancement so that Development see it; this does not mean it will be accepted, however.

Hi @Ann When you say you "have created a field and labelled it 'Budget Owner'" is that a Custom Field? In my Contracts I already see a standard field for Budget Owner. Have you created your own, additional field? Either way I'm afraid I'm not currently aware of a bulk update option.

Although those roles are visible, the Knowledgebase Management has not gone live yet so will not be available in the Service Manager menu. Please keep an eye on the Roadmap, Forum Posts, and Release Notes for further progress.

As far as I'm aware the Roadmap updates when a Release is made, as that is when the status of the cards changes. For example the completed cards will move on and create space for incoming cards to move to in progress, etc.

Unfortunately that's not my forte, There's a TechNet article on it but there are probably easier ones to understand out there!

The way I would do this would be to ensure that the Users I wish to archive are moved to a specific Azure AD OU, and have a separate Import to set these Users to have an Archived Status. i.e: Joe Bloggs joins the Company Joe is added to the "IT Services" OU The Import Tool picks up Joe's details and creates a Hornbill Account Joe leaves the Company Joe's AD Account is moved to the "Leavers" OU The "Archive" import picks up Joe's account from and updates the values/status accordingly

That is correct, and the expected behaviour. You can see the full list of To: addresses by opening the email using the View Email option on the Timeline entry.

Without knowing how you have this set up it's difficult to advise, but presuming you are using the addProjectTask api then as far as Hornbill is aware this is "just a Project Task" created in the normal way, so you would have to have some information within the Task to identify it. If you're not using the External Reference field, this would seem to be the easiest option - so a Project Task with an External Reference would indicate it originated in an MS Project Online Project and the content would indicate which specific Project. Other options might be a Prefix/Suffix on the Name, some identifying content in the Description, etc. @AlexTumber and his team might have additional suggestions.

@MichelleReaney Unless they have a Forum account you can totally take the credit!

The short answer to this is "Any change to a Request" The list would be: A Timeline Post or Comment is Added, Edited, or Deleted The Status or Sub-Status are changed The Request is placed On Hold or taken Off Hold The Category is changed The Priority is changed The Urgency is changed The Request is Escalated An Asset or Asset Type is linked/unlinked A file attachment is added Customers or Connections are Changed/Added/Removed An email is sent A Request is linked/unlinked or a Linked Request is created The Request is Resolved, Closed, Reopened or has the Resolution Details updated A Member is added or removed A Workaround is set The Request's standard or custom fields are updated For Changes/Releases; the Request is scheduled/unscheduled