Fix - Add conversation only based on id in the subject

Fix - Add conversation only based on id in the subject


Recently, many customer have asking for a requirement to add conversation to request only when the request id is present in the subject of the mail in the desired format. Meaning, conversation addition shouldn't add based on mail headers like 'InReplyTo' or 'References' headers.

How to achieve this?

1. Execute the below queries in the application database (How to connect to database? -

1. update globalconfig set paramvalue='false' where category like '%EMAIL_PROCESSING%' and parameter like '%AppendOnRequestReferences%';

2. update mailconfig set paramvalue='false' where category like '%EMAIL_PROCESSING%' and parameter like '%CHECK_REFERENCES_AGAINST_NOTIFICATION%';
Both the queries are to disable the conversation addition based on "References" mail header.

2. After executing the above queries, kindly place the attached fjar file (check the below table for your build's compatible fjar file) under <server_home>\fixes\ directory (For eg. If the application is installed in C:\Program Files\ManageEngine\ServiceDesk, then create a new folder with name as "fixes" (case sensitive) and place the fjar file under the "fixes" folder)
3. Restart the application service once.
4. Wait for the issue to reoccur. 
5. If it re-occurred, kindly share us the logs for analysis (You can use our FTP link to upload -> Mention the product as "ServiceDesk Plus" and ticket id as <your_ticket_id>)

Compatible Fjar files:

Compatible fjar file name

                    New to ADSelfService Plus?

                      • Related Articles

                      • Report on Conversation

                        This report gives an overview of all Conversation of Technician and requester.  To make any changes to a query, refer to the KB article below. SELECT ...
                      • Dynamic checklist based on field values

                        Requirement: Based on the answers provided for resource questions / request additional fields, dynamically a checklist has to be associated to the request UseCase: When an alarm is received indicating an issue with a server’s performance, with the ...
                      • Update Change Impact based on Selected Assets Business impact value

                        This requirement includes 3 global functions, 1 change custom action and 1 change custom trigger.   Step 1: getConfiguration Global Function   1) Go to Admin ->  change custom function -> global function-> Add new --> Mention function name and Return ...
                      • Dynamically add CAB based on Risk field value

                        Requirement: Based on the Risk field value chosen, a set of CAB approvers have to be added to the Change UseCase: There will be different sets of CAB approvers available and when a Change is created with ‘Low/Medium’ risk a set of CAB approvers have ...
                      • Mail Fetching: Subject Contains Unwanted Characters and Garbled Text

                        Issue: We use MIME for processing emails obtained from EWS. Unwanted characters and garbled text are present in the subject when fetching it from the MIME after decoding. Восстановить стату�� ACSID\WSID в базе Omega [2L] Ð Ð±Ð½Ð°Ñ Ñ Ð¶ÐµÐ½Ð¾ ...