Skip to main content

​
Highlights

​
AI classification and condition checks in workflows

Workflows can now classify data and evaluate a condition described in plain language as built-in steps, without wiring up a separate model. A workflow reads the AI’s answer and branches on it, so decisions that used to need a custom integration now come built in. For example, a ticket workflow can decide whether a request describes a security incident and route it to the right queue based on the answer.

​
Normalization rules for databases

Normalization rules map inconsistent entries in a database table to a single canonical value, so messy data from different sources lines up. Each rule sets the raw value to match and the canonical value it maps to, and you can run a new rule on existing records to clean up data already in the table. You can add rules from a table’s Rules tab or describe the rule you want to Catalyst in plain language. For example, a rule can map “Acme Incorporated”, “ACME”, and “Acme Inc.” to a single vendor, “Acme”, across your vendor table. See Database rules.

​
Validation rules for databases

Validation rules let you require values in a database table and block changes that don’t meet your conditions. A rule can check whether a field changed, compare a field to a fixed value or to another field, match a regular expression, or check a numeric range, and you can combine conditions with AND or OR. When a change is blocked, Serval shows the error message you set. You can add rules from a table’s Rules tab or ask Catalyst to set them up. For example, a rule on an asset table can require a serial number on every new laptop record and block purchase costs outside an expected range. See Database rules.

​
Reroute an access request to a different role

When an approver reviews a pending access request, they now have a third option alongside approve and deny: change the request to a different requestable role on the same resource. The original request concludes as rerouted and a new request starts for the role the approver chose, so a near-miss request keeps moving instead of being denied and refiled. Rerouting is available on the ticket timeline, in the Slack approval modal, and on the Teams approval card. For example, if a requester asks for a broad admin role, an approver can reroute the request to a narrower read-only role on the same application.

​
Reusable approval procedures in beta

Approval procedures are now named, reusable resources in Serval. You can define a procedure once, manage it centrally, and attach it to workflows, access policies, and more, so you update your approval logic in one place. When you ask Catalyst to build a workflow or access policy that needs approvals, it creates the approval procedure as its own resource and attaches it. Approvals already set up in existing workflows and access policies keep working as they do today. For example, you can create one security sign-off procedure and attach it to every workflow and access policy that grants production access. See Approvals.

​
Edit assignment rules from Catalyst

Catalyst can now edit a team’s assignment rules. You can open Catalyst directly from the assignment settings page and describe the routing change you want in plain language. Catalyst updates the rules for you, so you don’t have to build each condition by hand. For example, you can ask Catalyst to send urgent hardware requests from the London office to the EMEA desktop support group during business hours. See Assignment rules.

​
Workflows

See recent run health in the workflow list The workflow list now shows a health indicator summarizing each workflow’s recent run outcomes, so you can spot a workflow that has started failing without opening it. The indicator reflects the most recent runs and updates as new runs complete.

​
Ticketing

Set the assignment strategy per group An assignment group can now override how work is spread across its members, so one group can round-robin while another leaves tickets for manual triage. See Assignment groups. Add a Category path column to the ticket list The ticket list can now show a column with each ticket’s full category path, so you can see where a ticket sits in a deep category tree without opening it.

​
Campaigns

Deliver campaigns through the embedded widget Campaigns can now be delivered through Serval’s embedded widget, reaching people on your own site or app alongside the existing channels. See Manage campaigns.

​
Integrations

New native integrations Serval adds several native integrations you can connect and drive from workflows, all in beta: Palo Alto Panorama for managing firewalls, policies, and objects; Sonos for cloud playback control; Smartsheet for reading and updating project sheets; and Jenkins, JFrog Artifactory, Terraform Enterprise, Neat, and n8n. Real-time Okta group sync When Okta event hooks are set up for a connected Okta application, Serval now refreshes a group’s membership within seconds of a change in Okta, instead of waiting for the next scheduled sync. Group-based access and routing stay current as people join and leave teams. See Okta. JWT bearer authentication for custom apps Custom app connections can now authenticate with a JWT bearer token, so you can connect internal services that expect signed bearer tokens. Expanded regional endpoints Serval can now connect to more regional API endpoints: regional Harvest endpoints for Greenhouse, the US-3 and USGOV-2 regions for CrowdStrike, and the UK1 and US2-FED domains for Datadog.

​
Platform

New public API endpoints The public API adds endpoints to manage custom roles and assign them to groups, and to read a team’s assignment settings and rules, so you can manage more of Serval from your own tooling. Merge a duplicate user account Serval can now merge a duplicate user account into the correct one, moving its login identity so a person ends up with a single account. Reach out to Serval to request a merge.