Maximizing MIM comms popups - some suggestions

 

There are a number of combined steps as a workaround that could be used to make the MIM popups larger:

 1) Minimise the left hand nav by clicking the arrow toggle button



2)      2) Expand the body text area of the MIM popup (may not be applicable to the SMS box)




3)       3) Click fn-F11 (on a windows laptop at least) to maximise the screen

 

Comments

Post a Comment

Popular posts from this blog

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 https://developer.servicenow.com/app.do#!/api_doc?v=madrid&id=r_GlideRecord-setValue_String_Object
Read more

variable advanced reference qualifier example

javascript: 'sys_idIN'+new hld_hr_functions().getHRRefQual('hr_openedfor_returner'); *************** script incl funcs: getHRRefQual: function(refQualID){ //--build up ref quals var sRefQualQuery=""; if (refQualID=='hr_openedfor_returner'){ //--called from here: /nav_to.do?uri=item_option_new.do?sys_id=271a5f781b766f00cee5ed7cee4bcb60 //sRefQualQuery="nameISNOTEMPTY^u_technical_user=false^" + this._DormantAccountUsers(); sRefQualQuery=this._DormantAccountUsers(); } return sRefQualQuery; }, _DormantAccountUsers: function(){ //--use below to query dormant accounts table var grDorm=new GlideRecord('u_dormant_accounts'); var sQuery='u_user.nameISNOTEMPTY^u_user.u_technical_user=false^u_user.last_login_time<javascript:gs.beginningOfLast3Months()^ORu_user.last_login_timeISEMPTY'; grDorm.addQuery(sQuery); //grDorm.addQuery('u_user.active=false'); grDorm.addNotNull
Read more

Running transform maps asynchronously

Some rough notes I took on running a transform asynch... Import set needs to be set to mode=asynch Look at the business rules for the sys_import_set and sys_import_set_row tables.  This is where the mode of synchronous is set when it's from SOAP, otherwise uses the default attribute value of asynchronous.  With some modifications or additional rules for specific import set tables as conditions you could set the mode before insert based on the target import set table. I'm not sure I follow when/how you were trying to run this code, but how about a BEFORE INSERT business rule that sets the mode? Name: Set Mode to Asynchronous Condition: 1.        current.data_source.name == 'My Data Source'   When: Before Insert: True 1.        current.mode = 'asynchronous';   schedule transformation take a look at Asynchronous Import Set Transformer Follow following steps for scedule load: 1. Activate "Asynchronous Import Set Tr
Read more