Set Workflow using Item Buckets Search Operations

Recently one of our clients asked to set the workflow on large number of items that were created without workflow, so i was thinking of writing a script on powershell to do that, but then i thought why not extend Item buckets Search operation and add "Set Workflow" option there!

Basically, You will need to write a command that sets the workflow for all items in search results, and register that command.

1- The Code:


2- The Configurations:
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
  <sitecore>
    <commands>
      <command name="bucket:setworkflow" type="Sitecore.SharedSource.Buckets.SearchOperations.SetWorkflow, Sitecore.SharedSource.Buckets.SearchOperations"/>
    </commands>
  </sitecore>
</configuration>

3- Adding Command item in Sitecore:

  •  Open Content Editor and go to "/sitecore/system/Settings/Buckets/Settings/Search Operations/Fields"
  • Create new item of Template "/sitecore/templates/System/Item Buckets/Dropdown List", name it "Set Workflow".
  • In "Type" field, enter "bucket:setworkflow" and in "List Name" field, enter "Set Workflow", and choose a proper icon for that item :) .

The Result!


Comments

Post a Comment

Popular posts from this blog

Attaching a file on WFFM Send email action

On Sitecore 8.1 i recently faced this issue, We have a CM/CD setup and we are using WFFM for our forms, One of the forms has a file upload field where we store the file in media library, and We have "Send Email" action where we also add the uploaded file link, However, what we are seeing in the email sent that Sitecore is generating the File URL with CD domain, in this format: https://{CD Domain}/sitecore/shell/themes/standard/-/media/{guid}.ashx?db=master We are disabling sitecore shell access on CD, so we can't really access this URL, So i reached out to Sitecore support team for help, they said this behavior is registered as a bug (ref  77357)  and they gave the following workaround as a solution which is basically to attach the file into the email itself : Navigate to /sitecore/system/Modules/Web Forms for Marketers/Settings/Actions/Save Actions/Send Email Message item.  In Parameters field add the following: true . Save and publish changes. uploaded f...
Read more

Solr with Sitecore Checklist

Image
We have been using Solr with Sitecore for our latest Sitecore implementations as it offers better index synchronization across all CD/CM servers since its a standalone web app with HTTP access, which means that all CD/CM servers will have up-to-date indexed content, unlike lucene where each Sitecore server is responsible of synchronizing its lucene index, which sometimes breaks and causes content to be out-dated. This blog is not about how to configure Solr with Sitecore, there are many blogs talking on this subject, This blog is about some considerations and best practices that you need to take into account when you setup Solr with Sitecore.     First, Disable Indexing on CD's With Solr/Sitecore setup, you only need to enable indexing on CM, and disable it on CD servers, By default after any publish operation, Sitecore will store (item changed/added) event into Event Queue table, and each Sitecore instance will pick that and trigger index job for that item, W...
Read more

Caching Rendering HTML when conditional rules are applied

Image
Applying Sitecore caching is an essential task when you build your site, It help improve your site general performance and decrease response time significantly , Output HTML cache is one of the different types of cache that Sitecore offers, I almost apply it everywhere on site rendering components. However, If you are applying Conditional rendering on a component (Personalization) and you are setting different datasources based on some conditions, Applying Caching on that Component with " Vary by Data " option checked will not work as expected, At first i thought that Sitecore will resolve Component datasource by applying the Conditional rules before adding that to the " Cache Key",  That was not the case :( . It turned out that Sitecore uses the default datasource applied on the component to generate the Cache Key, So you will always see the " Default " version of the component on the page, And all of Conditional rules will be ignored. I'm usin...
Read more