Create final Approved State within Awaiting Approval state. For Final Approved state ensure to mark Final checkbox .

For Reject State select Next state to Draft state.

Template used

State

Action

Command

Validation Action

Important Library

Sitecore.Workflows.Simple.ValidatorsAction, Sitecore.Kernel

Sitecore.Workflows.Simple.PublishAction, Sitecore.Kernel

Publish Parameters

Publish action accepts 6 parameters:

"deep" - controls whether children of the current item will be published. Possible values: "1" - children of the current item will be published; all other values - children of the current item will not be published.

"related" - controls whether related items of the current item will be published. Possible values: "1" - related items of the current item will be published; all other values - related items of the current item will not be published.

"targets" - comma (,) separated list of database names that item will be published to. Note, that this parameter does not expect a list of publishing target names, it expects list of database names.

"alllanguages" - controls whether current item will be published in all languages that exist in source database. Possible values: "1" - current item will be published in all languages that exist in source database; all other values - code uses values of other parameters to determine languages in which current item will be published.

"languages" - comma (,) separated list of languages in which current item will be published.

"itemlanguage" - controls whether current item will be published in its current language. Possible values: "1" - current item will be published in its current language; "0" - current item will not be published in its current language; all other values - current item will published in its current language. Note that even if value of this parameter is "0", current item will still be published in its current language if current language of the item is in "languages" list.

Querystring parameter

deep=1&related=1&alllanguages=1

Auto Publish

Custom Workflow Action: SyncCustomDB

Suppose you want to sync your sitecore CMS data with custom database for Ecommerce database products or promotions if your enterprise solution doesn't provide that. The approach can vary with respect to problem and business requirement.

Assign this workflow to the page item and then when business user approves the sitecore content for given item -template the action event will be performed to sync custom database. These can be anything, we can even replace this with any functionality such email notification or anything that needs to be done in case of approve content.

Below are the list of querystring param that comes handy
when we are in production deployment and wants to troubleshoot the deployment
status in each and every sitecore delivery server. This is very useful querystring parameter at times where there are separate Content managed –Authoring server and several load balanced
delivery server, these querystring helps in finding the various behaviour of page and act as troubleshooting tools.

yes there are various ways to look for sitecore errors such as data folder logs, sitecore analyzer, IIS logs, event logs etc.

Thursday, January 7, 2016

Problem Statement
What if there is CMS system hosted in DMZ server and there is no scope of adding any additional requirement due to some reason and still wants to use Sitecore CMS as an option to port content to your digital interface that can be Mobile or other touch screen device installed in stores. Here is the solution to do so.
Recently we did the same implementation and made Sitecore CMS as source system to give data to digital screens and native Iphone App.