Skip to main content
added 406 characters in body
Source Link

I've a question on what the expected behavior would be this scenario:

Scenario: Content updated in WFBundle and then updated outside of WFBundle.

No minimum approval status set on STAGE Minimum approval status is set on LIVE

Component is created – v1.0

Component added to a WFBundle and WFBundle is activated

Component is edited through workflow bundle – creating v1.1

  • Publish to stage : v1.1
  • Publish to live : v1.0 (as expected as doesn’t meet approval status)

Workflow bundle is complete

  • Publish to stage : v2.0
  • Publish to live : v2.0 (as expected as it now meets approval status)

Component is edited (outside of active workflow bundle)

  • Publish to stage : v3.0
  • Publish to live : v3.0 (not expected as this has previously been through WF and the approval status is updated to Undefined when component is saved – I would have through this would set to the lowest in the workflow (i.e. one above Unapproved))

UPDATE My assumption comes from several blog postings and the documentation that indicate the minimum approval status is adhered to irrespective of the item being in workflow or not.

Also, regarding the update of the approval status to undefined - I've seen there is a hotfix 88203 that may be related to this - but it's stated this is part of the HR1 Roll-up which should have been applied.

UPDATE 2 We have the noted version of the DLL per the response from Chris (below) and quoted in the documentation - however, that version of the DLL didn't have this hook in it. We've checked the version in the GAC and this does have the hook! We're checking the upgrade steps to see if this is an error on our part or something wrong in the upgrade - if you've any info on this, please share here?

I've a question on what the expected behavior would be this scenario:

Scenario: Content updated in WFBundle and then updated outside of WFBundle.

No minimum approval status set on STAGE Minimum approval status is set on LIVE

Component is created – v1.0

Component added to a WFBundle and WFBundle is activated

Component is edited through workflow bundle – creating v1.1

  • Publish to stage : v1.1
  • Publish to live : v1.0 (as expected as doesn’t meet approval status)

Workflow bundle is complete

  • Publish to stage : v2.0
  • Publish to live : v2.0 (as expected as it now meets approval status)

Component is edited (outside of active workflow bundle)

  • Publish to stage : v3.0
  • Publish to live : v3.0 (not expected as this has previously been through WF and the approval status is updated to Undefined when component is saved – I would have through this would set to the lowest in the workflow (i.e. one above Unapproved))

UPDATE My assumption comes from several blog postings and the documentation that indicate the minimum approval status is adhered to irrespective of the item being in workflow or not.

Also, regarding the update of the approval status to undefined - I've seen there is a hotfix 88203 that may be related to this - but it's stated this is part of the HR1 Roll-up which should have been applied.

I've a question on what the expected behavior would be this scenario:

Scenario: Content updated in WFBundle and then updated outside of WFBundle.

No minimum approval status set on STAGE Minimum approval status is set on LIVE

Component is created – v1.0

Component added to a WFBundle and WFBundle is activated

Component is edited through workflow bundle – creating v1.1

  • Publish to stage : v1.1
  • Publish to live : v1.0 (as expected as doesn’t meet approval status)

Workflow bundle is complete

  • Publish to stage : v2.0
  • Publish to live : v2.0 (as expected as it now meets approval status)

Component is edited (outside of active workflow bundle)

  • Publish to stage : v3.0
  • Publish to live : v3.0 (not expected as this has previously been through WF and the approval status is updated to Undefined when component is saved – I would have through this would set to the lowest in the workflow (i.e. one above Unapproved))

UPDATE My assumption comes from several blog postings and the documentation that indicate the minimum approval status is adhered to irrespective of the item being in workflow or not.

Also, regarding the update of the approval status to undefined - I've seen there is a hotfix 88203 that may be related to this - but it's stated this is part of the HR1 Roll-up which should have been applied.

UPDATE 2 We have the noted version of the DLL per the response from Chris (below) and quoted in the documentation - however, that version of the DLL didn't have this hook in it. We've checked the version in the GAC and this does have the hook! We're checking the upgrade steps to see if this is an error on our part or something wrong in the upgrade - if you've any info on this, please share here?

Tweeted twitter.com/StackTridion/status/677435656277245952
updated to acknowledge check from Nuno's comment
Source Link

I've a question on what the expected behavior would be this scenario:

Scenario: Content updated in WFBundle and then updated outside of WFBundle.

No minimum approval status set on STAGE Minimum approval status is set on LIVE

Component is created – v1.0

Component added to a WFBundle and WFBundle is activated

Component is edited through workflow bundle – creating v1.1

  • Publish to stage : v1.1
  • Publish to live : v1.0 (as expected as doesn’t meet approval status)

Workflow bundle is complete

  • Publish to stage : v2.0
  • Publish to live : v2.0 (as expected as it now meets approval status)

Component is edited (outside of active workflow bundle)

  • Publish to stage : v3.0
  • Publish to live : v3.0 (not expected as this has previously been through WF and the approval status is updated to Undefined when component is saved – I would have through this would set to the lowest in the workflow (i.e. one above Unapproved))

UPDATE My assumption comes from several blog postings and the documentation that indicate the minimum approval status is adhered to irrespective of the item being in workflow or not.

Also, regarding the update of the approval status to undefined - I've seen there is a hotfix 88203 that may be related to this - but it's stated this is part of the HR1 Roll-up which should have been applied.

I've a question on what the expected behavior would be this scenario:

Scenario: Content updated in WFBundle and then updated outside of WFBundle.

Component is created – v1.0

Component added to a WFBundle and WFBundle is activated

Component is edited through workflow bundle – creating v1.1

  • Publish to stage : v1.1
  • Publish to live : v1.0 (as expected as doesn’t meet approval status)

Workflow bundle is complete

  • Publish to stage : v2.0
  • Publish to live : v2.0 (as expected as it now meets approval status)

Component is edited (outside of active workflow bundle)

  • Publish to stage : v3.0
  • Publish to live : v3.0 (not expected as this has previously been through WF and the approval status is updated to Undefined when component is saved – I would have through this would set to the lowest in the workflow (i.e. one above Unapproved))

UPDATE My assumption comes from several blog postings and the documentation that indicate the minimum approval status is adhered to irrespective of the item being in workflow or not.

Also, regarding the update of the approval status to undefined - I've seen there is a hotfix 88203 that may be related to this - but it's stated this is part of the HR1 Roll-up which should have been applied.

I've a question on what the expected behavior would be this scenario:

Scenario: Content updated in WFBundle and then updated outside of WFBundle.

No minimum approval status set on STAGE Minimum approval status is set on LIVE

Component is created – v1.0

Component added to a WFBundle and WFBundle is activated

Component is edited through workflow bundle – creating v1.1

  • Publish to stage : v1.1
  • Publish to live : v1.0 (as expected as doesn’t meet approval status)

Workflow bundle is complete

  • Publish to stage : v2.0
  • Publish to live : v2.0 (as expected as it now meets approval status)

Component is edited (outside of active workflow bundle)

  • Publish to stage : v3.0
  • Publish to live : v3.0 (not expected as this has previously been through WF and the approval status is updated to Undefined when component is saved – I would have through this would set to the lowest in the workflow (i.e. one above Unapproved))

UPDATE My assumption comes from several blog postings and the documentation that indicate the minimum approval status is adhered to irrespective of the item being in workflow or not.

Also, regarding the update of the approval status to undefined - I've seen there is a hotfix 88203 that may be related to this - but it's stated this is part of the HR1 Roll-up which should have been applied.

added 519 characters in body
Source Link

I've a question on what the expected behavior would be this scenario:

Scenario: Content updated in WFBundle and then updated outside of WFBundle.

Component is created – v1.0

Component added to a WFBundle and WFBundle is activated

Component is edited through workflow bundle – creating v1.1

  • Publish to stage : v1.1
  • Publish to live : v1.0 (as expected as doesn’t meet approval status)

Workflow bundle is complete

  • Publish to stage : v2.0
  • Publish to live : v2.0 (as expected as it now meets approval status)

Component is edited (outside of active workflow bundle)

  • Publish to stage : v3.0
  • Publish to live : v3.0 (not expected as this has previously been through WF and the approval status is updated to Undefined when component is saved – I would have through this would set to the lowest in the workflow (i.e. one above Unapproved))

UPDATE My assumption comes from several blog postings and the documentation that indicate the minimum approval status is adhered to irrespective of the item being in workflow or not.

Also, regarding the update of the approval status to undefined - I've seen there is a hotfix 88203 that may be related to this - but it's stated this is part of the HR1 Roll-up which should have been applied.

I've a question on what the expected behavior would be this scenario:

Scenario: Content updated in WFBundle and then updated outside of WFBundle.

Component is created – v1.0

Component added to a WFBundle and WFBundle is activated

Component is edited through workflow bundle – creating v1.1

  • Publish to stage : v1.1
  • Publish to live : v1.0 (as expected as doesn’t meet approval status)

Workflow bundle is complete

  • Publish to stage : v2.0
  • Publish to live : v2.0 (as expected as it now meets approval status)

Component is edited (outside of active workflow bundle)

  • Publish to stage : v3.0
  • Publish to live : v3.0 (not expected as this has previously been through WF and the approval status is updated to Undefined when component is saved – I would have through this would set to the lowest in the workflow (i.e. one above Unapproved))

I've a question on what the expected behavior would be this scenario:

Scenario: Content updated in WFBundle and then updated outside of WFBundle.

Component is created – v1.0

Component added to a WFBundle and WFBundle is activated

Component is edited through workflow bundle – creating v1.1

  • Publish to stage : v1.1
  • Publish to live : v1.0 (as expected as doesn’t meet approval status)

Workflow bundle is complete

  • Publish to stage : v2.0
  • Publish to live : v2.0 (as expected as it now meets approval status)

Component is edited (outside of active workflow bundle)

  • Publish to stage : v3.0
  • Publish to live : v3.0 (not expected as this has previously been through WF and the approval status is updated to Undefined when component is saved – I would have through this would set to the lowest in the workflow (i.e. one above Unapproved))

UPDATE My assumption comes from several blog postings and the documentation that indicate the minimum approval status is adhered to irrespective of the item being in workflow or not.

Also, regarding the update of the approval status to undefined - I've seen there is a hotfix 88203 that may be related to this - but it's stated this is part of the HR1 Roll-up which should have been applied.

Source Link
Loading