Workflow Rejection for Dynamic Module Items Using the Sitefinity API

Workflow Rejection for Dynamic Module Items Using the Sitefinity API

November 01, 2013 0 Comments

The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.

When moving Sitefinity module builder items through the workflow, the standard method used is to call.

It is the extension method SetWorkflowStatus which allows you to state the status of each item to Published, Draft, AwaitingApproval, AwaitingPublishing, Rejected.

dynamicItem.SetWorkflowStatus(testsItem, dynamicModuleManager.Provider.ApplicationName, "Published");


The case with rejected, however, doesn`t support the addition of a rejection reason when rejecting an item sent for approval through code. While this is available through the UI and the rejection reason can be added, using SetWorkflowStatus doesn`t support it.

For this purpose until this feature is implemented and SetWorkflowStatus supports addition of a rejection reason, you can use the custom class that can be downloaded from here and provides customization of the SetWorkflowStatus method.

To use the class, call the static method  IWorkflowExtensionsCustom. SetWorkflowStatus

IWorkflowExtensionsCustom.SetWorkflowStatus(testsItem, dynamicModuleManager.Provider.ApplicationName, "Rejected",new CultureInfo("fr"),"rejection reason: fix spelling");


Stanislav Velikov

Stanislav Velikov is a Tech Support Engineer at Telerik. He joined the Sitefinity Support team in April 2011.

Comments are disabled in preview mode.
Latest Stories in
Your Inbox
More From Progress
5 Questions Automakers Should Ask to Improve Asset Uptime
Download Whitepaper
2018 Gartner Magic Quadrant Web Content Management (WCM)
Download Whitepaper
What Serverless Means for Enterprise Apps
Watch Webinar