Enterspeed is no different from other software; things go wrong, and then you need to figure out why. So we are very happy to announce that you can now access the logs for our destinations the Enterspeed Management app.

If you just want to see how it works, then head over to Settings and the Logs section ➡️

If you want to read more about the feature, then we recommend reading our What to Do When Things Go Wrong blog post?

Only last week, we announced the availability of creating and managing the Algolia, Azure Service Bus, and Webhooks destinations via the Management app. Today, we are expanding the list of destinations to include:

1️⃣ Relewise

2️⃣ Typesense

3️⃣ Elastic App Search

Read more about how to use these destinations in our documentation.

We're thrilled to announce this update: Destinations can now be configured via the management app 🎉

What are Destinations? They're your gateway to effortless integration with third-party services like Algolia and for custom integrations with Azure Service Bus, and Webhooks. With Destinations, pushing data where it's needed has never been easier.

Previously a feature by request, Destinations are now available to all tenants via the Enterspeed Management App.

Curious to learn more? Dive into our documentation on integrating with Enterspeed.

The Management App have been updated, for this release you will notice some smaller features and changes:

↕️ It is now possible to sort both source entities and views by updated date
⬅️ You can hide the left sidebar to give more space for schemas
📋 The JSON document in the testing pane is saved when opening/closing the testing pane
🌚 Dark mode colours have been given a refresh
⌨️ More keyboard navigation options from the ctrl/cmd-k menu powered by CommandBar
🌍 View connected sources on the Environment settings

We hope you enjoy the small new features and we are looking forward to releasing more Management App features. If you have any feedback or questions, then please reach out on your Slack support channel or via support@enterspeeed.com

It is now possible to filter which source entities you want to initiate a reprocess action for. The reprocess action is used when an update to one source entity should also trigger the processing of a schema that isn't directly triggered by that source entity.Until now, it has been possible to reprocess by schema or source entity origin ID. With the introduction of the .filteroption, reprocessing can be done very specifically, yet flexibly and dynamically.

An example of using the filter for the reprocess action is when a product source entity type should trigger the processing of one or more category pages. Using the filter option is similar to the filter method when using references. Below is a simple example:

Read more about actions in the documentation.

Here's a bonus tip for all you eager beavers who can't wait to dive in without even glancing at the manual: Reprocess actions only kick into gear during ingest, not when you're flinging schemas around - because let's face it, schemas don't rearrange the data the reprocess actions are designed to tinker with. So, take a breather, grab a cuppa, and maybe give that documentation a cheeky little peek, eh?

We keep expanding the list of integrations to Enterspeed, and this time it’s a new destination integration from Enterspeed to an external Azure Service Bus.

With this integration, a message is pushed to your own or any other external service bus whenever a view is created, updated, or deleted. In many ways, this works just like our webhooks. However, if you prefer a service bus and are working in the Azure environment, you now have an extra option to choose from. The service bus integration supports both queues and topics as destinations.

As with our other destinations, you decide at the schema level which views should trigger a message.

JavaScript schema example:

It is now possible to create redirects explicitly from a JavaScript schema. Previously, redirects were implicitly created based on the redirects added to the source entity during ingest. When creating multiple URLs or stitching URLs together from multiple data sources, we now offer the possibility to add dynamic redirects as well.

A simple example for creating redirects from a JavaScript schema is where the .redirects function is passed an array of strings:

Read more about routes, urls and redirects in the documentation.

A couple of months ago, our Delivery REST API introduced a POST request version, allowing you to request up to 1,000 views in a single request. With the introduction of the FetchMany method, this is now also possible through our .NET SDK.

Just as in the REST API, it’s possible to fetch views by handles and IDs, as shown in the example below:

Simply install or update the package to version 1.4.0 from NuGet.

In addition to the new method, the new package version also includes dependency updates to System.Text.Json to support version 8.

We are now opening for a public beta of an updated Management App: https://app.beta.enterspeed.com. We would very much appreciate your feedback on the new app, so please try it out and shoot us a message using your Slack support channel or via support@enterspeed.com.

Initially, you will not notice a lot of changes, but we have cleaned up the codebase to allow us new possibilities in the future. For now, we want to focus on delivering the same capabilities as you know today. We do want to highlight one feature that many users have requested: in the beta, it is now possible to sort source entities by updated date!

It is a beta, and we need your help to weed out the last potentially blocking bugs. We have been using the beta internally for a few weeks and already had a couple of our partners help test it out. Currently, all features more or less work as expected. We are aware of dark mode bugs, layout issues, and other minor issues. For example, signing up using the beta app is not supported.

You can simply go to https://app.beta.enterspeed.com and start using this as the primary app. You can use this URL until we launch this new app as the new default. We are particularly interested in knowing if you run into anything that makes you want to revert to the existing one. But any feedback is welcome!

Using the new app is very low risk, as you can always switch back to https://app.enterspeed.com if something is misbehaving.

And finally, a note for users who have been with us for a long time. You may risk being prompted by an "Unsupported Tenant" popup. This will happen if you are using a non-source group tenant. The popup will include a link to the old app, so it looks scarier than it is. All active tenants that are in scope for this popup have been contacted directly.

As you probably know, you can organize your schema in folders in the Enterspeed app, making it easier for you to find the schema you're looking for.

Now we also brought the folder support into the CLI. This means that you'll see and work with the same folder structure on your local disk as you do in the Enterspeed App. You can move schemas from one folder to another locally and update them in the Enterspeed app.

As a result, the old static partials folder is now gone and the type is reflected in the file name instead (schemaAlias.schemaType.js), which also opens up for supporting new types of schemas in the future.

If you already have your schemas locally and you want to upgrade the CLI, simply clear your local schemas folder and run the schemas clone command to get the new schema name and folder structure.