Product Updates

4me’s Webhooks API has been extended to allow organizations to build near real-time integrations that use the time entry data in 4me to update their financial application.  This is especially useful for managed service providers (MSPs) that use 4me’s time entry data as input for the invoices they generate for their customers. To make it […]

It has been a while since new fields became available for 4me’s email templates.  A new field has just been added, though.  It is the Supplier request ID field. When an organization has set up a 4me account that is used only as an integration point for one of its external providers, it can be […]

A new parameter has become available that allows administrators and account designers to define automation rules that look up the person who is currently acting as the coordinator for a team. This parameter makes it possible, for example, to define an automation rule that causes a notification to be sent to the team coordinator when […]

A new option has been added to the ‘Contact Details’ section of person records for chat links.  This new option makes it possible to add a chat link for Microsoft Teams.  The option is called ‘Teams’. The syntax of the link that will open a Teams chat conversation with the person should be defining as […]

4me’s SCIM Provisioning capabilities make it easy for organizations to automate the maintenance of their employee information in 4me by linking their 4me account with their identity provider, such as Azure AD, Google SSO, Okta, OneLogin, etc. When the configuration of an identity provider is updated, however, the link between a SCIM user record in […]

Many customers have asked for the ability to filter the request views and reports by the person for whom a request was submitted.  To make this possible, the Requester filter has been added.  This filter looks at the person who is selected in the Requested for field of each request. In addition, the following three […]

Two more filters have become available for filtering the SLA reports that are available in the ‘Reports’ section of the Analytics console.  The first makes it possible to limit the affected SLA records that are included in a report to those that are linked to a requester from a specific region. Specifically, the ‘Requester organization […]

The’Reports’ section of the Analytics console provides quite a number of reports that are based on the Affected SLA records.  These reports can be found easily by entering  sla  in the Search box above the list of reports. What is new is that an additional filter has become available that allows these reports to be […]

Even though requests can only be related to a single service instance, an incident in one service instance may actually affect multiple service instances.  That is why it may be more useful for organizations to filter their views, reports and dashboards by an affected service instance, rather than the service instance that is linked to […]