since ‎14-11-2017
‎16-06-2020
lutzu70088640
Level 1
Re: Notification of deployed fixes
Avatar

lutzu70088640

lutzu70088640
- Adobe Experience Manager
Sorry, but I doubt that this feedback process in the case is really exsiting. At least from the past the original case was NOT updated once the fix was out. And also, the suppoer answer that I gave you as an example does not fit to your statement - why I should I monitor the CQ-number although I get notified via an update of the case? So, I would really appreciate to check to process. Is it is like you said, that there is already a process that the connected case get's updated, then that's perfe...

Views

518

Likes

0

Replies

0
Re: Notification of deployed fixes
Avatar

lutzu70088640

lutzu70088640
- Adobe Experience Manager
Yes, but that's not the point. From my ticket I get such unswers "... I would request you to please monitor the CQ-4298048 inclusion of the fix for your issue on the future release notes of the coming versions or service packs/CFPs on our official online documentation/ release document. " And here, I would like to have an automated notification in order not to check the release not for my several CQ-number bugs.

Views

1.0K

Likes

0

Replies

0
Notification of deployed fixes
Avatar

lutzu70088640

lutzu70088640
- Adobe Experience Manager
I don't know it is the correct place, but customer care recommended to post this here. Basically I have an enhancement request regarding the new Support portal (former daycare.day.com) within Admin Console. I often have the case that a reported issue was confirmed as a bug, got a internal Adobe CQ-number and will be fixed in a later release. When it will be included is not clear, and I as a customer are asked to check release notes. I would be really happy if I can get some notification in the t...

Views

1.0K

Likes

0

Replies

5
Re: cq-msm-lockable not working for component level properties in touch ui
Avatar

lutzu70088640

lutzu70088640
- Adobe Experience Manager
Hi,we have also raised a support ticket to get an answer how to break inheritance on field level within the component. Re: Field Level Inheritance - MSM For Classic UI (AEM 6.1) it seems there is a "hidden" property but I don't know about touch UI so far.From Business perspective breaking the inheritance on component level only, with having all fields cancelled at once, does NOT match the real live requirements of multilanguage websites for large company with hundreds of websites...

Views

814

Likes

0

Replies

0
Re: [Q&A | January 2018] Ask the AEM Community Expert: Using Multi-site Management with AEM
Avatar

lutzu70088640

lutzu70088640
- Adobe Experience Manager
Hi, I'm trying to find someone that can help with a question which relates to question 22) here. It's about the property "fieldEditLockMode"I would appreciate if someone could help to answer this question here:Re: Field Level Inheritance - MSM Thx!

Views

3.5K

Likes

0

Replies

1
Re: Field Level cancelled Inheritance getting lost on rollout
Avatar

lutzu70088640

lutzu70088640
- Adobe Experience Manager
Hi, could you provide details what you added in your action? I'm having basically the same problem but on 6.1Re: Field Level Inheritance - MSM

Views

3.1K

Likes

0

Replies

0
Re: Field Level Inheritance - MSM
Avatar

lutzu70088640

lutzu70088640
- Adobe Experience Manager
Hi,I having the same challenge: I need a field level based inheritance of a component since I need to avoid cancelling the whole component inheritance and therefore all fields.I found the property "fieldEditLockMode" in this article: aem - CQ5 - Cancel individual property inheritance of a Live Copy component - Stack Overflow. Adding this to the component dialog let the small locks appear in front of the field in the dialog. But when I cancel the inheritance of a field, changing the content, clos...

Views

1.1K

Likes

0

Replies

0
Re: Upgrade/Migrate AEM 6.1 to AEM 6.3
Avatar

lutzu70088640

lutzu70088640
- Adobe Experience Manager
Thanks, well an inplace upgrade is possible, of course. Our consideration was that since we did always inplace upgrade starting with CQ 5.4, it might be a good idea to start from scratch and maybe leave old stuff from older versions that is not in use anymore behind us...

Views

1.0K

Likes

0

Replies

0
Re: Upgrade/Migrate AEM 6.1 to AEM 6.3
Avatar

lutzu70088640

lutzu70088640
- Adobe Experience Manager
Hi,we are also planning to migrate from AEM 6.1 SP1 to AEM 6.3. We are thinking of setting up fresh AEM 6.3 and migrate content then. But we have the need to keep and migrate the versions. Is this possible? Does anyone have experience with this scenario?Thx

Views

1.0K

Likes

0

Replies

0
Creating not inherited page property field
Avatar

lutzu70088640

lutzu70088640
- Adobe Experience Manager
Hi,we are using AEM 6.1, SP2 in a blueprint/livecopy environment. I would like to add a field in the page properties which should not be inherited to livecopy page - so there should be no lock symbol in front of the field. Is this somehow achievable - meaning that fields are not connected/synced to blueprint page?I'm aware that I can exclude the page property field from being updated via "CQ MSM Content Update Action" Config but then the field is filled in when I create the livecopy initially al...

Views

820

Likes

0

Replies

0