Schedule Publish/UnPublish Best practices

Publishing best practices

Schedule Publishing/UnPublishing

Architecture and customization

-Jitendara Soni

1       Introduction. 4

2       Schedule publishing and unpublishing – Best Practices. 5

2.1         Items should have workflow assigned, else it will be automatically published to CD(WEB) 5

2.2         User publishing version option, instead of using publishing option on the template. 5

2.2.1      Template level publishing will be applicable for all version. 5

2.2.2      If you create first item and publish for future then it’s fine but if you edit and publish for the future the current whole item will be removed from the CD(WEB) instance. 5

2.2.3      Before publishing new version – default it will take current time for publishing, verify and reschedule this before workflow goes in final stats. 5

3       Schedule publishing and unpublishing scenarios. 5

3.1         Scenario 1 –    Create an item without any worklow. 6

3.2         Scenario 1.1 – Create second version of that item without any workflow.. 6

3.3         Scenario 1.1 – never publish setup without any workflow. 6

3.4         Scenario 2.1 – Create item with workflow.. 6

3.5         Scenario 2.2 – Create new version of workflow items. 6

3.1         Scenario 2.3 – Schdule multiple item through publish menu-change options

1 Introduction

For scheduling and unpublished content based on the upcoming dates is a key area for the Architecture to take the right decision, even to agree for the initial discussion,

Here, it’s an attempt to cover – What is default is Sitecore and what all are the must required changes/customization.

Example – Scheduling.

2 Schedule publishing and unpublishing – Best Practices.

2.1  Items should have workflow assigned, else it will be automatically published to CD(WEB)

2.2  User publishing version option, instead of using publishing option on the template.

        2.2.1 Template level publishing will be applicable for all version.

        2.2.2 If you create first item and publish for future then it’s fine but if you edit and publish for the future the current whole item will be removed from the CD(WEB) instance

        2.2.3 Before publishing new version – default it will take current time for publishing, verify and reschedule this before workflow goes in final stats. 

3 Schedule publishing and unpublishing scenarios.

Scneaion after enabling the future publishing job, as example below

3.1 Scenario 1 – Create an item without any worklow.

Item will be published.

3.2 Scenario 1.1 – Create second version of that item without any workflow

Second item will automatically published.

3.3 Scenario 1.1 – never publish setup without any workflow.

Set never publish to this items – let see if this item automatically disappear or not

It would be quickly deleted.

3.4 Scenario 2.1 – Create item with workflow

It will be published after approval

3.5 Scenario 2.2 – Create new version of workflow items

After approval for next 5 minutes, previous content will be moved.

3.6 Scenario 2.3 – Schdule multiple item through publish menu-change options

Here multiple item can be defined, below are the details

Pipeline Execution:-

Note :-  For any execution and logic for the pipeline execution below information will be usefull.

We wanted to process some date modification on pipeline and used itemCompleted pipeline but that will only triggered once for all language versions, then have to move our code to itemProcessing pipelines.

Details:-

ItemProcessing - this will be executed for all language versions. Let's say if you have one content for five languages then it will be executed for five time, You code should handle to be executed for one or multiple time based on your field type Shared or not.

Pipeline processing End :- This will be executetd only one time, let's say if you have content published for five languages it will be executed once.

Piple line end: this will also be executed once as Pipeline process End