Szymon Kuzniak

Happy new year!

Let’s be honest. Documentation is a great thing, but sometimes you just need to get your hands dirty and do some exercise, to actually understand the concept. That’s how I came up with the idea of this little blog post series.

Long time there was no word from me but now, I’m coming back with new, exciting project, I was working on recently. Our client requested an automated translation service for products from Content Hub PCM module. As much as it was interesting, the project had also few challenges which I will describe here shortly.

Adding new localization might not sound like a fancy topic for a blog post. Well, it turns out in the case of CMP there might be some interesting caveats worth knowing about.

Content Hub is a great tool to centralize all your content operations. However, it can be tricky to get the content out of it to all the different channels you might want to support. The main problem is obviously, how do you know if there is anything new to be synchronized, and I’m pretty sure you don’t want to poll Content Hub every now and then to find it out. Sure, it’s possible to write a separate action for every channel and handle them using a trigger, but there’s even a better way, which allows you to set up Content Hub just once, and then only connect new clients.

Content Hub security model seems pretty simple - there are rules for entity types with conditions, and a set of available access rights. What can potentially go wrong?

I was about to demo the connection between Sitecore Content Hub and Sitecore XP, and I though that apart from regular content elements, such as articles or blog posts, I could maybe synchronize also products. I was quite surprised, when I found out that I can’t acutally synchronize majority of the fields of my products because… they are multi-lingual.

Today, I would like to go through the configuration of the Content Hub, to automatically synchronize content with Sitecore XP. The process itself is fairly simple, although there are some caveats worth noting.

This post is a fourth part of the series about creating custom notifications with Sitecore Content Hub. This time I wanted to share a script which will send the notification when the user shares a saved selection with another user.

This post is a third part of the series about creating custom notifications with Sitecore Content Hub. The problem I am trying to address is triggering an email notification when the entity is updated, depending on the value of one of the relations. In other words, if a product which belongs to “Health” department is modified, I want to send email notification only to members of groups related to healt.

This post is a second part of the series about creating custom notifications with Sitecore Content Hub. The problem I am trying to address is triggering an email notification when the entity is updated, depending on the value of one of the relations. In other words, if a product which belongs to “Health” department is modified, I want to send email notification only to members of groups related to healt.

Sitecore Content Hub has a rich set of notifications complemented by a set of editable email templates. They can be easily turned on and off depending on the channel - either email or internal push message. However administrators are restricted only to this initial list and its base functionality. Sometimes it might be necessary to notify users about events which are not available out of the box or use non-standard email template.

It’s trivia to say that time flies.