Himmat Singh Dulawat (4x Sitecore MVP)

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: 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  😊