Skip navigation

Mobile is eating the world - smartphones outsold PC's for the first time in 2011 and it is estimated that a quarter of the world's population will have a smartphone by 2016. With the proliferation of smartphones comes the demand for new mobile applications.  As a developer building custom applications on ServiceNow mobile shouldn't be an afterthought. The capabilities of smartphones - location, camera, touch ID to name just a few can open up a whole world of possibilities on the types of apps you can build and the user experience you can deliver. The good news is that you have multiple options to build mobile apps with ServiceNow

1) Take advantage of the smartphone interface in the platform - The smartphone interface provides functionality to make your application functionality accessible in a mobile friendly fashion.  The form designer additionally allows you to define mobile specific views.  This may be sufficient for many custom applications where the focus is on enabling users of the applications to access a subset of the functionality easily through their mobile devices.

2) Build a native mobile application - These are applications that are custom built for a specific platform - iOS, Android etc. and access ServiceNow through APIs.  This approach has the advantage that the user experience and application functionality can be highly optimized by taking advantage of the capabilities of the device.  The disadvantage of this approach is the cost and complexity - developers will have to code to native APIs of these platforms and if multiple platforms need to be supported, it would mean building the application on each of the platform.

3) Build once on a container using HTML5, deploy to any OS - this approach is sometimes also called the hybrid approach.  Essentially, developers build on top of a container that abstracts away the differences in mobile OS and makes device capabilities available in an uniform manner.  Developers can write standard HTML5 code (JavaScript, CSS etc.) and call ServiceNow APIs to build the application.  Apache Cordova is a popular open source container that supports this style of development.

 

This year at #CreatorCon, nabilenayet a senior solutions consultant with Evergreen Systems is leading a hands on workshop to build a Conference Companion app using Apache Cordova and ServiceNow. confcompanion.pngIn teaching you how to build this app, you will learn how to access the device camera, location and contact list with simple javascript commands, and synchronize data to and from a ServiceNow instance.  He will also be covering general mobile design principles. 


If you are interested in attending, please sign up for this workshop at CreatorCon using the session builder.  If you have additional questions for nabil.m.enayet please post them below. 

For older, upgraded instances, if your Update Set Picker is not automatically updating its list of available Update Sets when you create a new one or close an existing one, the problem is with the "ui_update_set_picker" UI Macro.  Older instances, going back as far as Berlin, may not be upgraded properly, because, in order to hide the picker in your Production instance, you must set the Active flag to false and that means a change to the record.  That change marks it a custom record now and no longer upgradeable.  That record will always be viewed as a custom record each time you clone back to development, so will always get skipped on upgrades.


In order to fix it, you will want to revert the record to OOB in your production instance so it will be pushed down to dev during the next clone cycle.  To do this, select "Upgrade History" from the "System Diagnostics" application and find the latest upgrade you've performed and load the record:



Filter the "Upgrade Details" related list to show "File name = sys_ui_macro_49a50b9ca9fe3dba0059d0f944e412d1":



You should end up with 1 record showing in the list with a "Disposition" of "Skipped".  Open that record and click on the "Revert to Out-of-box" button.  This will upgrade the UI Macro to the latest version.  That will fix your production instance.


In order to temporarily (until the next clone) fix your development instance, where it really matters, first export the UI Macro record from the production instance as an XML file.  Then, select the "Default" Update Set in development and import that new XML file.  Now you have the latest file in development as well as production.


When you now turn the UI Macro on (in development) and off (in production), that change is no longer considered a custom change, so you will still get automatic updates to the macro.  This is because of a feature that was added way back in Calgary - Administering Update Sets - ServiceNow Wiki

*** Please Like and/or tag responses as being Correct.
And don't be shy about tagging reponses as Helpful if they were, even if it was not a response to one of your own questions ***

Want to understand how some feature of the platform works or why it works the way it does - just stop by the developer lounge. At  #CreatorCon we have a dedicated area where you can meet and interact with our product development engineers. We have identified the following five focus areas for the developer lounge

 

  • UI/UX - UI Development using UI pages, CMS, integrating other JS libraries etc.
  • Application Model in Fuji - application scoping, upgrading etc.
  • Building Applications - Application creation, team development
  • Domain Separation
  • Integration - REST, OAuth and best practices
  • Building an application for Store - certification and listing

 

The developer lounge will be open through CreatorCon.  Hope to see you there.

Welcome to a great new experience on the ServiceNow support system known as HI. Introducing the Customer Self-Service Portal!


When you log on to HI at hi.service-now.com, you'll see a sleek new look that matches our Fuji release and you'll have the most important tools you need to manage your instances all on one screen. Here's a quick look:


customer_portal1.jpg


(1) Receive important information

 

Important notifications are located at the top of the screen.


(2) Easily view instance availability and open issues


Your real availability statistics and list of open issues (incidents, problems, changes, and enhancement requests) are still easily available.


(3) Control all of your instances


Click Manage Instances to see key information about all of your instances listed in one page. Select different actions such as activating a plugin, cloning the instance, or requesting a version entitlement for the different individual instances.customer_portal2.jpg


(4) Managing upgrades


Manage your upgrades using the Instance Upgrade Management dashboard. This useful dashboard lists all of your instances, showing the current version, upgrade versions available, and any upgrades already scheduled.

customer_portal3.jpg

(5) Review alerts


Click a red badge to obtain information about alerts such as locked out users or upgrades in progress.

 

(6) Take care of user accounts on HI


Keep user information current, assist locked out users, activate and deactivate users as necessary, and edit user roles all in one spot.

customer_portal4.jpg

 

(7) View Service Catalog options

 

Service Catalog items and services are listed, including VPN requests, training registration, and a handy option for determining your customer administrator.

 

(8) Obtain support from ServiceNow

 

Use the Support option to view extensive documentation, enter the ServiceNow community to talk with other ServiceNow users, or file an incident.

 

(9) View the legacy HI portal

 

If necessary, use this option to view the legacy HI portal with the Application Navigator on the left side.

 

Note that ServiceNow Express users and ServiceWatch users will not see the Customer Self-Service Portal, but will continue to use the legacy HI portal.


ServiceNow offers more information about the new Customer Self-Service portal in our knowledge base:

 

 

 

 

 

 


Administrators have the ability to change the base system icons on their instance. When you are customizing your instance, you may be wondering where to find icons that you see in existing categories, especially top-level ones that appear in your self-service portal, such as your Service Catalog. These can quickly be found in your System UI. As an admin, you can easily modify and manage module icons and images to create a customized user experience unique to your company.

 

Modifying module icons in your instance:

  1. Navigate to System Definition > Modules.
  2. Select the module.
  3. Click the reference lookup icon.
  4. Select the desired image file from the existing images. To use a custom icon, see Creating a New Icon.
  5. Click Update.

 

Locating ServiceNow images in your instance:

  1. In the navigation filter, enter System UI > Images. Here you'll find a table of images that are stored as attachments, which come in handy if you need to upload an image to a service catalog item, for example.

Screen Shot 2015-03-26 at 12.54.23 PM.JPG

 

 

You can create or update service catalog items using the existing icons, or upload your own:

  1. Navigate to Service Catalog > Catalog Definition > Maintain Items.
  2. Click New.
  3. Enter the catalog item details, and select Click to add in the Picture field to upload your icon.
  4. Click Submit.

Screen Shot 2015-03-26 at 12.58.43 PM.JPG

 

Or you can go into an existing item to select the Image tab to update or delete an image:

 

Screen Shot 2015-03-26 at 1.00.30 PM.JPG

 

If you're uploading your own, use a 16x16 pixel image so it appears as an icon beside the item name in the catalog. If you use your own default icon to overwrite an image, this is stored in images/service_catalog/generic_small.gif. If you don't upload an image, the default icon appears beside this item.

 

So what happens if you're not seeing your icons at all?

 

If this is the case, you may try to do a cache flush to see the images:

  • instancename.service-now.com/cache.do

 

Make sure that you do not run a cache flush during business hours. Scheduled cache flushes, using cache.do, can affect overall performance and degrade system response times. Cache flushes are intended to prevent older data from interfering with changes and updates.

 

For related links, see:

Where are icons for Service Catalog Items stored in SN?

change service catalog icons

Icons are not visible

Defining Catalog Items

Jim Coyne

"Clear User Settings" Tool

Posted by Jim Coyne Mar 21, 2015

I've been meaning to share this functionality for a while, but I have not had the time until now.  It's a Form link UI Action on the User table, available to users with the "admin" role and to all users when looking at their own record:

_Screenshot.png

It's a quick way to reset a user's settings back to what they originally were when they first logged in.  It might be useful to give your "itil" users permission as well so your Service Desk techs can clear the settings for your users.  The user is asked to confirm the action before deleting records from the following tables:

  • Bookmarks [sys_ui_bookmark]
  • User Preferences [sys_user_preference]
  • List View customizations [sys_ui_list]
  • Tags [label]
  • Label History [label_history]
  • Notification Messages [cmn_notif_message]

 

Name: Clear User Settings

Table: User [sys_user]

Order: 100

Action name: u_clear_user_settings

Active: Checked

Show update: Checked

Client: Checked

Application: Global    (for Fuji and above)

Form link: Checked

Onclick: u_clearUserSettingsClient();

Condition: current.isValidRecord() && (gs.hasRole("admin") || gs.getUserID() == current.getValue("sys_id"))

Script:

//client function that runs 'onclick'
function u_clearUserSettingsClient() {
  var confirmMessage = "Are you sure you want to clear this user's settings?";

  //is this the user's own record?
  if (g_user.userID == g_form.getUniqueValue()){
  confirmMessage = "Are you sure you want to clear your settings?";
  }

  if(confirm(confirmMessage)) {
  gsftSubmit(null, g_form.getFormElement(), "u_clear_user_settings");   //MUST call the 'Action name' set in this UI Action
  }
}

//code that runs on server
//ensure call to server-side function with no browser errors
(function() {
  if (typeof window == 'undefined') u_clearUserSettingsServer();
})();

function u_clearUserSettingsServer() {
  //First, commit any changes to the record
  current.update();

  //get the record's sys_id
  var sysId = current.getValue("sys_id");

  var infoMessage = "Settings cleared - have the user logout then back in for the change to take effect.";
  if (gs.getUserID() == sysId){
  infoMessage = "Settings cleared - logout then back in for the change to take effect.";
  }

  //Clear Bookmarks
  var gr = new GlideRecord('sys_ui_bookmark');
  gr.addEncodedQuery('user=' + sysId);
  gr.deleteMultiple();

  //Clear User Preferences
  var gr = new GlideRecord('sys_user_preference');
  gr.addEncodedQuery('user=' + sysId);
  gr.deleteMultiple();

  //List view customizations
  var gr = new GlideRecord('sys_ui_list');
  gr.addEncodedQuery('sys_user=' + sysId);
  gr.deleteMultiple();

  //Clear Tags
  var gr = new GlideRecord('label');
  gr.addEncodedQuery('owner=' + sysId);
  gr.deleteMultiple();

  //Recently Accessed records/modules
  var gr = new GlideRecord('label_history');
  gr.addEncodedQuery('user=' + sysId);
  gr.deleteMultiple();

  //Notification messages
  var gr = new GlideRecord('cmn_notif_message');
  gr.addEncodedQuery('user=' + sysId);
  gr.deleteMultiple();

  gs.addInfoMessage(infoMessage);
  action.setRedirectURL(current);
}


It will then display a message to the user to logout then back in for the change to take effect.  Not 100% sure if that is necessary, but it doesn't hurt. 

 

If you want to give your "itil" users permission to clear settings as well, change the Condition field to:

current.isValidRecord() && (gs.hasRole("itil") || gs.getUserID() == current.getValue("sys_id"))


The "gs.hasRole("itil")" snippet will return true for "admin" users as well.

 

Please let me know if there are any tables that I missed.

*** Please Like and/or tag responses as being Correct.
And don't be shy about tagging reponses as Helpful if they were, even if it was not a response to one of your own questions ***

This year there is one more reason to attend Knowledge and that is to attend  CreatorCon the inaugural ServiceNow Developer conference.  Starting on Thursday, April 23rd and running through Friday afternoon, CreatorCon is packed with learning and networking opportunities. Here are a few things you can look forward to

 

Keynote by Pat Casey and Fred Luddy - Pat Casey, GM of ServiceNow platform business unit and Fred Luddy our founder will kick of the conference with their keynote - get ready to be educated and inspired to build the next generation of cloud applications.

 

Project Led Workshops - These hour and a half workshops led by the top experts on ServiceNow platform with give you hands on experience on the new Fuji application model, building a mobile application, CMS, Killer UX, Advanced scripting and a lot more.  The workshops are designed to give you the knowledge you can apply in your job right away.

 

Demo led breakouts - These breakouts are slide light and code / demo heavy to educate you on the newest features and best practices.  Topics include integration best practices, application testing, performance tuning, using APIs effectively.

 

Certified Application Developer Exam - Be among the first few to get certified as an Application Developer on ServiceNow platform  You can take the exam on site and we are waiving the exam fee ($150) if you take the exam during CreatorCon.

 

Developer Lounge - Grab a drink and discuss APIs, UI, Domain separation or any other platform topics with our product engineers and product managers.

 

HackZone - Release your inner geek by playing with Internet of Things (IoT) devices that are integrated with ServiceNow.  A P1 incident just doesnt have to change color on the screen, you can get it to light up a philips hue bulb.  Or have it get displayed on a pebble smart watch.

 

And attend a great party at the legendary House of Blues

 

And now for the best part - CreatorCon is absolutely free with your Knowledge registration.  Don't miss it  - the learning from this conference will make you a better developer.

If you are creating a record from a filtered list, you’ll notice that some fields on the record automatically populate based on the filter conditions. For example, if the filter on the Incident list is [Priority] [is] [1 - Critical] and you click New, the Priority field automatically updates. Here's what your new incident will look like:

 

 

Priority Critical.jpg

 

 

If you are using filter conditions with the = operator, all of your values with the = are taken by default when you click on the New button. This is an enhanced feature and designed to behave this way. If you remove the =, this will prevent these value from populating.

 

Knowing how to add or remove the right filter conditions can help you set the correct default values when creating a new record. To keep in check the different ways to set your conditions, follow the guidelines below.

 

How to set filter conditions:

  • The current filter is a hierarchical list of conditions, also know as breadcrumbs, at the top of your table.

left to right conditions.jpg

  • Breadcrumbs are ordered from left to right, with the far left condition being the most general and the far right condition being the most specific.
  • Clicking a breadcrumb removes all of the conditions to the right.

Breadcrumb.JPG

  • Clicking the condition separator (>) before a condition removes only that condition.

Separator condition.JPG

 

 

Finally, clicking, ALL on a table the table above, for example, removes all conditions and returns all incidents in the system. Use this to ensure certain fields are not  auto-populated when creating a new record.

 

For related links, see:

Using Filter and Breadcrumbs

New button takes default value

"More than the act of testing, the act of designing tests is one of the best bug preventers known."

-Boris Beizer

 

Everyone wants to test their software thoroughly, but deadlines, lack of resources, competing projects, and so many other demands always seem to get in the way of doing the very best testing possible. One way to get a handle on testing is to get better organized. Are you using email and spreadsheets for managing tests? There is an alternative - the new Test Management application in the Fuji release. Test Management enables you to create tests, group tests into cases and suites, write test plans, lead testers through execution, manage the process, and review results.

 

Creating tests, test cases, and test suites

Test suites contain test cases. Create test suites to logically group test cases together.

  1. Navigate to Test Management > Test Repository > Test Suites.
  2. Click New.
  3. Add a Name.
  4. Add a Description of the suite.
    test_management1.jpg
  5. Click Submit.


Test cases contain a single or several individual tests.

  1. Navigate to Test Management > Test Repository > Test Cases.
  2. Click New.
  3. Specify a Test Suite for the test case.
  4. Add a Short Description.
  5. If required, add Prerequisites.
  6. Click Submit.

 

Individual tests contain steps with an expected outcome. Tests are created on a specific test case.

  1. Navigate to Test Management > Test Repository > Test Cases.
  2. In the Short Description column, click a test case.
  3. On the Tests related list, click New.
  4. In Test, type the steps necessary for determining if a feature is working correctly.
  5. In Expected Result, add the information to determine if the test passes or fails.
    test_management2.jpg

  6. Click Submit.

 

Writing test plans

After you have test suites, test cases, and test plans, pull them together into a test plan. Users with the test manager (tm_test_manager) role can write test plans, assign test cases to the appropriate testers, and track progress.

  1. Navigate to Test Management > Test Execution > Test Plans
  2. Click New.
  3. Add a Short Description.
  4. Click Save.
  5. Do one of the following:
    • If you already have a test suite containing the appropriate test cases, go to Related Links, click Add Test Cases from Test Suite, select a suite, and click OK.
    • On the Test Cases tab, click New (you can follow the steps in the section above).
  6. Click Save.

 

Tips and Tricks when Using Test Management

 

  • To get a better sense of the overall testing approach, see Process Flow. You have a great deal of flexibility in what options you choose to use and the order in which steps take place. Create a process that works for you and your organization.
  • Test Management is part of the Project Portfolio Suite and can be used with other applications in the suite. For example, the project manager can create a test phase in the project workbench.
  • There are two roles associated with the Test Management application: test manager and tester. Give the test manager role to users to need control of process. Give the tester role to users that just need to perform tests and record results.
  • You must set the status of a test cases manually. The status of individual tests in a test case does not change or update test case status automatically.
  • If you use Visual Task Boards, you be pleased to know that a visual task board is automatically created for each test plan. Any tester assigned to a test case included in the test plan is added to the visual task board.
    test_management3.jpg

ServiceNow offers more information about Test Management in the product documentation:

This week we published a video that provides a tour of new features in the improved Fuji user interface.

 

We walk you through some changes made in the Fuji UI including:

  • Icons
  • Tooltips
  • Shortcuts
  • Additional system settings

 

 

For more information on the improved user interface in Fuji, see:

 

ServiceNow product documentation:

Navigation and the User Interface

Understanding Icons in the Interface

 

ServiceNow Knowledge Base:

Fuji UI Updates

 

ServiceNow Community:

https://community.servicenow.com/welcome

 

For general information about ServiceNow, visit the ServiceNow Website

 

Your feedback helps us better serve you! Did you find this video helpful? Leave us a comment to tell us why or why not.

If you are not receiving email notifications, there may be a simple reason this is occurring – you may not be set up to receive notifications. In any case, users have the ability to enable or disable email notifications on HI. If you are not receiving any or certain types of notifications, you should first check to see that your Notification settings are enabled in your HI user profile. If the Notification field is set to Disable, the system will not send you an email notification.

 

To check that email notifications are enabled on HI:

  1. In HI go to Self Service > My Profile.
  2. Check the Notification field to see is set to Enable.
  3. If disabled, select Enable from the dropdown to restore notifications.

 

Enabling notifications.png

 

Alternately, administrators can check to see if users are set up to receive email notifications:

  1. Go to User Administration > Users.
  2. Go into the user record and check that the Notification field is set to Send Email.
  3. If not, chose Send Email from the dropdown.

 

If you've actually created an event, the system won't send you a notification by default. For example, if you've assigned an incident to yourself, you won't get an email letting you know the incident was assigned to you.

 

To receive email notifications as event creator:

  1. Got to System Policy > Email > Email Notifications.
  2. Open the notification, and select the check box for Send to event creator to enable notifications.

 

Also see iris.geist latest blog post for a tip on using the "Send to event creator" ability. Troubleshooting email notifications - Send to the Event Creator

 

We recently added a bunch of new Knowledge Base articles around notifications in HI. Check out the new HI notifications resource page for a complete list of product documentation articles, Knowledge Base articles, community solutions, and troubleshooting and implementation videos.

Are you already using UI actions? Many ServiceNow customers use them in a variety of creative ways. If you are using UI actions in your instance, consider refining them and controlling when they appear and for whom. For example, you can show the Delete button on the Problem form only to users with the admin role instead of all users.

 

For those who are not using them yet, a brief definition. UI actions are elements such as buttons, links, or a context menu that you can add to a form or list. When a user clicks the element, some script is executed. UI actions help customize the user interface and make it more specific for individual users. Users with the admin or ui_action_admin role can create UI actions.

 

ui_actions1.jpg

 

 

How to limit access with conditions:

Many users limit a UI action by defining a condition. If the condition is true, the action is visible. (Note that leaving the field empty defaults the condition to true.)


Here is an example for the Delete button on a Problem record:

ui_actions2.jpg

In this UI action, the Delete button only appears on the Problem record if the problem is in Closed/Resolved state.

 

 

How to limit access with roles:

Combine conditions and roles to limit access to UI actions by user role. The syntax is: gs.hasRole('role_name').Here is an example again for the Delete button on the Problem record, but this time we are controlling access by role:

ui_actions3.jpg

In this UI action, the Delete button only appears on the Problem record if the user has the admin or problem_admin role.

 

How to limit access with views:

Another nifty way to control who sees a UI action is by including or excluding views using the UI Action Visibility related list. Note that if you do not include or exclude views, the action appears on all views. In this example, we are specifying that the Close Incident UI Action is only included (visible) in Advanced view:

ui_actions4.jpg

 

There are some great discussions the community about UI action visibility:

 

ServiceNow offers more information about UI actions in the product documentation:

The Knowledge Base is kept current with frequent edits and additions. Find out what is new and stay up-to-date on the latest ServiceNow Knowledge Base articles by reviewing the weekly KB digest.user interface.jpg

 

 

 

Recently added and updated articles on User Interface:

 

 

 

UI Actions


Add buttons, links, and context menu items on forms and lists, making the UI more interactive, customizable, and specific to user activities with UI actions. (Click to see all UI Actions Knowledge Base articles)

 

 

UI Policy


Create and manage the user interface with UI policies (Click to see all UI Policy Knowledge Base articles)

 

 

General User Experience Solutions


Find solutions to general ServiceNow user experience related problems. (Click to see all General Knowledge Base articles)

The Knowledge Base is kept current with frequent edits and additions. Find out what is new and stay up-to-date on the latest ServiceNow Knowledge Base articles by reviewing the weekly KB digest.

notifications.png

 




Recently added and updated articles on Notifications:

 

 

Email


Configure, diagnose and resolve issues with email and notifications. (Click to see all Email Knowledge Base articles)

 

SLA


Define a set amount of time for a task to reach a certain condition using Service Level Agreement (SLA) (Click to see all SLA Knowledge Base articles)

 

 

Processes, Policies, Procedures


Define the processes, policies and procedures to help Technical Support implement features and troubleshoot missteps. (Click to see all Processes, Policies and Procedure Knowledge Base articles)

The Knowledge Base is kept current with frequent edits and additions. Find out what is new and stay up-to-date on the latest ServiceNow Knowledge Base articles by reviewing the weekly KB digest.

scripting.jpg

Recently added and updated articles on Scripting:

 

 

 

UI Policy/ Client Scripts


Create and manage UI and client scripts with UI policy and client scripting. (Click to see all UI Policy/ Client Script Knowledge Base articles)

 

 

Web Services


Allow diverse HTTP-based applications to talk to each other with web services. (Click to see all Web Services Knowledge Base articles)

Have you ever had a situation where you've submitted a inquiry, incident, or change request to HI and for some reason your notifications on the inquiry aren't coming through? Or you're on a watch list for a change and aren't getting emails on the subject? We have compiled a treasure trove of information on how to set up and troubleshoot your HI email notifications, and we've done our best to leave no stone unturned. Click the link below and start browsing! And let us know if there's anything we might have missed. We've got your back!


All new: HI Notifications Resource page


Screen Shot 2015-03-09 at 11.26.28 AM.png

If you have stopped receiving update notifications for your incident or other ticket, this may because the size of the email notification exceeds the max limit. Often this can be the result of large work notes, which as part of the email notifications, continue to increase in size with each notification.

 

If the Additional Comments, for example, get extremely large, chances are you will eventually exceed the max-allowed limit. The email is then set to send-ignored because its size exceeds the value set in glide.email.outbound.max_body_bytes property.

 

To prevent performance issues, the system not only sets configured limits on the maximum email body size but also the total attachment file size and number of attachments per email. Administrators can modify the maximum values by using these properties. You can, however decrease the size of the notification without modifying the max set value.

 

To decrease email notification size on HI:

 

  1. Copy the existing Work Notes/Additional Comments.
  2. Create a new document with work notes and add them as an attachment to the notification.

 

Work_notes_notification.png

 

You should then be able to continue receiving notifications without deleting work notes or making other system modifications.

 

For more information about notifications on HI, see:

As part of the ServiceNow Fuji release, we have again given the UI a makeover and aimed to provide you with a more consistent, useful experience. The stylistic changes include new icons and color schemes throughout the platform, the Edge, and various applications. There are also more opportunities to personalize views, user-friendly reference and preview features, and improved spacing and readability in the layout. Here is a look at just a few of the cool changes made in Fuji.

 

Forms - Responsive design

Form layouts adapt to better accommodate a variety of window widths. For example, in the reduced-width window, columns are displayed closer together:

Updated field notations

Field status indicators are larger and bolder to better highlight mandatory fields.

 

Lists - Sort indicator arrow and detail row

The top of the arrow in a list view column now indicates the max value and the detail row allows you to put a wide cell, like short description, on its own row.



API changes - popups

The form elements now respond to a fluid container, meaning the size of the browser window tells the form elements what their maximum size should be. As a result, GlideDialogForm needs a width and height set before rendering. If a width and height are not set, it estimates how big to make the dialog and sets some maximum sizes based on the dimensions of the container in the dialog.

Note the difference between Eureka and Fuji:

Info messages

Bolder notifications have been implemented to emphasize the message on the form or list and the timing of many notifications has also changed. Sometimes an AJAX transaction triggers an info or error message in a business rule. These messages now show when the AJAX transaction completes instead of when the next page is loaded.

 

 

And that's not all, of course! To accommodate the new release, we have created a Fuji improvements page packed with info from all areas of Support. As always, don't hesitate to send us your feedback here, in the Knowledge Base, or in Product Documentation. Take a look and enjoy getting to know the new UI!

New Fuji Improvements

 

Screen Shot 2015-03-02 at 2.32.51 PM.png

Folks, we've got a good one this week that we know you're going to love - an all new User Interface (UI) Resource page! Our UI team has been hard at work recently creating and gathering this content for you and we hope it addresses most of the UI questions that might come up in your day-to-day business. Check out the landing page below and as always, please send us your comments here or directly on the landing page and articles within. We look forward to your feedback!

 

All new: User Interface (UI) Resources page


Screen Shot 2015-03-02 at 1.56.42 PM.png

Filter Blog

By date: By tag: