Updating custom computed fields

Applies to:

If you have custom computed fields that generate HTML that contains JavaScript, replace them with URL launcher fields.

For information about URL launcher fields, see Adding a URL launcher field.

For example, in releases prior to 9.0, the RCSA Alignment Helper computed field generated the following HTML:

<a href="#" onclick="openReport(report.tree.post.do?label=Current+Reporting+Period&mainNavReport=true&amp;submitAction=preview&amp;actionContext=preview&reportId=2196&resourceId=11574leftPos=0&amp;topPos=0')">RCSA Alignment Helper</a>

In 9.0 and later, the replacement is a URL Launcher field with the following default value:

${ 
	"labelKey": "orm.rcsa.alignment.helper.url", 
	"path": "/report.tree.post.do",
	"parameters": {
		"reportPath": "/_cw_channels/Reporting/Hidden Reports/ORM Custom Reports/RCSA Process Alignment Helper.pagespec",
		"reportingPeriodId": "$reportingPeriodId", 
		"resourceId":"$objectId" 
	}, 
	"popUp" : { 
		"windowAttributes" : "height=600,width=800,menubar=no,status=yes,toolbar=no,scrollbars=yes,resizable=yes" 
	}
}

If some of the URL arguments that are generated by the computed field were calculated, you can replace them by creating GRC Calculations and then referencing those output fields in the URL launcher configuration. See Configuring GRC Calculations.