Skip to main content

ServiceNow Demand on mobile: certain fields not available

 

 I am the support engineer who will be assisting with your Case.

Issue:
Unable to select List type field and Date type fields for UI Parameters for the Mobile App.

Investigation Summary:
List (AKA GlideList) type fields are currently not supported in the Mobile Apps, so these type fields are intentionally not available. I did find PRB1337482 that discusses--
"PRB1337482: Glide List/WatchList Not supported in Mobile UI parameters"

PRB1337482 was closed stating that it would be a new feature request. I also found the following Enhancement Requests asking for this feature as a UI Parameter type:

https://community.servicenow.com/community?id=view_idea&sysparm_idea_id=fe483d581b0bc850ada243f6fe4bcb95&sysparm_idea_table=x_snc_com_ideation_idea&sysparm_module_id=enhancement_requests



https://community.servicenow.com/community?id=view_idea&sysparm_idea_id=31ce652bdbacd150ca6fdb85ca961951&sysparm_idea_table=x_snc_com_ideation_idea&sysparm_module_id=enhancement_requests



One important note on that last link-- it's possible to use List type fields with Input Form Screens:
----------------
While a UI parameter mapping does not have the option to map list type fields, this requirement can still be fulfilled using a "Input Form Screen" (formerly known as Parameter screen):

https://docs.servicenow.com/bundle/sandiego-mobile/page/administer/tablet-mobile-ui/reference/parameter-screen-var-attr.html


----------------


For Date type fields, these should work with UI Parameters. The 'Input type' would just be 'Text' and the associated mapped Item Parameter(sys_sg_item_parameter) would have the type 'Date'. There should be some Out-of-Box examples of these as well.

Next Steps:
Please review my findings on these 2 Field Types for UI Parameters and let me know your thoughts.
If the Date field still is not working, can you grant SNC Access in an affected instance to the following user for further investigation?: ethan.xxxx


http://www.servicenow.com/support/contact-support.html

 

Comments

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' href=hr_profile.do?sysparm_query=number=" + 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 https://developer.servicenow.com/app.do#!/api_doc?v=madrid&id=r_GlideRecord-setValue_String_Object