since ‎07-06-2018
‎11-11-2020
prahladd9593982
Level 2
Re: How to modify the threshold value of "org.apache.sling.healthcheck: requestsStatus (HealthCheck)"
Avatar

prahladd9593982

prahladd9593982
- Adobe Experience Manager
Correct.I have raised a adobe support ticket regarding the same and had a conversation with adobe person it is not possible to change the threshold value as it is hardcoded inside java code - RequestsStatusHealthCheckImpl.java and they don't have any future enhancement for the same.They have suggested if require you can write a custom health check class to make it configurable accordingly.https://helpx.adobe.com/in/experience-manager/6-3/sites/administering/using/operations-dashboard.html#Health...

Views

921

Likes

0

Replies

0
Re: Classic UI | Unable to add or move components inside "Experience Fragment Container"
Avatar

berliant

Employee

berliant
- Adobe Experience Manager
Experience and Content Fragment components are not designed for Classic UI. It's expected to be used in Touch UI.

Views

1.2K

Like

1

Replies

0
Re: AEM6.4 | DAM queue issue | Upload a pdf file, it always shows “processing” status
Avatar

prahladd9593982

prahladd9593982
- Adobe Experience Manager
I found the root cause of this issue.https://forums.adobe.com/thread/2393368In my workflow last two steps were missing “Dam update asset workflow completed” and “send transient workflow completed email”Also two configuration were missingAfter Added above configuration the issue were solved.

Views

647

Likes

0

Replies

0
Re: Unable to create a page by providing only title after upgrade AEM6.2 to AEM6.4
Avatar

sampath_kumar_g

sampath_kumar_g
- Adobe Experience Manager
Yes We are also facing the same issue after the upgrade. Do we have any process to get back how the pages used to behave in AEM 6.2Earlier Behavior : When we used to create pages in AEM 6.2, while creating a page in AEM 6.2, even though when we haven't entered any "Name" for the page, AEM would be taking the title of the page as Name.But, we are missing this behavior after upgrading our application from AEM 6.2 to AEM 6.4. Can we get any resolution for this. Or any fixes via service packs or cod...

Views

2.6K

Likes

0

Replies

0