Is this for AMS or Cloud Service?   In AEM Cloud Service, you cannot install parts of the code base, every deployment creates a new image and your complete code package has to be deployed every time. If Cloud Service is on the roadmap already, I'd try to stick to the best practices for that. Even th...

@Shashi_Mulugu this again is a difference that comes with Cloud Service. I highly recommend you watch the adaptTo recordings from last year for the feature model. In the build image step of the pipeline, it is decided which osgi config will be applied to the environment. This is based on the runmode...

There are a couple of issues going on here. There is no “test” runmode in Cloud Service. Looks you have configurations under that runmode. Please read the Cloud Service documentation on which runmodes are supported This error is shown when you have multiple configs with the exact same PID in your co...

The doc does state that the functional tests are ran against the Cloud Service stage environment _after_ the stage deployment, this should fix your issue.

@joannaj49016259 Each release is validated against customer instances before being classified as safe and pushed out. If you write unit tests and functional tests using https://docs.adobe.com/content/help/en/experience-manager-cloud-service/implementing/developing/understand-test-results.html#writin...

Hi @joannaj49016259, you should be compiling your code using Java 8, until Cloud Manager supports Java 11 and running your AEM as a Cloud Service SDK locally using Java 11. HTH. 

the validation happens client side. Not in the file you mention above. Below is a sample to make the fileupload widget required, you can use the same. (function(document, $, Granite) {   "use strict";   var CLASS = ".coral-FileUpload-input",   DATA_VALIDATION_VALUE = "fileupload-required",   fieldEr...

With 4 publishers and dispatchers, 1000 consecutive requests should be a breeze. Are you sure your requests are being cached appropriately? Are you activating pages while running these tests? This might be an issue further down the request chain and not something that should be fixed on the web serv...

Does the value need to be hardcoded in AEM? or simply registering "mydam" as a namespace and adding "mydam:gDubz" as a schema property of PDFs within a specific folder enough? Just registering the namespace "mydam" is enough. Then you can have custom properties for the name space like mydam:prop1 an...

If you are adding custom properties, you'll definitely need to update the metadata schema. Whether you create a profile or not depends on whether you want the metadata values to be populated automatically. For example, if you wanted to add a new property to PDFs called mydam:gDubz and want it to be ...