Pipelines in Sitecore

During the interview, many developers face questions about giving name of a particular pipeline for a particular purpose. And in most of the cases, we don’t remember name because we have never given attention to it during development. While writing code, we find the pipeline, add the processor and go head, but we don’t memorize that pipeline name.

So, to make it easy to memorize the name and purpose of pipelines, I’m trying to list them here to make sure never fail to answer the interview question.

Pipeline namePurpose
initializeRuns when ASP.NET initializes Sitecore. In some cases, you can use a hook rather than add a processor to the initialize pipeline.
preprocessRequestRuns for each HTTP requests for which IIS invokes ASP.NET to determine whether Sitecore should handle the request. The httpRequestBegin pipeline also includes processors that apply logic to each HTTP request.
httpRequestBeginRuns for each HTTP request for which IIS invokes ASP.NET.
getContentEditorWarningsRuns each time you select an item in the Content Editor to generate a list of notifications (warnings) to display at the top of the editing pane.
httpRequestEndPerforms diagnostics after each HTTP request
insertRenderingsDetermines presentation components to render an item.
jobInvokes jobs (background processes that can run for long periods) in dedicated threads
publishManages publising
publishItemRuns to publish each item.
renderLayoutPopulates placeholders to assemble the control hierarchy for rendering a page
healthMonitorPeriodically invokes diagnostic operations
sessionEndRuns when an ASP.NET session ends
getMediaStreamRetrieves the binary stream for a media request
expandInitialFieldValueExpands tokens in standard values such as $name when you create items
getLookupSourceItemsDetermines the items to include in selection data template fields.
getContentEditorFieldsDetermines the fields to display in the Content Editor
getPlaceholderRenderingsDetermines the renderings a user can add to a placeholder
getChromeDataDetermines features available for placeholders, fields, markup elements, and renderings in the Page Editor
getRenderingDatasourceControls the CMS user interface that allows the user to create or select a data source for a presentation component
renderFieldRenders the value of a field
searchImplements search operations
filterItemDetermines which version of items to display in interfaces such as Preview
uiAddFromTemplateInvoked when the user adds an item based on a data template, branch template, or command template
uiCopyItemsCopies an item and its descendants
uiCloneItemsClones an item and its descendants
uiDeleteItemsDeletes an item and its descendants
uiDragItemToInvoked when a user drags and drops an item
uiDuplicateItemDuplicates an item
uiMoveItemsMoves an item and its descendants
uiRenameItemRenames an item
uiGetMastersDetermines effective insert options for an item
loggininInvoked when a user logs in
loggedinInvoked after a user logs in
logoutInvoked after a user logs out
saveUIInvoked when a CMS user saves an item
uiUploadInvoked when a user upload a media item


Leave a Reply