Update Request with another Group when the request is approved

Update Request with another Group when the request is approved

Use case:  
Assume a requester is requesting for an gadget asset and it requires approval from their managers.  This ticket needs to be moved to "Asset" group only when the ticket gets approved.  Depending on the availability of the requested gadget, the requester will be provided with it.

Prerequisites:
2. functions.py :  This package consists of all the functions that are used to handle the standard requirements of the customer.  Most repeated requirements are written as separate functions.  Depending on our usecase, we can include these functions in our script. 
3. configuration.json : This file maintains the configuration details of the installed server.  

Execution Steps:
1.  Extract the ZIP file under ..\ManageEngine\Servicedesk\integration\custom_scripts - folder.
2.  Edit the configuration.json and update the values.
3.  Configuring a Custom Trigger:  Go to Admin > Custom Trigger > give a trigger name > Execute the action - when the request is approved > execute script - py update_group.py $COMPLETE_V3_JSON_FILE  

                  New to ADSelfService Plus?

                    • Related Articles

                    • Script to update Request with another Group when the request is approved

                      Use case:   Assume a requester is requesting for an gadget asset and it requires approval from their managers.  This ticket needs to be moved to "Asset" group only when the ticket gets approved. Pre-requisite - Python should be installed in the ...
                    • Update Request with another Group when the request is approved - Deluge

                      Use case:   Assume a requester is requesting for a gadget asset and it requires approval from their managers.  This ticket needs to be moved to "Asset" group only when the ticket gets approved.  Depending on the availability of the requested gadget, ...
                    • Request violated by Group

                      This report used to find the group who violated the request. If the request/incident already has a violation and is reassigned to another group the new group assumes the violation instead of the group that the violation occurred. To make any changes ...
                    • Shared Request - Group

                      SELECT wo.WORKORDERID AS "Request ID", wo.TITLE AS "Subject", aau.FIRST_NAME AS "Requester", qd.QUEUENAME AS "Group", ti.FIRST_NAME AS "Technician", std.STATUSNAME AS "Request Status", qa.queuename "Shared to group" FROM WorkOrder wo LEFT JOIN SDUser ...
                    • Query to show how many times a ticket has “hopped” from group to group. (MSSQL & PGSQL)

                      Tested in build PGSQL (14300) and MSSQL (14306) MSSQL: SELECT wo.WORKORDERID AS "Request ID", mdd.MODENAME AS "Request Mode", qd.QUEUENAME AS "Current Group", aau.FIRST_NAME AS "Requester", ti.FIRST_NAME AS "Technician", cd.CATEGORYNAME AS ...