I have object named Payment and in share-config-custom.xml I defined form, everything is set nicely, but I don't know how can I change generic title "Payment" to "Payment Details". Does anyone know how to change that?
Best,
D
You can define a resource bundle in Alfresco were you can fill in the type properties or you could just change the custom model you've defined and change it there.
Related
is there a way to have prefilled attributes notes in enterprise architect?
It should be something like this scenario:
1) I create new attribute
2) Enterprise architect prefill note of attribute with predefined text
Something like template for attributes.
Thank you for any advice
I know this won't help directly this question.
Anyways you can achieve it through an external addin.
All you need to do is handle the EA_OnPreNewAttribute and EA_OnPostNewAttribute broadcast events .
This isn't quite what you're after but it is possible to create an Attribute stereotype in a Profile and add to this a Tag with an initial value set to what ever you want. When you create an attribute with this stereotype, this means your predefined text would appear in a tag-value for the attribute rather than the note. Not ideal, but might work for you.
You could also have a go at writing some JavaScript to do this as well (under Scripting in EA). You'd have to use the JS to navigate the repository structure, find the attributes in question, and update their note. I don't believe you can attach a script to a UI event, so I think you'd be stuck running this post-hoc rather than having the note auto-populate on attribute creation.
Is there a way to add a custom attribute at customer in Magento2 CE, which are shown in the Admin with autocompletion like the category for product?
I'm not really sure what you mean. If you are talking about a custom attribute with a predefined set of possible values, you could just use a "dropdown" or "multiselect" type attribute.
Otherwise, if you want to get "real" autosuggestions, for example from some kind of rest API, you would need to write that yourself.
I'm new to CQ5 and working on a project that deals with refactoring code that uses design dialogs.
Currently, I have a property declared as part of design dialog of my component. It creates a folder in /etc/designs/ for each template my component is used on. Is there a way we can make sure that those property values are stored at one particular configuration in /etc/design(as opposed to multiple)? I need to make sure only one set of configurations is used for all pages that use my component.
Thanks in advance!
Pallavi
The designs are linked to the template and not the whole site.
Hence whenever you configure the component in design mode, the values are stored within the corresponding template under the jcr:content of the configured design page or under /etc/designs/default/jcr:content in case no design is configured.
As far as I know, there is no way to tell AEM to store all the design configurations under one single path, unless you are using absolute paths in your dialog / page configurations.
If you are using multiple templates in your site, there must be one master template (which render global components eg. header/logo/navigation & footer), and all other templates should extend master template to get these global components and change pagelayout for content section.
Saying so, if templates are structured & inherited properly, you should be able to set design dialog property on home page (created using master template) and all internal pages will be able to access those design property OOB. Though child pages (created using other template) can override those design property (if needed for that template) to break inheritance.
I have a requirement to store a list of designers with logos and some bio information in my Umbraco CMS. I created a document type called 'Designer' with all those properties. I'd like to now create a dropdown list with those designer names so I can associate it with other document types. How do I create this dropdown? I'm using the v7 of umbraco.
Checkout nuPickers for Umbraco v7. Should have everything you need.
http://our.umbraco.org/projects/backoffice-extensions/nupickers
http://github.com/uComponents/nuPickers/wiki
http://www.nuget.org/packages/nuPickers
Look here for help with creating custom labels using macros
http://github.com/uComponents/nuPickers/wiki/Custom-Labels
As I understand, your intention is to let editors pick designers from the designers dropdown when editing content items in the backoffice.
If so, you may want to either use an existing data type called 'Dropdown' or create a custom data type.
If you only want the names in the dropdown, the default 'Dropdown' data type may suffice. Take a look at the article explaining how to customize the 'Dropdown' data type
Otherwise (say, if you want to show the avatar of the designer in your designer picker), you may want to implement your custom property editor (designers picker) and a custom data type related to it. Then you will be able to associate your data type with any document type you want.
A couple of useful links in this case:
how to create a custom property editor in umbraco 7
the demo which includes building a custom picker property editor to assign custom data to a document
Umbraco v7 XPathDropdownList implementation
I'm trying to add an attribute to the form tag of a cq5 form. I noticed that the output is generated using
FormsHelper.startForm(slingRequest, new JspSlingHttpServletResponseWrapper(pageContext));
I was curious how I can either:
alter the request so that the formHelper prints the form w/ the attributes I need
Hook into the actual print out to include the attributes I need.
Any help or direction would be good.
note:
I've already checkout out the javadoc for formshelper, done some searching via goolgle, and dev.day.com including the dev.day.com doc on developing forms.
thank you
API doesn't allow you to add any attributes to this tag. You can only specify desired CSS classes adding css property to the form component. Of course, you can also create component sling filter and response wrapper to rewrite created form, but it seems to be an overkill. I think better solution is using JS to add attributes client-side.