I have also encountered this issue on an AEM 6.5 instance after
upgrading from AEM 6.2 (fresh install). Apparently this issue was caused
in our case due to using the crx2oak migration tool to migrate
content-pages and assets. It turned out that for some reason the user
"workflow-process-service" lost all the ACL permissions on the node
"/content" which it requires to complete the DAM asset update workflow.
Hello,I also encountered this issue in AEM 6.5. The official
documentation is not very helpful when talking about how to get your
custom workflow into the system.Adobe Experience Manager Help | Common
Repository Restructuring in AEM 6.4 From a UX point of view it's not
good that you have to open a default workflow and change the URL in the
browser's address to your custom model. Also I was not able to find that
"sync button" mentioned at the 3. point when I have a workflow model
open in the edit...
Hey Scott, thanks for the reply. I thought that there might be something
(like a property) missing which would fix the issue. Unfortunately the
extension of that part isn't described in high detail, so it's more
trial and error.
For one of our customers we created a corporate asset database in AEM
6.1 (SP2) with a heavily customized asset administration in the Touch UI
for the asset metadata properties. For that we have created our own DAM
schema and stored it under /apps/dam/content/schemaeditors/forms (see
the attached schema.txt). The asset authors can choose the image type
which changes which property tabs are visible. Some of these properties
are stored as Boolean property values.Now during an bulk edit of the
Hello everyone,I just installed the Service Pack 3 which was released a
few days ago on my local AEM 6.0
after the installation the project I'm working on displays an error when
rendering a page. It says "ReferenceError: "granite" is not defined.".
It looks like it's a Sightly related issue since there are no errors in
the JSP-based Geometrixx projects like Geometrixx-Media. My page
component uses "wcm/foundation/compo...
I learnt the solution to how to extend hbs script of the SCF components.
Since the logic is processed on the server side (instead of the client
side), the extended component's factory service
(com.adobe.cq.social.commons.comments.api) needs to be extended in
Java.Example:@Component(name = "My News Comment System Component
Factory") @Service public classNewsCommentSystemComponentFactory extends
CommentSystemSocialComponentFactoryAlso the component created by the
factory needs to be extended and h...
Hello,I'm trying to extend the comments component
(resourceSuperType="social/commons/components/hbs/comments"). I want to
limit the comments number to 1 per user in a comment system.I managed to
get it running and altered the HBS script to my needs, but neither can I
find a HBS template property which tells me if the current user already
wrote a comment, nor will the system allow me to register new HBS
helpers or HBS attributes.For the helper I tried to add a simple
conditional helper. It shows ...
Hey guys, thanks for the quick reply.smacdonald2008 wrote... To get this
straight - this works sometimes and you see this error other times? It
worked for the past months, then about a week ago I started getting the
error on the customer's staging system. Now I also get it on the
test-system. Yesterday I managed to get 1-2 occurences of "Page
successfully activated" but then right afterwards it didn't work. It
still works fine on my local instance. I thought that one of the