Provide ability to terminate user processes
Our BBCRM is hosted by Blackbaud. Whenever a user has a runaway process our Helpdesk contacts Blackbaud Support, who then contacts Hosting to kill the process. Within BBCRM, the client with Sys Admin access or with proper security access should be able to identify the process and stop it. This will expedite turnaround time and alleviate issues from occurring due to backed up processes.
-
Guest
- Jun 29 2015
- Reviewed: Voting Open
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +77
-
Safely Kill Runaway Processes
Merged We would like a safe way to kill long running processes such as R68 without the potential that some data will be updated or corrupted.0 Reviewed: Voting Open
-
An option under the task of every process (especially the query export process) that allows you to kill a process.
Merged Currently if a change needs to be made to a query where an export process is needed, that change can't be reprocessed until the running export process either finishes or a ticket is submitted to Blackbaud and they kill the process on their end. In...1 Reviewed: Voting Open
-
add a method to stop Queues.
Merged Currently the only method to stop a large queue is to perform an application pool recycle or individually terminate process SPIDs from SSMS. This is very time consuming and an application pool recycle is not always possible in production environme...1 Reviewed: Voting Open
-
Allow an in-progress queue or business process to be halted
Merged It would be very helpful if we could halt a queue while it is running. Even better would be a dashboard that showed all business processes currently running, across all of CRM, and allowed them to be terminated.2 Reviewed: Voting Open
-
Add an option to cancel a running Business Process
Merged We have on several occasions had marketing efforts or exports or saving static selections run for up to 13 hours before they finally fail. Once they start, there is no way to stop them and they tie up system resources for every other process that ...1 Reviewed: Voting Open
-
Add a Kill/Stop/End Global Change Action
Merged In some cases a global change runs for longer than expected/wanted or enters a run-away state, or is executed by mistake. Add a feature to stop/kill the execution of the procedure and roll it back.1 Reviewed: Voting Open
Related ideas
Vote added. This would be useful.
Attachments Open full size
This would be extremely helpful. Presently we have to raise a ticket with Blackbaud, and it usually takes hours or overnight to get a process killed, meaning that it continues to cause performance issues for hours. Functionality to identify the process (e.g., provide a list of processes) and then kill one of them, could possibly be provided in the CRM Cloud Portal.
Attachments Open full size
This would be extremely helpful to us!
Attachments Open full size
This would be very handy functionality.
Attachments Open full size