AntisamyNotificationSchedule - Move Notification Description as Attachment
Large content (>64k) in notificationtodescription table causes failure in backup/trimmed backup. The schedule's (AntisamyNotificationSchedule) job is to move large content from notificationtodesc table as attachment.
Below is the file attached to guide through the steps to reset the schedule.
Also, the same task can be performed using jar/fjar and invoking server:port/servlet/DebugServlet. Need to insert values in globalconfig. Check attached file for reference.
Note: Check whether proper entries are available in globalconfig table before starting schedule or invoking DebugServlet.
AntisamyNotificationSchedule and Invoking DebugServlet after putting these jars will do the same operation. So please perform any ONE operation with proper values configured. Difference is Servlet will run continuously (causes high CPU usage) while schedule will run as per design in off business hours.
- Nihal
New to ADSelfService Plus?
Related Articles
Issue : Description content in the notification shows unwanted text ( css texts ) after upgrading to 11138
Issue : Users are receiving system notifications for request module with the following content when $Description variable is added in the notification template. Issue occurs only when the end user sends the mail from Outlook desktop app ...
Update Requester from Request Description
Use case: When a request is submitted on behalf of a user via email, the request description contains the requester's full name. Script to update the ticket requester accordingly. Tested on builds: 14306,14500. Steps to follow: Go to Admin > Request ...
Query to show last conversation and last notification in a request ( MSSQL )
Tested in Build MSSQL (14306) Query SELECT wo.WORKORDERID "Request ID", aau.FIRST_NAME "Requester", wo.TITLE "Subject", ti.FIRST_NAME "Technician", longtodate(wo.CREATEDTIME) "Created Time", (select conversationdescription.description from ...
Notification script using Custom function in custom trigger
This is applicable from 10600 builds. From 10600 , Business rules dont have Email notification feature. The same use case be achieved through Custom triggers feature as mentioned below. Script to enable notification of request creation using custom ...
Incoming and Outgoing conversations with Attachment name and location (MSSQL & PGSQL)
Tested in Build PGSQL (14300) or MSSQL (14306) PGSQL & MSSQL: Incoming: (Referred as 'Conversations' in the database) select conv.conversationid "Conversation ID", conv.workorderid "Request ID", wo.title "Request Subject", aaau.first_name "Sender", ...