Skip to main content

Service Portal: redirect from old portal to new portal

pull the following widget into your OLD portal home page to redirect to your NEW one:

admin can override if they wish to, and toggled on/off via a sys property pulled in via the server script.




function($scope, $location) { /* widget controller */ var c = this; if ( { var bProceed = false; if ( { bProceed = confirm('redirect to new portal?'); } else { bProceed = false; } if (bProceed) { c.url = "/new_portal"; $location.url(c.url); } } }


(function() { /* populate the 'data' object */ /* e.g., data.table = $sp.getValue('table'); */ data.redirect = false; data.redirect = (gs.getProperty('portal.old.redirect') == "true"); data.isAdmin=gs.hasRole("admin"); })();


Popular posts from this blog

URL link in addInfoMessage

var ga=new GlideAjax('gld_HR_ajax'); ga.addParam('sysparm_name', 'checkEmployeeNumber_hrProfile'); ga.addParam('sysparm_hrprofilenumber', g_form.getValue('number')); ga.addParam('sysparm_employeenumber', newValue); ga.getXMLAnswer(function(answer) { if (answer!='undefined' && answer!=''){ var navURL="<a style='text-decoration:underline;color:blue'" + answer + ">" + answer + "</a><img width='3' src='images/s.gif'/>"; var sMsg='The employee number entered already exists on another HR Profile ' + navURL; //alert(sMsg); g_form.showErrorBox('employee_number', 'error - please check'); g_form.addInfoMessage(sMsg); } });

GlideRecord setValue

setValue(String name, Object value) Sets the specified field to the specified value. Normally a script would do a direct assignment, for example,  gr.category = value . However, if in a script the element name is a variable, then  gr.setValue(elementName, value)  can be used. When setting a value, ensure the data type of the field matches the data type of the value you enter. This method cannot be used on journal fields. If the value parameter is null, the record is not updated, and an error is not thrown!/api_doc?v=madrid&id=r_GlideRecord-setValue_String_Object