Setting the Request Due Date as the Schedule End Date for All Associated Tasks
Requirement:
Request DuebyDate has to be set as the schedule end date for all the tasks associated to the request.
Steps to follow:
- Goto Admin > Developer Space > Global function > New > Paste the content from the attachment Global function_4.txt and save it with a name.
- Update the URL and integration key in the script.
- You can get the integration key under Admin > Integrations > Integration Key > New
- Please use an integration key with admin privilege, as there wont be any role related permission issues.
- Update the integration key in the global function.
- Incase of older builds you can use the techniciankey with admin privilege.
- Go to Admin --> Task Custom Functions. Create a new function.
- Refer to the attached script. (UpdateScheduleEndDateForAssociatedTask_fromReqDuebyDate.txt.)
- Update the global function count in the script as per your instance.
- Configure Task custom trigger to get executed on every task being created in request module.
New to ADSelfService Plus?
Related Articles
How to close associated incident requests of change request automatically
This post describes the use of a python script to close change that are in a specific stage using Custom Schedules. Use Case: There may be a scenario where number of Change Requests that have got closed and the associated incident is still in open ...Update schedule start and end time for associated task from request additional field
Requirement: When a request is submitted, the task completion date is saved as an additional field in the request. This must be reflected in all associated tasks. The schedule start date must be set to 7 days before the date configured in the ...How to populate request details on associated tasks.
This sample script is used to update request field values into tasks associated with request templates The Request details are stored as a JSON Object in a file and its path is provided as input to the Script. This can be used in the application ...Query to show Problem details, timespent and its associated request IDs (MSSQL)
Tested in MSSQL build (14306) SELECT "prob"."PROBLEMID" AS "Problem ID", "prob"."TITLE" AS "Title", "statdef"."STATUSNAME" AS "Status", "orgaaa"."FIRST_NAME" AS "Reported by", Cast((((sum(ct.timespent))/1000)/3600) as varchar(20)) +'Hrs ...Problem and Associated incidents with Request id
MSSQL SELECT "prob"."PROBLEMID" AS "Problem ID", max("prob"."TITLE") AS "Title", longtodate(max("prob"."REPORTEDTIME")) AS "Reported Date", max("prob"."DUEBYTIME") AS "DueBy Date", max("orgaaa"."FIRST_NAME") AS "Reported by", max("probf"."UDF_CHAR1") ...