Sign in to Community
Sign in to view all badges
Expand my Community achievements bar.
When creating a content fragment model, the data types "multi line text", “number field” and "enumeration" are missing the following properties:
We are using the latest 6.5 FP. Is it that feature on a roadmap ? Can we expect it in future releases ? Or should we request an evolution to add these fields ?
Below is a snapshot showing the properties of the multi line text, we see that these 2 options are missing:
Note: using the table kept deleting the content of my request so not using it...
You can contact the support team or your Adobe representative in the account to find out whether the feature is in the roadmap or not.
Please note that this section of the community is dedicated to feature requests for AEM. So it is not clear to me if this is a feature request or a question that should be asked in other relevant section of the community OR AEM support. Please see the guideline on how to submit a feature request. Thanks
Right, the questions may be misleading but it is a feature request.
I already posted on this same topic in the main forum, where they recommended to post here, and contacted the support team on this topic.
And as mentioned, I tried to use the template multiple times but the content of the table just kept being erased (HTML issues). That's why the post does not have any particular format. All the information is there though.
Thanks for clarification. Can you clarify the following:
Here are my answers
Content fragments exist to be consumed by APIs and that is precisely how we plan on using them. As for any API, there are certain constraints that need to be respected and we do not want to put that burden on the users. Instead, we prefer to guide them through the UI to prevent them from doing mistakes. Also, these content fragments are used in in a legal project and we want to have as many safeties as possible.
No, I just mean that they are not there.
As mentioned, this will guarantee a safeguard since we are in a legal context.
This request has been raised to the product team via the Jira CQ-4316685. The product team will triage this request to verify feasibility based on prioritization model. This post will be updated according to the Jira request status.
Excellent, thank you