BLOG

After a request has been completed, 4me sends out a notification to ask whether the requester is satisfied with the way the request was handled. In the past, when a requester ignored this [...]

A minor feature has been added to the REST API for changes. This API now allows the manager of the change to be set when a new change is created. In the past, the API user would always become the [...]

People may have already noticed that the attachment file size limit has increased significantly. In the past the maximum size of an attachment, including videos and files in the Media Library was [...]

When a specialist clicks on him/herself in the far right of the toolbar and selects the option ‘My Profile’, it used to be possible for this person to go to the ‘API’ [...]

When a configuration manager registers a new product, the name of this product gets filled out automatically in the Name field when its brand, model and category are specified. The REST API for [...]

People who have the Project Manager role are now able to see the time entries that their colleagues added to the tasks of the projects they manage. Similarly, change managers are able to see the [...]

Sometimes an SLA is no longer considered affected by a request. That happens, for example, when the provider that is responsible for the SLA has rejected the request.

Apart from being able to filter the configuration item views, configuration managers are now also able to perform mass updates of the CI records. This is a powerful new feature that makes it much [...]

Some people already noticed the 3 small dots that are now visible in the header of the views within the Records console. When a user clicks on these dots, the option to add a filter to the view [...]

A significant performance improvement has been transferred to production. Specialists who work in very large organizations should notice that their requests, problems and tasks now open just a [...]