Zia approval prediction failure even with customized data

Zia approval prediction failure even with customized data

Zia approval prediction is not working as expected even though the data is given under customized data.


The customized model will be considered for the prediction at first and then if it fails to predict, the default model will be considered.

Reference Ticket: 

Jar Compatibility :
    11140 SDP Build version

          • Related Articles

          • Zia prediction failure due to security statements at the front of email content

            Issue: Zia approval prediction fails when security statements are present at the starting of the mail content. Since we consider the first 100 characters and 2 sentences from the content, the approval comment given by the user was not considered due ...
          • Failure during Zia Reopen prediction process stops the mail fetching schedule

            When the requester replies to closed/resolved requests with empty content or if there is no proper content except the content of the parent mail, then no content will be available for zia reopen prediction process and an exception will be ...
          • Request Approval Details

            This report is used to view the historical details of Approved and Denied approval processes and their individual steps.We can also use this report to display all details for which an approval decision is pending.   To make any changes to a query, ...
          • How to implement dynamic request approval through custom triggers with configurable CSV file.

            This is a sample script written in Python to handle Conditional Approvals for Incident \ Service Requests, through Custom Triggers.More information about Conditional Approvals can be  found in the link here One of the advantages of using this script ...
          • Change approval

            SELECT chdt.CHANGEID AS "Change ID", chdt.TITLE AS "Title", orgaaa.FIRST_NAME AS "Change Requester", qd.QUEUENAME AS "Group", ownaaa.FIRST_NAME AS "Change Owner", catadef.CATEGORYNAME AS "Category", priodef1.PRIORITYNAME AS "Priority", ...