14

If the workflows are not drastically different, you can achieve 'site-specific' workflow via content security. Step 1: Workflow security Create a single workflow definition with some generic access roles for each state. Use these only to grant access to the workflow states. Step 2: Content security Create a security role for each site and assign it to ...


11

Check if Version 2 of your item in "final" workflow state. This is not an error. This is a functionality of Sitecore. When the current item version you are working on does not satisfy the requirement to publish (ex: item version is not in the final workflow state, item version is set to never publish, item version have publish time set, etc), this warning ...


10

Using the code below, you can get comments from all workflow states of any particular item version: Sitecore.Workflows.WorkflowEvent[] workflowHistory = Database.WorkflowProvider .GetWorkflow(item) .GetHistory(item); string workflowComments = ""; foreach (Sitecore.Workflows.WorkflowEvent work in workflowHistory) { workflowComments += string....


9

You can use below powershell script (https://gist.github.com/marcduiker/950e0358bb4752ed5b047931a8c958c1) : # This is the ID of the workflow that will be set on the content items. $script:workflowID = "{A5BC37E7-ED96-4C1E-8590-A26E64DB55EA}" #Sample Workflow # This is the ID of the workflow state that will be set on the content items. $script:...


8

Yes, it is possible to do this without customization. Sitecore has the special validation rule that is named "Required", which checks fields that contain the value​​. You can find it in Sitecore/System/Settings/Validation Rules/Field Rules. Please, configure the workflow and validation rules for your template, in this way: In the "master" database open ...


8

Well the first thought that comes to mind is the deletion of the E-mail Action Item, found in the System/Workflows area of the content tree. It would appear under the workflow that you currently have running and under specific workflow states. You could also optionally just remove the To field, so it wouldn't send it anywhere, but that might be what you ...


8

This is not a good idea. If you want remove the requirement to Lock and Edit an item then you can update the following setting to false: <!-- REQUIRE LOCK BEFORE EDITING If true, the user must have a lock on a document before they can edit it, otherwise it is always ready for editing --> <setting name="RequireLockBeforeEditing" value="...


7

You can always use Sitecore PowerShell Extensions if you would like to generate reports or build a UI around the history data. $item = Get-Item -Path "master:" -Id "{110D559F-DEA5-42EA-9C1C-8A5DF7E70EF9}" $db = Get-Database -Name "master" $workflowProvider = $db.WorkflowProvider foreach($version in $item.Versions.GetVersions()) { $workflowEvents = $...


7

Here is code which changes workflow state and executes actions: public static WorkflowResult ChangeStateAndExecuteActions(Item item, ID workflowStateId) { using (new EditContext(item)) { item[FieldIDs.WorkflowState] = workflowStateId.ToString(); } Item stateItem = item.Database.GetItem(workflowStateId); if (stateItem....


7

Make sure to check "publish subitems" when publishing parent folder. To verify if the item was removed from the web database, switch to web database from Sitecore Desktop and see if your page is there. Open .../sitecore/shell/ in the browser and on the bottom right corner of the screen there is a button to switch database. Switch back to master database ...


7

There's no pipeline or event that you can plug into in the general sense of Sitecore's pipelines and events that you see in the ShowConfig. Instead, it's driven by an Item based pipeline provider. This is accomplished by creating what's called Workflow Actions that allows you to execute code when a workflow is changed to that state. There's an example of ...


7

To disable workflow entirely across your JSS templates and existing items, you can use the following bit of Sitecore PowerShell to clear the Default workflow on templates, and the Workflow and Workflow state on content items. Note that this script totally removes all workflow from the referenced content and template paths, so use with care if you have other ...


6

There's no out of the box functionality to approve child items Sitecore, but it is a common enough of a problem. Basically you would need to write a custom approval action that checks all related items when the main item is approved, and sets the workflow of the related items (or subitems) to approved state. Here's one example of how this could be done: ...


6

For bulk workflow operations there is a setting which decides whether the comment box should be displayed or not. Add <setting name="Workbox.SingleCommentForBulkOperation"> <patch:delete /> </setting> <setting name="Workbox.SingleCommentForBulkOperation" value="true" /> setting via a patch file to you App_Config. The first ...


6

One way you could handle this would be to remove access (through security) to Delete items in the tree and instead add a workflow command that sends the items through a "Delete Workflow." 1. Restrict delete access Remove the Delete access right from wherever you have defined it in your content tree. Note: Unless you want everyone to be subject to this ...


6

The the role to see the actions, you have to assign the permissions at the action level. Without that, the role will be denied the permissions to see the action.


5

I wrote the article that you linked to in your question, and my main motivation for writing it was the (current) lack of documentation around this new feature. Does this work if the data sources are in a different workflow than the page? The answer is no. The workflow command executed on the datasource items is the exact same one as the "parent" item. ...


5

Are you logged in as an Admin? Admins are not subject to workflow enforcement.


5

The difference between Sitecore Email Cloud Delivery and Custom SMTP are pretty simple. But to really understand why they exist, some background is needed. What is a Mail Transit Provider and why do I need one? At it's most basic component, the act of Sitecore (or any application really) to send email successfully, requires connection to some kind of ...


5

You can create an interim Workflow State which specifies an Action to decide which state to move the workflow to next. For example: Ensure you have set the following: The Submit Action on the Draft state should specify interim state as the Next State The interim state should contain: An Action item, and set the Type string value to your custom class (see ...


5

My two cents If to go strictly after the Helix documentation it seems like both the workflows and the datasources should belong to the project layer: https://helix.sitecore.net/principles/templates/template-types.html and https://helix.sitecore.net/principles/security/workflows.html So it would seem that there is a discrepancy between the Helix ...


5

The simplest way will be just removing the Default workflow from the existing template's standard value and update/enable it back when needed. Also the new templates needs to be created without any default workflow and setup later when needed. Note - If you have lot of existing templates, can try execute a power-shell command to set/revoke default workflow. ...


4

It is a dictionary item in core database. So go to the core, open Content Editor. Search for this item: /sitecore/system/Dictionary/S/Some of the fields in this item contain critical errors Are you sure you want to save this item. Here you can set the Phrase to your language.


4

I'll try and answer some of these questions. It does sounds like this setting will do what you want, and by default it's enabled in 8.2: <setting name="WebEdit.AffectWorkflowForDatasourceItems" value="true" /> There doesn't seem to be any documentation for the new workflow features of 8.2 yet but based on the info here it suggests that components ...


4

In my case we have a load balancer terminating TLS and then passing decrypted traffic to the backend CM server on port 80. The only solution we could get working is to add a the header Content-Security-Policy to the Web.config with a value of upgrade-insecure-requests. Now Chrome does not block the execution of the link but rather upgrade to https. ...


4

To stop your site from serving mixed content, you will need to ensure that HTTPS is used for all pages. How exactly you achieve this is up to you; there are several existing approaches that you can apply separately or together: Add scheme="https" to all site definitions. You may need to add port="443" to your site definitions as well, but then you'll ...


4

Security is stored on the content items themselves so it's likely that when you deployed the workflow items through TDS to your QA environment, those items contain, in plain text, the names of the Security Roles that you configured on them in your DEV environment, even though the actual Security Roles haven't been created in your QA Core database. To see ...


4

You can't find any new fields there out of the box. But Sitecore recently introduced the Standard Comment Template, thereby making it possible to cook up more advanced authoring scenarios. Grant Bartlett has a good example of what that could look like in Sitecore 8: Advanced workflow commenting In short; it was changed because Sitecore now has the ability ...


4

This post is an old one from Alex Shyba: http://sitecoreblog.alexshyba.com/who_moved_the_item_to_the_workflow_state/ It highlights a way to go back through the workflow history to find a user. This can be more accurate than going to the Created field as an item might go through workflow multiple times, or the user that created an item might not be the one ...


4

deep parameter support just two values "1" and "other value" I describe above all parameters what they are doing. You need to override PublishAction to handle deep publishing on multiples level. Publish action accepts 6 parameters: "deep" - controls whether children of the current item will be published. Possible values: "1" - children of the current ...


Only top voted, non community-wiki answers of a minimum length are eligible