Content publishing using Content GovernanceIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Content publishing using Content Governance. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Releases Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1. Submit the request using the below link. https://<instance_name>.service-now.com/esc?id=sc_cat_item&table=sc_cat_item&sys_id=ae414741775f0110a10440483f5a99ff 2. Open the Content Request Item that has been requested by a user, do this as a Content Manager or Content Admin role. This Content Request should be in Open/Work in Progress state, and should not yet have a Content associated to it yet. 3. Set the state to Work in Progress save the content request item and assign it to a user. 4. Notice a new UI Action button "Create Content", click it and you'll see the Content Library content creation menu pop up. 5. Select type and create content as per your requirement (Example :Rich Content ). 6. Fill in the required details, then click "Save and continue" to continue to the publish tab. 7. Add a publish plan, and fill in the name and location of where you want to publish the content. Also fill out the audience. For the "When", fill out a Start and End time, but ensure you keep the selection on "Inactive". Save the publish plan. 8. Once saved, you should see a "Send for review" button in the Content Builder (you can also set it to In Review in the Content Request Item itself once you have set all the approvers you want). Set the Content Request Item to "In Review". 9. Change the state of the Content Request Item to "published" so that the scheduled content will be active and the content will get published based on the updated start date and end date. 10. Attached is the screen shot for reference while creating the publish plan and sending it for review.