Victor

Yes.

Yes but actually no. No because that field is a date/time type of field, it will always store the time and the report will output the content of the field with no formatting. And Yes because you can theoretically use another set of fields, for reporting purposes only, where you only store the date part of the value.

It is sent to the email provided in the node. I would (like to) think the workflow designer will not just put any address in there? You would still know where the email was sent originally. If forwarding is an issue, you could question the forward with the respective person?

@NickH you can have the template entirely made of variables that pull information from the request... this way the user can customise the content from the request and then use the auto-task/custom button to send the email...

@QEHNick hmm..2 seconds.. does the generated report have have data in it?

@NickH how about custom buttons that can invoke an auto task (that will send the email)? Custom buttons can be used at any time, independent of the workflow...

@QEHNick might be that the query behind the report takes longer than 30 sec to execute. All queries are set to timeout after this time and if a query times out then it will have no results which means the report will also have no results...

@Alberto M what exactly you are looking to be implemented? It's been quite a while (4 years) since this conversation took place, many, many things changed, new things...

@NickH would the email be sent manually or automatically by the/a workflow?

https://wiki.hornbill.com/index.php?title=Contacts

@Berto2002 talking of obvious, let's get one out of the way. Subscribed to relevant services?

@Berto2002 there are options available to see the original email and any emails that have been applied to a request. They are not however "attached" but "linked". So there is the issue of them not being available as link once the email is removed. I cannot comment on if and how this can be addressed, I am simply not involved in development. So suggestions are something for product and development teams to consider and discuss.

@Berto2002 difficult to say why with this info... you probably know what I am going to say... https://www.hornbill.com/support/ ...

@Sam P you cannot change or, better said, format the date in a report. The reports are using whatever values are stored in the respective table in the database. Date/time values are always stored as GMT/UTC as this is used as a base of reference for formatting dates in the UI based on the user timezone and also used in email templates based on instance timezone. However there is no such formatting in reports (not yet anyway). You can theoretically have a formatted value in a report if you offset the date/time value (e.g. +1 hour) then store it in a custom field that you will specifically use for reporting (ideally will not be used for anything else as it is offset and will appear as "incorrect" in the UI and/or emails).

What about the workflow associated with the request?

@FUTSALCOACH difficult to say without looking at some examples. I would suggest liaising with one of the supported contacts for your instance to raise a support request with us.

What is this node configured to do? Is it what the name implies, updating the request timeline? Or some other operation that will (also) update the timeline?

@will.good The way this functionality works currently is that it will take the plain text part of an email and use that for the timeline entry. This is how the code was written for this functionality. There is no setting or switch or something similar to change how this works without changing the underlying code for this functionality. Technically anything is possible. However, there are quite a few challenges to use the HTML part of an email to create something. It is mainly the tags, the multitude of them, that they can appear in different places in a different order plus the aspect of differentiating what is an HTML tag that needs parsed and what is an HTML tag that is not part of the formatting. And that is just tip of the proverbial iceberg. I am in no shape or form a SME on this, I will let our product management and development teams comment on this further.

There is no automation functionality to notify (email) users when a task is assigned. It can be done by the workflow (as above) so the email node would be necessary here.

These can't be allocated automatically. License allocation needs to be processed manually.

@Martyn Houghton yes, should always return UTC time.

@Adrian Simpkins I can see why anyone can expect that behaviour however I still think it should be as it is now as it is a clear indicator that the role has been created as a platform role and "it only happens" to have rights from a specific app (such as SM)

guest.ui.app.com.hornbill.servicemanager.operation.defaultVisibility does not relate to a specific action. It applies to an "off hold" action and any other action that does not have a specific setting in regards to visibility (e.g. update or assign have dedicated settings for visibility) So, yes. As per above it will apply to any action that does not have a designated setting.

@Adrian Simpkins that is a platform role configured to have application rights. So it will appear in Platform section. Custom roles created in Service Manager will only be for Service Manager rights. The platform ones can have roles from multiple apps, unlike the roles created in specific apps which are only for that app.

@Tina.Lapere not really. It can theoretically be done IF the workflow would be in a permanent form of suspend. When eventually resumes it can check the reassignment and fires of an email. Again this is in theory and really not advisable as the workflow would be built more or less for this single purpose. So in practice, not possible.