Service Portal widgets

A widget has a server script that runs once and fills the data object, an HTML template rendered by AngularJS, and a client controller that handles interaction. The data object is the bridge between server and client.

The client calls the server again with c.server.update() or c.server.get(). Anything on input arrives in the server script as input, and anything on data returns to the client.

// server script
data.openCount = new GlideAggregate('incident');
// ...
if (input && input.action === 'refresh') {
  data.refreshedAt = new GlideDateTime().getDisplayValue();
}

// client controller
c.refresh = function() {
  c.data.action = 'refresh';
  c.server.update().then(function() { c.data.action = undefined; });
};

Declare an option schema so the same widget can be dropped on several pages with different titles, tables or filters. Hard coding a table name inside a widget is the fastest way to end up with five near identical widgets.

The server script runs on every page load. Keep queries narrow, use GlideAggregate for counts, and avoid loading a hundred records to show five.