Hi Team,
I am using AEM forms to capture user inputs. I am deploying the configuration updates on the fragment like the pattern (regular expression), max length, css changes on the fields. I can see that configuration changes which i did are present when viewed via CRX, but it does not reflect on the page where the fragment is added.
It would be great if someone can share the resolution for the same.
Thanks,
Raghu
Solved! Go to Solution.
Views
Replies
Total Likes
The adaptive form fragment is inserted by reference in the adaptive form and is synchronized with the standalone adaptive form fragment. So when you're updating the adaptive form fragment configuration, the changes should reflect in all adaptive forms where the fragment is used, more info[0].
Can you check the following:
If a Publish instance, please republish the updated adaptive form fragment.
A quick check, to see if the fragments are not embedded in the Form.
Views
Replies
Total Likes
The adaptive form fragment is inserted by reference in the adaptive form and is synchronized with the standalone adaptive form fragment. So when you're updating the adaptive form fragment configuration, the changes should reflect in all adaptive forms where the fragment is used, more info[0].
Can you check the following:
If a Publish instance, please republish the updated adaptive form fragment.
Re-publishing the adaptive form fragment helped resolve the issue. But do you know if there is any specific reason why it does not reflect, even though configuration is already present on both author and publish instance. I mean this should start reflecting once the latest configuration is deployed right. Please share your thoughts
Views
Replies
Total Likes
Haven't tried deploying the configuration changes as such, but it seems the properties were present in the repo but not published for this fragment.
BTW, how are you making the configuration changes to a fragment?
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies