Share via

Page Editing Toolbar - Problem with submit for approval node in the quick access

  • Article

You need to customize the CustomQuickAccess.xml to achieve the functionality. Curiously, the functionality works well when you click the button – “Submit for approval..” under the workflow tab. So the idea was to somehow replace the original button with a new button which has the same functionality as that of “Submit for Approval …”.

Following is the content of the customquickaccess.xml which will delete the non working node and will add the working node in the quick access area.

<?xml version="1.0" encoding="utf-8" ?>

<Console>

      <references>

            <reference TagPrefix="cms" assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral,

PublicKeyToken=71e9bce111e9429c" namespace="Microsoft.SharePoint.Publishing.WebControls.EditingMenuActions" />

      </references>

      <structure>

            <ConsoleNode Action = "cms:PublishWithCommentAction" ID="saPublishWithComment" Sequence="610" ConfigMenu="Add" />

            <ConsoleNode ConfigMenu = "Delete" ChangedNodeID = "qaPublish" />

      </structure>

</Console>

In the above CustomQuickaccess.xml you can find that we are adding the cms:PublishWithCommentAction through ConfigMenu=Add option and deleting the “qaPublish” node through ConfigMenu=Delete which is cms:PublishAction console node existing in the quickaccess.xml. This is how we need to override the OOB Quick area nodes. In the same way you can customize the EditingMenu and Site Action nodes.

Once you save and publish the customquickaccess.xml file the problematic console node vanishes and the new console node for “SubmitForApproval” appears in the quickaccess which works fine for all the workflows irrespective of the associations.

So the conclusion is that the console node with action cms:PublishAction is a problematic node when you have custom workflows (with ASPX page association) attached to the pages library. The above mentioned trick is the work around or resolution and you can dig deeper on the above mentioned classes (Microsoft.SharePoint.Publishing.WebControls.EditingMenuActions.PublishWithCommentAction and Microsoft.SharePoint.Publishing.WebControls.EditingMenuActions.PublishtAction) to check the root cause for this behavior.

Comments