Asset Associations with Parent Subtype and Child Asset Type defined Does Not Work the Same in Web Mode and Form Mode
Last updated on OCTOBER 05, 2015
Applies to:Oracle WebCenter Sites - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
When using Asset Associations that define a specific parent subtype and a child asset on assets to control what contributors can drop in the association field on a template, the drop zone field restrictions do not work the same in both Form mode and Web mode.
1) In Form mode, the contributor will be able to drop the right asset into asset association field/drop zone, but in Web mode it will not work. An error message box will open with the following type of message "This slot only accepts assets of type Media (Product)", for example.
2) In order to get Web mode to work, the asset association should have the parent subtype removed but leave the child asset. This change allows the user to only drop assets of the child asset in to the asset assocation field/drop zone. However, now the Form mode will allow the ANY parent asset subtype for this association field/drop zone. This is not the desired behavior for the Form mode.
Note: For the insite:calltemplate tag, one could add the clegal argument to the insite:calltemplate tag to restrict the parent asset subtype in Web Mode. However, observations show that this is not working as noted in Bug 18291273 - ASSOCIATIONS CREATED FOR SPECIFIC SUBTYPES ARE NOT PERMI
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms