issues
search
adobe
/
aem-project-archetype
Maven template to create best-practice websites on AEM.
https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/archetype/overview.html
Apache License 2.0
533
stars
409
forks
source link
OOTB Core Component Adaptive Form templates and themes updates
#1155
Closed
pankaj-parashar
closed
7 months ago
pankaj-parashar
commented
7 months ago
Removal of panel for submit button for log service request. Keeping as is for other templates
Left aligned Submit button (all templates) - Remove resizing from layout layer
Benefits Summary Request -
Text title -
Form Introduction
Text name -
FormIntro
Benefits Enrollment template -
Rule fixing for Others panel.
Top panel title changed to
Basic Details
Submit button changed from generic button to actual submit button
Consent Form - Top panel name changed to
events
Contact Details Update - Text titles changed to
Form Introduction
and
New Address
Give Feedback - Panel
title
and
name
changed to
Feedback
and
feedback
respectively
Log Service Request template -
Renaming Tabs on Top title and name to Service Request/servciceRequest.
Moved submit button out of panel and removed the panel
Purchase Request - Text title -
Form Introduction
Quality Control Inspection - Text title -
Form Introduction
Request for statement - Text title -
Form Introduction
Safety Inspection -
Text title/name ->
Instructions
/
instructions
Renaming Tabs on Top title and name to
Safety Inspection
/
safetyInspection
.
Replaced foundation component usage by core components
Container instead of foundation parsys
Header and footer policy updated for all the templates
Telphone
field pattern validation fixed
Email
field type fixed
Template type updated
Read for everyone ACL
added for themes for publish use case
Configured
REST endpoint
submit action
Disable date rule in safety-inspection template
Description
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[ ] I have signed the
Adobe Open Source CLA
.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the
CONTRIBUTING
document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
Description
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: