In AEM as a Cloud Service you cannot control individual instances; especially the number of publish instances is dynamic and you cannot designate any of them in a way "special" (for example to execute a specific job and then send you those emails).
In your case it all depends why you send these em...
As already mentioned by the others, this is not possible. But it is also not necessary, because the access control layer on AEM checks if you are allowed to access binaries, and there is no other way to access binaries than going through AEM and these checks.That means if you want to have APP-1 not ...
Assuming that this is the only Excel file which needs this kind of handling, and that there are no other (access) restrictions on it:Read that file on startup in an optimized in-memory structure, which allows you to perform these required search operations efficiently. This should be done in a dedic...
I am not entirely sure, but you could try something like this as the entry of the value.["value1","value2","value3"] That should be parsed as multi-value.
I don't think that this is the case. When you were using SCR annotations, it did not matter if you annotated the @component annotation with additional properties or if you were providing them inline (and configurable). But technically this was not correct, as there is a disctinction between those pr...
Hi, I don't understand why you need to read the structure of the template in your own code. In the majority of all cases it should be sufficient to let AEM drive the resolution of the components and just implement the rendering of these components.Deducing the structure of the page (that means the c...
Hi, I recommend to raise that question on the ACTool github project, and please also include some more details regarding the exception.(Millions of users in the JCR sounds a bit problematic too me...)