Himmat Singh Dulawat (4x Sitecore MVP)

Sitecore has introduced the AI features into the Sitecore Content Hub. It's an advanced tool to provide features and functionality to content generation, virtual search, content Translation, Image tagging, and many more.  In this blog post, I am explaining a few of them and how to use them from the context of the Content Entity. But before getting started, we need to enable the AI features in Sitecore Content Hub. Enable AI features in Sitecore Content Hub: Click on the manage icon and choose the AI features option. Click on the Enable button for both Content Generation and Visual Search to enable AI features. Content Generation: After enabling AI for content creation, you can generate original content, update or enhance existing content, refine tone, summarize, and check grammar and spelling. To use these features, open any content entity in Content Hub and navigate to a single-line text, multi-line text, or CKEditor field. You’ll see a star...

The Sitecore Content Hub system does not display information about the author who submitted the content on the content detail page for review. To make the author’s information visible on the content detail page, we need to perform the following activities  Create a new member group with the additional Fields Create a Script, Action, and Trigger to set the values Enable the setting on the page component to display the details Create a new member group with the additional Fields: To add information about the author who submitted the item in Content Hub for review, follow these steps to configure it: Step 1: Navigate to the manage icon and choose the Schema option Step 2: On the Schema page, search for M.Content and on M.Content page, click on the “New Group” option and fill in the details, and click on the save button: Step 3: Once you create a new group, click on the New Member option and add the following new members with respective type...

Problem Statement: I was following the article Download options for Azure AppService deployments to install Sitecore PowerShell and SXA modules on Sitecore Managed Cloud Service PaaS 2.0 instead of my local dev instance. Sitecore Version: Sitecore 10.4 XP Managed Cloud Service: PaaS 2.0 I have successfully installed both the PowerShell and SXA modules, and they appear correctly in the CM instance.  But after restarting the CM Web App, both modules disappear from the CM instance, their config file is missing from the App_Service folder, and require reinstallation to complete the setup again. Here, I have used Sitecore CM instance Development Tools -> Installation Wizard to install the modules. Solution:  To investigate this issue further, I have checked the logs generated in Application Insights to confirm the installation. Additionally checked the traces and verified that the module is installed in the correct path: However...

In this blog post, I will explain the Experience Edge for Sitecore Content Hub, Experience Edge for Content Hub APIs, GraphQL IDE, and GraphQL. Experience Edge exposes data through GraphQL APIs and media through a CDN. The CDN is responsible for routing and caching queries that flow to and from the delivery platform. Whenever Content Hub detects changes to approved content or the schema, it raises an event that triggers the automatic publishing process. Refer to the document for more details about the Experience Edge:  Experience Edge for Content Hub To start with Experience Edge IDE, we need to first understand the Preview Vs Delivery APIs: Preview API: A GraphQL API that exposes a preview of your content. This API provides access to all content, including drafts and other content that is not yet approved. Delivery API: A GraphQL API that exposes your published content. This API provides access to approved and published cont...

Sitecore Content Hub provides Taxonomy and Option list features to classify the data; both have their use case to choose the appropriate approach. At a high level  Use Taxonomy when the data contains more than 50 items. Use Taxonomy if you want to apply a security rule based on the values, as the option list does not support it. See the documentation for more information:  Choosing between taxonomies and option lists In this blog post, I will explain to you how we can create a Taxonomy, classify the data, and use the same taxonomy for search purposes.  Create a Taxonomy: Step 1: Click on the manage icon, top right corner Step 2: Navigate to the Taxonomy Step 3: Create a new Taxonomy called POC.Educational and fill in the values in the following fields. I am allowing manual sorting as it lets you manually sort taxonomy items. Step 4: It will create and open the Taxonomy management page and the Education taxonomy....

Sitecore Content Hub provides a feature to export Content items in Excel, and we can customize the export profile according to our requirements. You can find the blog post here: Custom Export Profile in Sitecore Content Hub Export User Profile in Sitecore Content Hub In this blog post, I am explaining how to export the Collection items in Sitecore Content Hub. If you go to the collection pages, you will not be able to find the export to Excel option. Find a screenshot. To enable this feature, perform the following steps: Step 1: Click on the manage gear icon and click on the pages. Step 2: In the left panel, scroll down to the collection and click on the collection. Step 3: In the right panel, choose the selection component. If it is not enabled, then click on the user icon and enable it. Step 4: Now enable the Export to Excel radio button to have one more additional tab. Step 5: Click on the Add Definition button, sig...

Sitecore Content Hub provides you with the features and functionality to create a trigger, an action, and a respective script to enhance your customization and implement your business logic. As we are aware, we can execute the Trigger, Action, and Script on the Save button of the content entity, but in case you want to update any field value example, date field values, once the author approves the content after final review, instead of the save button then we have to tweak our approach while setting up condition into the trigger.  As we know, triggers, actions, and scripts in Sitecore Content Hub are typically executed by clicking the Save button of a content entity. However, suppose you want to update a field, such as a date field, specifically when the author approves the content after the final review (rather than during draft, review, or version save). In that case, the trigger conditions need to be carefully configured. The business requir...

Problem Statement: As part of the cloud infrastructure monitoring activities, the Sitecore Cloud Operations team identified an event and shared an email regarding the Sitecore Cloud Alert 'SearchStax CPU Usage.' We received alerts indicating that high CPU usage was detected on all nodes of the Solr deployment. Upon further investigation, the following observations were made: High CPU usage and system load High indexing activities  Solution: A CPU Usage alert is a Threshold Alert that notifies you via email when the CPU of your SearchStax Managed Search service deployment exceeds a specified threshold for a certain number of minutes. This triggers an Incident in the Managed Search Dashboard. Here are some recommendations to enhance SearchStax performance and improvement: 1. ContentSearch.SearchMaxResults/Lowering &rows=1000000 This setting determines the number of search results the search provider is asked to retrieve...

Problem Statement: Due to certain business requirements, we create fields read-only or hide them from the author to avoid unnecessary confusion while ensuring business logic is implemented.  In Sitecore Content Hub, we create a field property from the Content-Type option, there is no way to hide it during the creation process. Solution: There are two types of members for content types: content members and detail members . Content members represent individual pieces of content and are editable on the content detail page. Detail members represent content metadata and can be hidden from the content detail page. To meet the above requirements, you can change the member type from content to detail by moving the member to the M.Content schema page. Next, you can update the entity details component to ensure this member does not appear on the page. Happy Sitecoreing  😊

In an organization, the Password Policy is key to securing the platforms, preventing unauthorized access, and protecting sensitive media and metadata etc. In this blog post, I will let you know how you can update your password policy in the Sitecore Content Hub product by enforcing users to reset their passwords every 90 days. Sitecore Content Hub provides the configurable option to enforce the organization's standard-based password policy.  You can configure the password policy from the security settings section of Manage Launchpad.  Click on the Manage Icon and choose the Settings option: From the left panel, search for Authentication or click on the Authentication under Portal Configuration: The default setting of the expired password is set to 2147483647 minutes, and other default values can also be seen in the other settings in the PasswordRules example: RequiredLength, RequiredLowercase, RequiredUpercase, RequiredDigit, etc. To c...