Configuration improvements
The following configuration improvements have been made.
Handling of incoming emails for archived cases improved (#666156)
The handling of incoming emails for archived cases has been aligned with the behavior for closed cases. Previously, emails sent to archived cases were appended to the case, which could lead to unintended modifications.Now, archived cases are treated similarly to closed cases. The default script for email routing, NimhIncomingMailRouting.groovy has been adjusted accordingly.
Additionally, from an API perspective, archived cases are now protected against modifications in the same way as closed cases. However, archived cases technically retain an open status, which means they will appear in searches for open cases.
You need to adjust your NimhIncomingMailRouting.groovy script manually to make this change functional. Add ticket.isArchived()) to the condition which controls whether the mailToClosedTicketScript is executed next.
Log level for warnings about missing translations during workflow deployment changed (#666709)
When deploying a workflow in ConSol CM, warnings about missing translations were written to the server.log file for every workflow element which did not have a localized value in the default language. This information is now logged at DEBUG level to the workflow.log to reduces unnecessary warning messages in the server log.
Translation service via LLM improved (#666749)
The translation service via LLM has been adjusted to avoid errors which occurred when the LLM did not return a JSON object. The translation prompt has been adjusted by defining the expected response format more clearly.
You can add the following line to the section *RESPONSE FORMAT (strict):
Return only valid JSON. Do not include backticks, code fences, comments, or any extra text.
In addition, a new system property, translationService.llm.jsonResponseEnabled, has been introduced to force the LLM to return a JSON object. Only set it to true if you are experiencing problems, as this setting might not be supported by all LLMs.
The description of the existing system property translationService.llm.jsonSchemaEnabled has been adjusted to clarify that it cannot be used with OpenAI due to compatibility issues. This property forces the LLM to return a JSON schema, which is not supported by all models.
Database settings optimized (#667075)
The XML configuration files cm6-mssql.xml and cm6-dwh-mssql.xml have been adjusted by setting sharing of prepared statements to false in order to avoid seldomly occurring import problems.
Scene for CM/Ticketing updated (#667606)
The scene for the CM/Ticketing product, which can be selected when setting up a new ConSol CM system, has been updated to use several new features introduced in this version.