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

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){

Get URL Parameter - server side script (portal or classic UI)

Classic UI : var sURL_editparam = gs . action . getGlideURI (). getMap (). get ( ' sysparm_aparameter ' ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); } Portal : var sURL_editparam = $sp . getParameter ( " sysparm_aparameter " ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); }