When you install the Enterspeed Umbraco package on an existing site with content, media, and dictionary items, you should do a full seed to ingest all the data into Enterspeed. This is simple with just a click of a button.

But what if you change a hostname for a subsite or update your code to include additional properties for your media items? How do you re-seed the affected nodes without doing a full re-seed?

With version 2.4.0 it’s now possible to select specific nodes you would like to re-seed, being all media items only, a specific content node with or without it’s descending nodes or specific dictionary items.

It’s even possible to clear the queue of seeded items if you accidentally seeded the wrong items.

Nice right?

Just go ahead and update your package reference to the latest version and check it out.

Inspecting and debugging routes is now easier than ever.

We have added the Route Inspector page in our app, enabling you to see what's going on quickly.

What do we mean by that? You see, routes can be a little tricky to debug, to put it mildly.

Let's first look at a "normal route" - a generated view.

Here we can see that the route /fairy-tales/the-snow-queen/ is generated by the source entity 1147-en-us, which gives us the view 1147-en-us/View/contentPage.

That's great and precisely the expected behaviour for most routes. What can be confusing and introduce head-scratching is when we start having redirects. 

Say we have a redirect for the route /fairy-tales/the-fire-king/, which is generated by source entity 1234-en-us, take redirects us to /fairy-tales/the-snow-queen/.

Before the route inspector, finding exactly which source entity was causing this redirect could be tedious. Now it is much easier to get a feel of what's going on.

As we can see in the example above, we can quickly locate which source entity is causing the redirect.

Sometimes… something comes along… that’s so fantastic… not even an Owen Wilson “Wow” can capture its magnitude. We are so excited to announce the preview release of JavaScript Schemas 🎉

Tenants with this feature enabled will now see the option to choose either JSON or JavaScript format when creating a new schema.

So, why is this exciting? As you already know, the schemas in Enterspeed are all about transformation.

We take our existing data from our data sources (CMS, PIM, etc.) and build schemas that generate the views we use in the front end.

Sometimes all that is needed is a simple one-to-one mapping. But other times, we need some custom logic to either format the data correctly or return the correct data to a specific user.

This is where we experienced a limitation with JSON schemas. JSON is fantastic for representing and structuring data. However, all custom logic could only be done using Enterspeeds own built-in methods.

This is fine for some of the most common cases, but as the logic and use cases got more complex, so did the job of developing and maintaining these methods.

That is why we decided to give the power back to the developer by providing them with a familiar and versatile language – the one and only JavaScript.

Ensuring all routes were presented in lowercase is now as simple as appending the URL with toLowerCase().

What’s next?

Our goal for the preview release is to achieve feature parity with JSON Schemas.

However, we also have a list of enhancements planned. One particularly exciting addition is the support for shared JavaScript modules, including third-party NPM packages and custom modules.

We are also focusing on improving the overall developer experience, aiming to make JavaScript Schemas as user-friendly as other IDEs like VS Code.

Lastly, it's important to note that the preview release does not currently support Algolia and webhook destinations, which are still under development.

How do I get it?

Want to test it out? Reach out on your usual support Slack channel or write to us at support@enterspeed.com to request access to the preview.

We can't wait to see what you can build with JavaScript Schemas.

We hope you want to try out the new JavaScript Schemas, and we'll be grateful if you'll try your use case and provide your feedback.

Please note that this is a preview release; we do not recommend using this for production tenants. We might make changes based on your feedback!

We expect to roll out general availability later in the summer.

The Enterspeed Ingest API makes it super easy to ingest vast amounts of data from your CMS, PIM, ERP, etc.

The source entities ingested are then instantly available in the UI in the “Source entities”-table and will, depending on your schemas, generate or regenerate a view.

That’s great and all. Using the API is extremely powerful. But sometimes you don’t need the most powerful thing to solve your problem. You just need it to be quick.

If you’re hungry now, you would prefer those sweet, sweet Taquitos (shout out to all the Taquitos-enthusiasts out there 🙌) from the local 7-eleven you can get instantly, rather than wait 30 minutes for a restaurant to make your meal.

This is why we’ve added the option for you to add entities directly from the UI.

On the “Source entities”-page, you will now see an “Add entities”-button in the top right corner. Clicking this button will open a modal that allows you to either upload one or more JSON-files or add your entity manually.

Nice.

Simply select the source you want the entity/entities added to. If you want, you can also change the generated Origin ID, which is a random UUID on the “Add manually”-option and is the filename on the “Upload files”-option.

As a help, we added the Request Body Schema, which shows which properties are available and which are required when adding an entity.

Enjoy!

The package is an add-on for our Umbraco integration, so if you use Enterspeed on Umbraco, this is great news for you 😊

Cloudinary is a cloud-based image and video management service.

The Cloudinary-Umbraco package will automatically upload the Umbraco media to Cloudinary and ingest the Cloudinary url to Enterspeed instead of the Umbraco url.

That means you can now effectively use your Umbraco media library in a decoupled architecture! 😮

Awesome stuff, right?

The integration is open source and you can find it alongside our other integrations in our documentation.

How does it work, you ask? See for yourself 👇

We've added logs to our UI.

You're now able to view log details from our services:

• Delivery API (all regions)
• Import Worker
• Ingest API
• Management API
• Processing Worker

You can filter it by levels:

• Information
• Warning
• Error

We are happy to announce to you our new feature CommandBar. 

Now it is easier and quicker to find anything in Enterspeed. Simply click the search bar in the header or click Ctrl + K (⌘ + K on Mac).

CommandBar lets you search through Schemas, Partial schemas, and Tenants so you can quickly navigate to them. 

You'll also find quick access to all the pages in Enterspeed, as well as links to support areas.