question Re: Giving more Running Transaction time while save a record in Developer forum

Giving more Running Transaction time while save a record

subbarayudu — Wed, 04 May 2022 05:59:49 GMT

When I save a record (Vendor risk issue), it's taking lot of time even though internet speed is good. I'm getting a Running Transaction message on the top along with the time in seconds. Here i found the BR which effect the this Running Transaction time.

Could you please let me know what needs to be done in the BR.

After insert and update on BR on --- 'sn_vdr_risk_asmt_issue' Table

Re: Giving more Running Transaction time while save a record

Community Alums — Wed, 04 May 2022 06:05:47 GMT

Hi @subbarayudu ,

To determine what is taking so long, start by going to System Logs> Transactions and see if you can identify anything running for a long time (about the time you canceled the timer.)

Also, Please navigate to Active Transactions (All Nodes) and then you could find the list of current active transactions and time taken by each.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

Re: Giving more Running Transaction time while save a record

Kalaiarasan Pus — Wed, 04 May 2022 06:35:50 GMT

I dont know what you are trying to do but whatever you are doing seems incorrect. You are querying all the company records and updating the count for each record in every update. Is that what you are trying to do?

Re: Giving more Running Transaction time while save a record

subbarayudu — Wed, 04 May 2022 07:43:09 GMT

The field "Open Issue Count" would calculate the number of Vendor Risk Issues
where the Status(state) field is not in Closed Complete, Closed Incomplete, or Closed Cancelled) and populate that row count value in core-company form.

Re: Giving more Running Transaction time while save a record

Kalaiarasan Pus — Wed, 04 May 2022 08:05:06 GMT

I am guessing you need to add this line before first query so that you can get the corresponding company only instead of everything.

gr1.addQuery('sys_id',current.vendor);

Re: Giving more Running Transaction time while save a record

Ankur Bawiskar — Wed, 04 May 2022 08:10:56 GMT

Hi,

why not make the BR as Async Insert/Update?

Also check suggestion mentioned by Kalaiarasan

Regards
Ankur

Re: Giving more Running Transaction time while save a record

subbarayudu — Wed, 04 May 2022 11:09:40 GMT

using getRowCount in server side script is a health scan finding under performance risk category. This likely also needs to be addressed. How to use Glide aggregate in the above script

Re: Giving more Running Transaction time while save a record

Ankur Bawiskar — Wed, 04 May 2022 11:29:14 GMT

Hi,

something like this

(function executeRule(current, previous /*null when async*/) {

	// Add your code here
	var gr1 = new GlideRecord('core_company');
	gr1.addQuery('sys_id', current.vendor);
	gr1.query();
	while(gr1.next()){
		var vendorCount;
		var agg = new GlideAggregate('sn_vdr_risk_asmt_issue');
		agg.addAggregate('COUNT', 'vendor');
		agg.addEncodedQuery('stateNOT IN3,4,7');
		agg.query();
		while (agg.next()) {
			//do things on the results
			vendorCount = agg.getAggregate('COUNT', 'vendor');
		}
		gr1.u_open_issue_count_1 = vendorCount;
		gr1.update();
	}

})(current, previous);

regards
Ankur