Steve Giller
-
Posts
6,478 -
Joined
-
Last visited
-
Days Won
268
Content Type
Profiles
Forums
Enhancement Requests
Posts posted by Steve Giller
-
-
The Request List view only shows columns from the Requests table.
Unfortunately if the field you require is not in that table, it will not be available to display in the View, or filter the View by.
-
2 hours ago, Berto2002 said:
My logica is that it's an integer field, '1' is an integer and the resulting field contents of '11' or '111' are integers so this should work.
Appending is a function that only applies to strings. This will absolutely not work. This is neither a bug nor by design, it's fundamental to the difference between a number and a string.
Pre-empting the next question, we do not guarantee that this idea will work for a string either (see previous discussions)
While the workflow is perfectly capable of appending text to a text (or varchar) field, using it in this manner conflicts with the codeless environment ethos and while there is no issue when using this function as designed - for example appending the Customer's name to the Summary field - there are scenarios where appending multiple values to the same field will not produce the desired results.
-
The tables containing the timeline are optimised for performance rather than searching, and reporting on these is not recommended.
I would suggest holding back on this report and utilising the HAi "Summarise Request" functionality once it is fully available to provide this information in a field that you can then report on.
-
I would strongly suspect that you've not used the correct endpoint, if that's the response.
-
I believe this is by design:
On 12/01/2018 at 11:16, David Hall said:The sub-status will only be updated from within the request if it is manually changed by the user, to make it more configurable (via BPM) there is no automatic updating or resetting of the sub-status when resolving/closing etc... this should be built into the BPM process ...
See the following post for further details:
-
1
-
-
Why would you not simply pause the existing Request until the loan expires, then email the borrower and the Request Owner that the equipment needs returning?
Or if you really need a separate Request, just Raise one from the Workflow, assign it to a Team with no Members (so no-one will see it and interact with it) then assign it to the original Owner when the return is due.
-
22 minutes ago, Estie said:
I am not sure if this is an issue with my device/ our network as currently I am the only one affected
That would suggest it's unlikely to be a problem with the Instance, as if the Instance were down no-one would be able to login.
You can always check the status from the webform to see if any issues are highlighted there.
-
It may be worth checking with your network infrastructure teams whether there have been any updates to firewalls or proxy servers that coincide.
In the meantime I'll feed back to Cloud.
-
1
-
-
Your Instance Healthcheck is showing all green, and none of our automated connection tests have flagged any issues for your Instance.
The issue in the linked post affected all users on every connection attempt for that Instance, and the underlying issue was permanently resolved, so this will not be related.
Can you confirm whether this is affecting all Users, a particular group (e.g. at a specific location, or remote workers only etc.) or does it seem random?
"Could not connect to Server" is normally (but not exclusively) literally correct and indicates an issue between you and Hornbill that is preventing a connection, so any additional information could assist our Cloud Team in trying to establish where the problem lies.
-
(I merged the double-post)
-
15 minutes ago, Sam P said:
Would I be right in saying that if the customer is removed after the Wait for Customer node is completed that it could proceed without one?
Reading around the question, you can lock access to the "Change Customer" action which will prevent the Customer being removed once assigned (apart from by a "Full Access" User)
-
@Stuart Torres-Catmur The Tool is designed to remove the emails from your Instance and provide them as files that you can retain locally without consuming Hornbill storage.
Once they are exported they are your files to process as you see fit, if you need to free-search the archives (either natively or via some sort of file-searching tool) this would be something you would need to investigate internally, Hornbill do not provide this.
-
There is no concept of "counting" in a Workflow, this would be most easily achieved by the Analyst using the "Copy Request" option, or with a Custom Button that duplicates the existing request from its details.
-
There's an action in place to improve the sorting on this that should appear shortly.
-
@JAquino Could you give some details, please?
I've just tested both setting and amending a Priority on my Instance and there were no issues.
-
4 hours ago, Giuseppe Iannacone said:
I'm unable to post an update on the timeline as customer
I very much doubt there will be a setting/API to say "This is the Customer" as that will be evident from the session context matching the Customer of the Request.
Are you asking because you've posted an update (in which case, what did you use?) and the Workflow did not move on?
I'm not sure what the correct one would be, but if it's the one I'm thinking of this is not publicly available.
-
This is the button you need, I think?
In my Instance there are 5 Services - I have favourited 2
-
Is the automated User the Customer of the Request?
-
Then the second scenario applies; while possible, this method is not practical.
-
The short version is:
Pull 6 months' data, store this in a table locally, or even a spreadsheet.
Pull the next 6 months' data, and then add that to the table/spreadsheet.
-
1
-
-
I'm not sure I understand the request, here.
A radio button presents a list of options and allows you to select exactly one - the initial request was about adding multiple teams so a radio button seems like the least suitable option.
If you're asking for a list of your Teams to select from, we have Customers with hundreds of teams to choose from and any kind of list would be completely unusable for them in this area.
-
I'm not sure what you're asking here?
API Key rules are generally required for things like Import Tools where a number of different APIs will be utilised by the Tool, and the Rules restrict the API Key to the required ones.
Raising a Request is simply calling an API - rules should not come into it here.
What you should be doing is establishing a session against a User who can Raise the Request (i.e. they would be able to do this via the UI) and raising the Request, then closing the session.
-
Unless I'm misunderstanding, I'm pretty sure you can do this ...
-
I've merged these two posts as they appear to be the same question.
Lock down service domain
in Collaboration
Posted
I think this documentation is probably the best starting point, assuming I haven't misunderstood your requirement.
If that doesn't answer your questions please post back with any additional queries.
It would be worthwhile joining the Hornbill Academy if you haven't already, there was a recent Academy Live which explores the Employee Portal in depth and the replay of this should be available now.