ericgilmore
Kilo Sage
In response to Daniel Billing

‎04-22-2019 01:58 PM

The parent RITM

0 Helpfuls

brianlan25
Kilo Patron

‎04-22-2019 01:27 PM

My question is this really a requirement that needs to be implemented?  Are there really that many people not wanting to use what is available OOB?  When I get requirements like this I always ask them questions. 

1.  Why do you need this when it can be done this way?

2.  What are the business requirements for this that are not fulfilled by the OOB functionality?

To me personally there is no good reason to put a URL just so they have a direct link when they can just use the preview and click or ctrl + click on the open record button.  Next thing you know they will be asking that for any of the fields that are reference so they can just click on a link that directs them to the requested_for record.

You may want to take a look at this blog by Chuck Tomasi (Ask Why)

ericgilmore
Kilo Sage
In response to brianlan25

‎04-22-2019 02:01 PM

Brian,

 

You're absolutely right and I absolutely did ask why and pointed out exactly what you mentioned. It turns out, 2 clicks is too many for this particular user. 🙄

Thank you for the article. Still, what am I missing on this? Shouldn't this be simple?

0 Helpfuls

brianlan25
Kilo Patron
In response to ericgilmore

‎04-22-2019 02:52 PM

If it is a particular user unless they are the president of the company I defiantly would not do it and I would hope that your management will back you up on that.  However the only way I could think to do this was with the following.

1.  Create a new filed of type URL.  I called mine RITM URL.
2.  I used a UI Policy to make it read only and an ACL of type list edit to make it so someone cannot add it to their list layout and edit it.
3.  I created a Business rule on the sc_task table that is after insert no conditions since we want it on all task.  The below code creates the URL for you.

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

	// Add your code here
	var url = gs.getProperty('glide.servlet.uri') + "sc_req_item.do?sys_id=" + current.getValue('request_item') + "&sysparm_view=";
	current.u_ritm_url = url;
	current.update();

})(current, previous);

View solution in original post

ericgilmore
Kilo Sage
In response to brianlan25

‎05-09-2019 06:50 AM

What I ended up prototyping were 2 things. This solution and the creation of another form view for sc_task in which I added a section with fields that referenced the parent RITM.

 

They really seemed to like it, but no decisions have been made to move forward with it just yet.

0 Helpfuls