Skip to main content

Demystifying Workflow, Blueprint, Publish and Actions You Can do With Such Items

I was playing around a while ago with some Components in Workflow, in Blueprinted situation, when I noticed some strange behaviour.

I was trying to place a v0.x Component (in Workflow) on a Page in a child Publication -- can't do.
I was publishing a Component linking to a Component in Workflow. It works, but it will use the values from the last saved 'link-to' Component -- makes sense. But even when publishing with ActivateBlueprint=true, still the last major version of the 'link-to' Component was used.

This all triggered me to summarize these weird cases, as follows:

  • A _new_ Component (version 0.x) in workflow:
    • is visible in its own and child Publications (GUI & API);
    • can be published in its own and/or child Publication (GUI & API using the “ActivateWorkflow” flag). Publishing follows most of the rules we know (DCPs get published, Page republished if published previously), but some don’t actually work as expected: Components “linking-to” the Component in workflow will see the ‘last checked-in’ version of the Component in workflow;
    • can be put on a Page as CP:
      • in its own Publication – (GUI & API);
      • in child Publication – only API (because minor version new Component is not visible in GUI’s CP selector);
  • An _existing_ Component does all the above (it can even be put on a Page in a child Publication both in GUI and API)


Note: Be careful with the implications of placing a v0.x of a Component on a Page: you are responsible for cleaning up the Page (remove CP, unpublish Page, delete Page), in case you reject the Component (or if you abort the Workflow Process). If you don't, then Tridion will throw an error that the Component is used and cannot be deleted -- which makes perfect sense...

Comments

Nivlong said…
Context matters! Minor component versions not being available for pages CPs is seemingly subtle, but significant behavior. It makes sense, though. As a content author, I'd expect to see the last approved version of a component. Thanks for clarifying, Mihai--great post!

I imagine that clean up step gets more complicated the more we add to the page or link components. Deleting a "used" item aint easy!
Unknown said…
can we publish the minor version(v0.x) of Component only in workflow. when i tried it was not publishing, it is publishing only the major version of the component. please let me know if it is possible to publish minor version.
Mihai Cădariu said…
Yes, Sunil. It is possible. In the GUI, you have to publish the minor version Component from the workflow screens (or in Tridion 2013, with publish option "If possible, publish the in-workflow version of an item").

Using the TOM API, you will need to publish with a ResolveInstruction that has property IncludeWorkflow set to true.

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven