Script to auto-populate the task owner field with the technician who created the request
REQUIREMENT:
When a technician creates a request and a task is added under the request, the task owner should be the same technician.
TESTED IN: Builds 14503 (Postgres)
STEPS:
1) Under "Admin" > "Task Custom Functions," create a new custom function using the attached script.
2) Under "Admin" > "Task Custom Trigger," create a new custom trigger with the following conditions:
When a technician creates a request, and a task is added under the request, the same technician will be automatically populated in the Task Owner field.
New to ADSelfService Plus?
Related Articles
Script to auto-populate the "Estimated Efforts" of a task based on the "Category" and "Sub-Category" of an incident request
REQUIREMENT: When an incident request is created, a task should be automatically added to the request. In the created task, the "Estimated Efforts" field should be automatically calculated based on the Category and Sub-Category of the incident ...Script to Auto share request
1. Download MSP_share_Request.zip from the attachment, extract it, and paste the same under ManageEngine\ServiceDesk Plus MSP\integrations\Custom_scripts. # auto_share_MSP.py # functions.py # configuration.json 2. ...Query to show Request and associated task details (PGSQL & MSSQL)
Tested in build PGSQL (14300) and MSSQL (14306) PGSQL & MSSQL: SELECT wo.WORKORDERID AS "Request ID", aau.FIRST_NAME AS "Requester", wo.TITLE AS "Subject", pd.PRIORITYNAME AS "Priority", cd.CATEGORYNAME AS "Category", scd.NAME AS "Subcategory", ...Instruction to Change Worklog owner under All Request, worklog owner From Tech A to Tech B
Scenario Worklogs assigned to Duplicate user / Incorrect user need to change all worklogs under request to actual Technician. Step 1 : Navigate to Report - > New Query Report and execute the below query. Select workorder.workorderid ...Deluge Script to show request attributes in Task Subject / Description from builds: 10600 and 14306
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 ...