Modified Existing Pipeline to prevent when user deleting the content item

 This functionality implemented for, when user deleting the item, we are moving item to deletion workflow state instead of deleting the content item completely.


Alternatively we can say like "Remove the Delete access right from wherever you have defined it in your content tree."

For detailed reference, the below link covers

https://sitecore.stackexchange.com/questions/19262/adding-workflow-for-item-deletion

Step 1 : We need to create Deletion Approval workflow state. It contains the commands Approve for deletion and Reject. Approve command has the Delete action.


Step 2 : Then we have to create config file to update existing pipeline. It will patch(run) the processor, when user deleting content item in sitecore.

We have to specify type(Full class file name, AssemblyName), method(name of method).



Step 3 : We have to create class file to write the logic for updating Deletion Approval workflow state for the content item which user deleting.

Path of the class file : Cirrus.Foundation.Sitecore.Commands.Pipelines.CustomWorkflowDelete


Step 4 : Once the item moved to Deletion Approval workflow state, we have two commands. Those are Approve and Reject. If it is Rejected, it will go to the Draft state. If it is approved, it will go to Deletion Approved state.

In the Deletion Approved state, we have one action Delete item. 


Step 5 : Delete item action will have reference of class file in Type string field. The value should be Full class file name, AssemblyName.

It will cover functionality of deleting item in sitecore.

Path of the class file : Cirrus.Foundation.Sitecore.Commands.Pipelines.DeleteApproved




Comments

Post a Comment

Popular posts from this blog

Email Experience Manager (EXM)

Image
Email Experience Manager (EXM) To engage with customers in the website, we can deliver the relevant email messages to the customers at the right time. The Email Experience Manager (EXM) helps you create and deliver bulk email campaigns quickly and easily. The email campaign builder has four tabs each of which represents a step in the process. General On the General tab, you specify the campaign name and description along with the sender's details. Recipients On the Recipients tab, you add lists or segmented lists that you have created in the List Manager. You can also add a list of recipients that have been saved to a file. Message On the Message tab, you define the elements of the email message and this tab contains some important controls. Delivery On the Delivery tab, you have the choice to select the message variant and specify options and schedule.
Read more

Federated Experience Manager (FXM)

Image
The Federated Experience Manager (FXM) is an application that allows you to track visitor interactions and generate analytics information on external, non-Sitecore websites with Sitecore. You can use FXM to implement personalization rules, create goals and events, and implement content profiling on an external website. To enable FXM functionality, a JavaScript tag is added to the external websites. It allows the FXM application to connect the external site's components to the Sitecore Experience Platform. FXM has a dedicated Experience Editor that allows you to assign marketing attributes, implement personalization rules. You can access the FXM through the Marketing Control Panel or through the FXM application on the Sitecore Launchpad. When you have applied the FXM JavaScript tag to an external website, you can assign FXM functionality in one of the following ways: Capture Click Action Add Placeholder Add Page Filter Assign Marketing Attributes For reference :  https://vinayakchau...
Read more