The Collection selector in the Collection Display fragment configuration must support selecting configurable collection provider. When one is selected by the user, the configuration UI must provide, below the collection selector, one field for the of the parameters declared by the Configurable Collection Providers.
The fields shown to the user must be rendered dynamically based on the form definition provided by the specific Collection Provider that the user has selected as defined by
Developers declaring a new parameter for a Collection Provider or Related Item Collection Provider
Given a developer has created a related item collection provider or a Collection Provider
When a new parameter is declared in a related item collection provider or a Collection Provider by a Developer
Then a Page creator can modify the parameters values for that related item collection provider or a Collection Provider by configuring the parameters
Configuring the pre-filtering parameters from the Page Editor
Given the Page creator has already selected a related item collection provider or a Collection Provider **
When a DPT Author is accessing the related item collection provider configuration via the "Filter Collection" button
Then a pop allows a DPT Author to modify the parameters values for that related item collection provider
- Does this feature modify something already existing in the product?
- Why is the change proposed?
And example would be:
Does this feature modify something already existing in the product?
Yes, it removes the section component and replaces it with the container component. Existing section components should be replaced with two containers. One with fluid width, and an inner one with fixed width.
Why is the change proposed?
** Section component is more rigid, the container is more flexible allowing more use cases.
During or after the kickoff, the developer would fill a third section:
- Is an upgrade needed?
In this section they would define the steps needed for the upgrade if necessary.
Some example would be:
Is an upgrade needed?
1: We have to create an upgrade process because the properties of the section won’t be compatible with the new container component.
: No upgrade process needed since when reading the properties of the section we will swap it with the new one.
: Nothing to be done, this is already backwards compatible