This is a tool to assist you in closing orphaned tasks and processes in ServiceDesk & Workflow 7.1. It doesn't not delete any entries from your database. This process will simply complete any active tasks and close the associated process. It properly handles closing Change, Incident, & Problem processes. It will also handle EM processes along with any default processes that are generated by Workflow. It does not work with custom projects that use custom tables for their data storage.
The project will allow you to search for the process by Title, Process ID, or Description. As searching the description field can be rather intensive a check box on the form is provided to enable or disable this functionality. You can select multiple processes at one time to improve efficiency.
The project has been designed to be published and added to your Service Catalog if so desired. You are required to be a member of the Administrators group however to run the project.
You will need to modify the connection string project property to match your environment.
All of the rest of the instructions are included in the package.
I hope this is helpful for all.
The ServiceDesk 7.5 version of the project can be found here.
http://www.symantec.com/connect/downloads/close-processes-servicedesk-workflow-75
NEW: SD.Bulkclosure For Servicedesk and Workflow 8.1 https://www.symantec.com/connect/downloads/sdbulkclosure-servicedesk-and-workflow-81
Closing Processes In Servicedesk 7.5 https://www.symantec.com/connect/downloads/closing-processes-servicedesk-75
Close Processes in ServiceDesk & Workflow 7.5 https://www.symantec.com/connect/downloads/close-processes-servicedesk-workflow-75
Great search but I need to narrow it down to really only search close code 'Closed Orphan'
How can I do that?
Thanks
jen
TGiles,
Is it possible for you to recompile this project for SD 7.1 SP1? It throws errors when trying to open the project and after I copied the custom DLL files to the shared libraries folder.
Thank you very much! The project works great now. I used the exact connection string from the local.orm.
your connection string will look something like this:
Data Source=ALTSQL;Initial Catalog=TPS_CMDB;Integrated Security=SSPI;
However, if you want to get the exact connection string for your environment, open up the logviewer, click on the SYMQ Configuration Tab, and then click on the SymQ_Local_Defaults option on the left. In the list find the local.orm option and double-click on it. The top row will be your connection string. Highlight it and copy that to your project properties and you will be set.
My SQLServer name is=ALTSQL
DB Name is = TPS_CMDB
How do you update the connection string under the properties tab?
Data Source=soundwave;Initial Catalog=PM_Reflector;Integrated Security=SSPI;
Do I change Data Source="Name of SQL Server"?
noodleNT,
Sorry for the slow reply. Yes the connectionstring properly is connecting to the process manager database. I created a custom component to only pull specific pieces of information when you first perform the search to help minimize memory usage.
This worked well for me on SD7.5 running in debug mode from the Workflow Editor. As TGiles points out you need to update the connection string for your environment.
We don't use ServiceDesk here but we use Workflow. It looks like for the most part I should still be able to use this. However, I am not sure what your ConnectionString is actually connecting to. Is that the processmanager DB?
Thx a lot.
I'm going to test it.