Steve Giller

Hi @EWA You can use the Cloud Automation's date utilities to cater for that, but it's a bit cumbersome. If you are looking for extended features on Authorisations the the full Authorisation node (that requires a Collaboration License) may be what you need.

If I can refer you to Gerry's response On another thread for a complete answer: The short answer is that if it's not on the Hornbill Documents site then it is not intended for public use.

Application is Mandatory, setting that would be my first step. Also, I'm not sure how you've managed to have the language parameter blank, as this is a dropdown with no empty option, but I'd ensure that was set also.

What additional filtering are you looking for? It's probably more sensible to ask to have them added to the UI than to resort to digging around in Database Direct.

Timelines are not optimised for searching, they are extremely complex and have large numbers of entries, some of which are intended for restricted audiences. If there is a code, or other piece of information, that you would regularly need to search for I would strongly recommend storing that in a Custom Field for ease of access.

Have you considered Timesheet Manager?

If you're using On Hold Until you can simply use the raw value from the Date Picker by selecting that answer as the variable. Regarding the issue, I suspect it's that your input format does not match the format of the value in h_custom_23

That would probably work, however the Wait for Status Change node itself outputs the new Status: so it's more efficient to test on that.

Firstly, I think the value should be "open" rather than "status.open" Secondly, it's difficult to give any more detail without seeing how you get to the decision node, as that will affect what it's deciding.

2023-12-18 19:30:00 is not a valid Date/Time value: You will need to use the ISO format Date/Time string as detailed in the help popup/tooltip in order to make this work. I would also recommend using the Place Request On Hold option followed by a Suspend->Await Request Off Hold node rather than the Await Expiry, as should the Request not resume at the expected time for any reason you have the option of taking it off hold manually.

You will want to test this by having someone assign it to a Team they are not a member of, or someone who is not in your Team assigning it to your Team and ensuring you do not have the Request open in any tab/browser window. You don't get a notification to tell you that you did something, it is assumed that you're already aware. Likewise if you have the Request open it is assumed that you can see the change and do not need notifying.

Apologies, I'm slightly confused by the wording here. If your Single Sign On account has been suspended you would need to raise that internally. If your Hornbill account is suspended then someone with Admin access would need to navigate to Admin->Platform->Users, and open your account, and change the "Status" setting from "Suspended" to "Active" I've moved this to System Administration as it is not related to the Live Chat app.

I've merged some threads here which are all asking to have a node for Asset actions based on a known Asset ID

If that's what you've configured, that's what must be too long. You'll either need to ensure you truncate it with one of the String Utilities, or post it to the Timeline instead to see what the message being returned is. This error will be from Microsoft Teams, so Hornbill will have no control over its content.

Their Manager (as recorded in Hornbill) will be able to see their Activities from the "My Activities" screen, by changing the dropdown to User and entering the User's name.

@Adith You have created a Request Notice with text that has more than 255 characters. Reduce the number of characters to remove this error.

This is an advanced setting, so with the Include Advanced Settings checkbox cleared it won't appear by default. If you use the search function: then the relevant filters will be automatically checked, so putting membersTeam into the search will find it:

I would strongly caution against relying on it.

That suggests there may be an issue in the Capture, I'd review that first.

What is in field_9_value? My first troubleshooting step would be to post that to the Timeline so you know exactly what you are passing as a parameter.

That information is not stored, as it's an ambiguous value - is this assignment to a Team, a User, the initial assignment, the most recent assignment; if the most recent assignment does that replace the initial assignment - if so does that occur for a Team assignment, User assignment or both ... etc. If you need to create a view for this you'll want to specify your own criteria, use those to keep a Custom Field populated, and filter on that field for your View.

"Chaining" multiple Asset Forms is not something that is currently available, and I'm not aware of plans to introduce this at present.

That's not strictly true - the resent email will be a new Authorisation with a new link, so if the Authoriser receives the second email but clicks on the link in the first email then they will just see a message saying that it's expired. From experience, this may cause an issue if your recipient is using a client like Gmail that combines emails from the same address with the same subject into one conversation and they aren't familiar with how that works.

I can only usefully refer you to Gerry's post on another thread: Which I can summarise by saying if it's not visible on the Hornbill Documents site then it's not supported. Additionally (and I'm happy to stand corrected if Development need to do so) my understanding is that we have completed the removal of php from the platform, which would explain the link you posted above not working - and it appears this is based on a 3 year old thread, so it's quite likely that information is out of date.

If you're referring to exporting a Request List View (please remember that these are not reports, it's just a list of Requests that you can filter) then no - Linked Requests are not stored in the Requests table, and that is what the View is built from. You can write a Report to do this, the relationships between Requests are stored in the h_sm_relationship_entities table.