HelloThanks for the reply. one question I have used below simple line as
mentioned in the coral ui docs. Then this doesn't really working.in your
code you hardcoded the coral classes. but as per the docs if we should
apply below variant then it automatically work (eg: applying background
color blue) any thoughts here. Engagemy html
applies different classes like below. Engage
I am trying to create a button in AEM page (custom page not aem admin
console's), As a BE I wanted to leverage AEM coral-button component to
get same look and feel. I have tried using clientlibs embed option like
below. though I see coral js and css loading in page source. My button
still looking without any css applied example blue color. any pointer
would be helpfull. embed="[coralui3,granite.ui.coral.foundation]"
By mistake I marked it as correct answer, not sure how to revert it
though, but my requirement is once user uploads csv with some
assetPath's I need update those assetPath's to different assetPath based
on custom logic. How Can I introduce this additional step into this
complete import metadata workflow.
I am trying understand asset versioning and I have understand from the
AEM docs that whenever we upload metadata, new version will be creates
But when I verify this in latest cloud sdk I don't see this working, and
version is only created by selecting asset click create version button.
Hello, As per my requirement I need to some how process the uploaded
csv(whenever client uploads csv with assetPath and metadata) file and
modify the assetPath (before doing actual metadata update)given in csv
and then process the importing metadata. How the existing OOTB import
metadata functionality can be customised here ??is there some workflow
that I can extend any pointers would be helpful. Please check
Hey @jimp38732070 I have same usecase, But when I try to use options
predicate I am able to see list of checkboxes in the form instead of
dropdown with options. How did u manage to make it dropdown Could you
please share your thoughts here.