Thanks for getting back @arunpatidar  what we need is to create a custom schema with ALL the default tabs/fields AND additonally a custom tab with custom fields. We need to be able to do this for few different custom schemas and not just one. What we did was to copy the default schema and customised...

Thanks for sharing the screenshot @daniel-strmecki - We named our custom schema as <tenant_name>_schema and not used default as-is - I see above that you have modified or added  a custom tab within the default schema directly. Also we have multiple metadata schemas which are different to 'default'. ...

thanks for feedback @daniel-strmecki Our use case is to have the default and also our custom tabs.When I did the above I see only the custom tab but none of the inherited default tabs. We are on AEM as a cloud service. Is it possible to "inherit" default and append custom tabs in the metadata schema...

exactly - the code sample above for include is where I misunderstood (highlihted below)- our use case is to create a custom schema using the default and change them for our customer needs. The steps we took 1.Copy the default schema 2.Rename it to <customer_schema>3.Add new tabs (we have atleast 25+...

Thanks the path above now makes sense - "/apps/oneweb/aemlab/components/dialogs/dam/metadata/custom-tab/tabs We did not have the page property requirement so we were trying to include from libs above which was not working as expected due to schema form validations.

Hi @arunpatidar The above code snippet shows the path as being used directly from libs  path="/libs/dam/content/schemaeditors/forms/default/items/tabs/items/tab1/items/col1" />In the latest version of aem as a cloud service SDK - when I do this it does not load the schema ...

Hi @kautuk_sahni - Thanks for following up I am still requiring details on my question as outlined above.

Hi all Any inputs on this as we are still not able to control the time/day of version purging following these steps. Any one using this currently in their projects?

Hi @MukeshYadav_  @TarunKumar , Steps followed are outlined below: Create a MaintenanceTask.yaml (or any preferred name) file as specified in the Adobe documentation, including all properties for both version and audit purge configuration.Place this file in the top-level config folder of the codebas...

Thanks, @TarunKumar, for the response! I'm specifically looking for details about AEM as a Cloud Service. The links you shared cover AEM 6.5, but for AEM as a Cloud Service, we’d handle this through the config pipeline, correct? And this configuration would apply in future releases, not currently?