Hi,i followed this tutorial : Develop AEM Projects and got the working
package as mentioned. i installed it in AEM 6.5 and tested it with some
values in it.when i try to open the task from inbox and check the tabs
"project info" "workflow info" and "comments". they aren't showing
up.when i install the same package in AEM 6.4, it works fine and all
tabs are showing up.i have followed this documentation to create our own
version for our project approval and it have the same issue,is there any
okay i tried something else again.i went into the package that i got
from my local instance with new namespaces added to
"\jcr_root\_jcr_system\content.xml"when i tried installing this package
to another instance, it didn't add any new namespaces.but i found a
nodetypes.cnd file in this package "\META-INF\vault\nodetypes.cnd".i
added the new namespaces in this file like this: installed the package
with new changes. and YASSSSS! my new namespaces are available on this
instance.please let me know ...
@husams51669576 is there a reference article or something you could
provide for this please.i found this: Using the CRX2Oak Migration
Toolbut it doesn't specify anything about namespace migration.Please let
me know if you find any.Thank You!
Vish.dhaliwalAdding or Deleting namespaces from AEM using CRX/DE is not
possible. it gets deleted. but once we save and refresh, they are back
to their normal state.i tried packaging them from my local and installed
the package on our dev server. it doesn't install the new ones that i
I've created a new namespace on our staging environment and used it for
custom metadata properties.I've seen many articles to import the new
namespaces using AEM namespace editor.Is there a way to package the one
we created on our Staging and install it on PROD. (assuming that AMS
wouldn't provide access to namespace editor on PROD Environment).Thank
Thanks for quick response. JaideepBrar Vish.dhaliwalyes! this worked.
and all my launchers are working fine.But,will this workflow stay same
and not get lost when there's a hot fix or an upgrade?how do we persist
the customization of this workflow from code repository.should i just
create the same structure (/conf/global/settings/workflow/models) in my
code repository and deploy it.if not through code repository, should i
package it and install on my stage and prod servers?
AEM 6.5i've copied OOTB "DAM Update Asset workflow Model" in aem and
changed launchers for create, update, modifying assets to this new
model. but workflow is not being triggered when i upload an asset. are
there specific instructions to overlay a workflow model and customize
it.how do we persist the customization from code repository to avoid any
overrides ?Thanks in advance!!!
I'm also trying to do something similar.I have to save product model
Number to Asset metadata.Are there any metadata fields already available
to do this. (OR)Should i totally create a new metadata property and use
it to map a new field in metadata schema. Did you get to implement this.
if so, can you please post the solution here.Thank You!
SonDang thanks for responding.Yes, there's whole "we-retail" folder
under conf shown in the picture.and yes there's this console error:i
couldn't figure anything out of this error though.we're planning to
start using editable templates in our project. So just trying to see
we-retail templates to play around.here's the screenshot of
configuration browserThanks in advance.Also here's the Error
Log.22.05.2019 13:45:04.028 *INFO* [0:0:0:0:0:0:0:1  GET
Templates console is totally empty. i'm using AME 6.4.i used
configuration manager to create folder under conf named
"myproject".everything works fine on new AEM instance.couldn't figure
out the issue with our project. is there any exact nodes that i have to
check for. please HELP.Note: "we-retail" folder is also not showing up
in this console. and there'e no create button too. i also tried going
from "createtemplate" wizard. No luck there too.Please help and thank
you in advance.
polizzigaetano-codeland i found the same error even after doing
everything mentioned. can you please let me know authorization value you
added for the integration to work.should i white-list something.Thank
as per this page Overlays , it recommends to do this "This means that
creating an overlay with a skeleton structure is only appropriate for
the standard, touch-enabled UI."should the structure match here with
not clear about the solution in the article ECU Thank You!
Hi smacdonald2008,when i ran the pattern detector on my 6.3 project, it
showed too many acs-commons issues. example: "2018-07-31T17:28:20.755Z
[SUSPICION] The pattern=ECU/extraneous.content.usage was found by
message="Cross-boundary override of internal marked path
/libs/granite/ui/components/foundation/form/field referenced at
/apps/acs-commons/components/authoring/search-pathbrowser". More i...