i think that this will become quite difficult. You have indeed that agent that could do something for you but the issue would be that you have the always the user which changes all the time. seen that you do not have his password it seems rather complicated to create this kind of action. certainly if they make progress on the ticket.
where is the Service Call ID sent to the VB script from the DB rule. Cmd file is created for each Service Call with unique name e.g. c:\sdactions\SC\SC97.cmd and the sdactions folder is shared on the SD appserver.
- In the e-mail sent we add a reference to the cmd file e.g.
- Created a DB rule which deletes the cmd file with a VB script when the Service Call is closed. This is so the sdactions folder isnt filled up with lot of files but only with the amount of open calls.