Script to set Request Technician as the Task Owner for all associated tasks - Deluge
Requirement:
Request technician should be set as the task owner for all available tasks.
Use case:
When the request is updated with the technician, all the associated task needs to be assigned to the same technician.
Python Equivalent: https://pitstop.manageengine.com/portal/en/kb/articles/script-to-set-request-technician-as-the-task-owner-for-all-associated-tasks
Steps to configure:
1. Download the attached scripts. Copy the contents into Request custom functions.
2. Goto Admin > Request Custom Function > Global Function > New > Paste the global function contents and save it with a name.
(Update the SDP configurations details in the global function)
3. Goto Admin > Request Custom Function > Custom Function > New > Paste the "CustomFunction_to_UpdateTaskOwner.txt" content and save it with a name
(Update the global function count according to your instance)
4. Configure the created custom function in a trigger to get executed every time a request is updated with a technician.
Note: From Global Function >> Copy the global_function_(count). Update the copied count in the custom functions.
New to ADSelfService Plus?
Related Articles
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 ...Script to set Request Technician as the Task Owner for all associated tasks.
Use case: Request owner should be set as the task owner for all available tasks (or only open) from the request menu option (or trigger) Prerequisites: 1. Python Installation Steps ...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 ...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", ...Scripts to automatically cancel request tasks when the request status is set to cancelled (when the task closure rule is enabled)
NOTE: In the attached script Owner and Group value is hardcoded, so the script works only when the group and owner name are configured in task closure rules(valid technician name and group name). If technician and group doesn't exist inside the task ...