Unable to save Preventive maintenance tasks
Unable to update just one PM task with more than 300 tasks. When tried to save the PM task, it simply throws "User does not have sufficient privilege".
By default we would have restricted for these many tasks added in PM task. We can allow to add any of number of tasks by adding an entry in a file called security-requestaccess.xml.
1. Navigate to ManageEngine\ServiceDeskPlus-MSP\webapps\ROOT\WEB-INF\security and take a backup of the file 'security-requestaccess.xml'.
2. Download, extract the file from the below link and replace it under the above mentioned location.
3. Restart the application and check the issue.
NOTE: This fix is applicable for build 9400 and above.
Query to show PM task details and its next schedule and last ran time
Works in both MSSQL and POSTGRES SELECT swo.WORKORDERID "PM Task ID", adef.org_name "Account", sdo.name "Site", ti.SCHEDULE_TIME "Next Schedule Time", aau.FIRST_NAME "Requester", dpt.DEPTNAME "Department", ...
user does not have sufficient privilege
Found below error in the logs U13:26:20:252]|[05-07-2021]|[com.manageengine.zrmeinteg.framework.ZRSDPFrameWorkImpl]|[INFO]|: Server Exception in getting shared user and licence details ::: | ServerException (HttpStatusCode 403 Error Code: 7301 ...
Task related reports
Sample Output and headers present in this report Goto reports -> New query report and executes the following SELECT taskdet.TASKID AS "Task ID", taskdet.MODULE AS "Module", taskprior.PRIORITYNAME AS "Priority", taskdesc.DESCRIPTION AS ...
Unable to add/update Technician details ( For Builds 9408 & above)
When customer is trying to associate a technician having more than 300 Accounts/Sites/Groups, then in UI an error "User does not have sufficient privilege" error will be thrown. In the logs look out for the below error, ErrorCode: ...
Deluge Script to show request attributes in Task Subject / Description from builds: 10600
Requirement: To show the request field values such as Request Type, Status etc., or the additional field values in the Task subject/description. Use case: When a task is triggered from a request, it should contain the request details (configured) in ...