When Approving An Asset in Workflow the Corresponding CompositionSlot_C Asset Is Not Approved Automatically (Doc ID 2051157.1)

Last updated on APRIL 30, 2021

Applies to:

Goal

Scenario:

For an asset that is associated in the slot (CompositionSlot_C)

 - If the asset is updated/modified outside a workflow, on approval the asset is Held by the corresponding CompositionSlot_C asset, and Sites would prompt the user to approve the blocking CompositionSlot_C asset.

 - If the asset is updated/modified inside a workflow, and is approved using a Step Action, e.g. OpenMarket/Xcelerate/Actions/Workflow/StepActions/ApproveForPublish, then Sites displays a message indicates that the asset is approved, while it's actually Held by the corresponding CompositionSlot_C asset.

Is this a behavior by design? How to workaround the issue?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.