-
Type:
Story
-
Status: Closed
-
Priority:
Minor
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: Master
-
Component/s: Fragment Administration, Pages > Page Editor
-
Epic/Theme:
-
Epic Link:
-
Git Pull Request:
As a page editor, I want to be able to add a form container so I can create / embed forms on pages.
Design
https://www.figma.com/file/LQpQkrST4pVylqiCKMvbW6/?node-id=3%3A471
Acceptance Criteria
- A new form container fragment will be available under the "Forms components" section in the page editor (see
LPS-151867) - The new form container has to include all capabilities of the regular container (common styles, suitable for saved compositions, hide from search, hide / show fragment).
- When dragging and dropping the form container to the page, the side bar will show:
- For display page templates:
- the "source" field will show the item that was selected when creating the DPT as default option
- the user can also select "Other Content", and then a dropdown "Content type" with the list of available entities for it to be mapped to will be shown. In case the item type has subtypes, these will be displayed in a second dropdown selector "Content subtype".
- In content pages, the Content Type selector will display a list of all the available entities to be mapped.
- In case the item type has subtypes, these will be displayed un a second dropdown selector.
- For display page templates:
- The user won't be allowed to add fragments to the form container if it's not mapped to any entity.
- If the form container has been mapped to an entity and there are mapped fragments inside, when unmapping the container it is returned to the empty state.
Note: warnings will be tackled in other story (LPS-152107)
Test Scenarios
Test Scenarios | Test Strategy | Kind of test | Is it covered by FrontEnd ? (JS-Unit) | Is it covered by BackEnd ? (unit or integration) | Could it be covered by POSHI? |
---|---|---|---|---|---|
The page editor could map entity to Form Container in display page template | Critical | Manual | No | No | Yes |
The page editor could map entity to Form Container in content page | Critical | Manual | No | No | Yes |
The page editor cannot add fragment into Form Container without mapping entity | High | Manual | No | No | Yes |
The Form Container will be back to empty state once unmapping entity even though there are fragments inside Form Container | High | Manual | Yes | No | Yes |
The Form Container has all capabilities of Container | High | Manual | No | No | Yes |
- is related to
-
LPS-157785 Form Container should also have "Content display" and "Content width" configurations
- Closed
-
LPS-154264 LPS-149984 - Product QA | Test Automation Creation
-
- Closed
-
- Testing discovered
-
LPS-153314 Cannot add a fragment surround the Form Container when not map entity
- Closed