Hi,
Thanks for the response.
Content will be authored with in an app and a website, we would want to proxy Alfresco through an ESB, and the App would be going through a MBaaS layer. My vision is to allow clients (app/web) to dynamically render forms based on the template definition, and for a single API to be used that all content (for all different forms) can be submitted through, to in a generic way, validated, then stored in Alfresco. i.e One end point handling many forms.
From what I've understood so far:
Alfresco would not directly support the concept of creating a form definition, which Alfresco could then use to validate submitted content against when a user tries to store data.
So we would use Alfresco to store the content only, and build a validation layer outside of Alfresco to ensure all captured fields are completed as needed. It is likely that we would just store JSON data to represent user entered data.
I looked at Aspects, but my usecase would be misusing the functionality I believe.
Potentially if Alfresco is only storing, and cannot master templates and validate the content, I may as well just go with a database instead…It is just we have Alfresco on the estate and I'm wondering if it can help support this solution
Thanks,
Sky