# Cassis

## NEW

### Add step anywhere and cut/copy/paste

Long-awaited feature, essential while designing playbooks.

### OpenAPI additional properties

OpenAPI “additional properties” are now supported. This allows Mindflow to better support vendor APIs, in particular some advanced very generic-oriented APIs like ServiceNow or Atlassian JIRA.

### HTTP samples (ongoing)

A number of new HTTP APIs are now covered by bringing HTTP samples as steps in Mindflow. The user experience is a bit different than API-driven steps - this fills a raw HTTP request ready to be personalized. This adds convenience to support vendors not exposing their API as standard OpenAPI.

### Receiving email (alpha)

It’s now possible to **trigger playbooks by sending emails**. The integration is pretty simple: you need to send an email to {playbookId}@emailhook-{tenantId}.mindflow.dev. Emails are fully parsed, and the basic and advanced data can be picked, such as email subject, body, emitter, attachment. The only limitation is that you cannot handle attachment file content yet but only the attachment metadata such as filename or checksum.

Docs: [Run playbook through email](https://app.notion.com/p/Run-playbook-through-email-1a0aca49c0c045b1acc6bfcdb0767eb8?pvs=21)

---

## `CHANGES`

### Step inspector improvements

Step inspector user experience has been greatly improved and is more natural than before. This was needed to support additional properties and a super opportunity to add icons, enrich menus, consistency with the rest of the UI.

### Vault and credentials UI improvements

Clarity has been brought to Vault and associated credentals: better Vault header section, icons for credentials and constants, and panel display.

### Menu and toolbar enhancements

Actions such as adding a step, running a step, autolayout; or picking some data have been largely improved so that they are better organized, visually more appealing, and convenient to use.

---

## `FIXES`

A lot of **bugfixes and regression** have been addressed on:

- HTTP body content defined in OpenAPI 2.0 were incorrectly handled.
- Playbook execution time has been optimized.
- Search in Service explorer now works fine.
- Regular expressions in the function catalog (alpha) are now operational.

## `KNOWN LIMITATIONS`

- A number of functions in the function catalog are still not operational. Feature is marked as beta in the web inteface. They will be fixed along the next releases.