I am trying to add an action to one of the toolbars in the Hybris backoffice. However, in order to achieve that I would need to modify the component and add an action to it in the backoffice.xml. The problem is that for all the other modifications I see components like editorarea, listviewaction, editorareaaction etc and I have no clue what the name of my exact component is (it`s something about the collaboration center). I would like to know if there is a way to check from the backoffice, or somehow, which component is which, so next time I know how to modify it. Can someone help please?
Related
I was wondering if a feature for WxPython existed or if I need to make it.
Here is a sample from a C# program I am trying to achieve with a property grid:
Sample Grid Image
I want this look with a checkbox in front of a PropertyCategory such as Group 0 or Message 0 in PropertyCategoryExample and can include the category. If you include the parent category I want the children categories to also be included.
Basically it acts as the expansion next to it but is a checkbox. I want to be able to still expand and shrink but just an extra checkbox when I go to save to see if the user wanted it included.
I have looked around in the docs and web but can’t find anything related to this. Do I need to make a custom property to do this?
I have asked on the discussion board but I haven't heard anything back
Thanks for your help in advance!!!
I'm a bit new in Teamstudio xcontrol ( a bootcard based UI for xpage ) and i'm wondering if there is a property or a function that allows deleting of documents. I checked the FormViewer Custom control, FormEditor and any custom control that is related to domino documents or view but I haven't found any. I also checked the website of the xcontrol but I haven't found any. Do I miss something or do we really need to create the functionality on our own. Thanks in advance for the help!
They're isn't, however in the upcoming version 1.2 we do support the addition of custom buttons so you could add your own delete button.
I wanted to write a hook which will place a new field in new document type along with present ones(textbox, selectbox etc.)."I need That new field which works like dropdown box under Metadatasets as screen shot shows .and also i need to get values from database whenever i select that field in the available fields if we choose "select" it show option1 ,option2 ,option3 .."
Can anyone know which js and jsp files should I edit.? Please help
https://www.liferay.com/documentation/liferay-portal/6.1/user-guide/-/ai/lp-6-1-ugen04-document-types-and-metadata-sets-0
i was unable to upload image,Can u plz see the above link.in this page figure 4.6 is the image.
Since Document Types are part of Document library so you can check-out: \portal-web\docroot\html\portlet\document_library\edit_file_entry_type.jsp. and other related pages which might be accessed from this page.
Hope this is what you want, again I would suggest to please pay heed to my comments to your question.
So I'm trying to find the best approach to solve the following problem.
I have the following pages:
1.insert.xhtml(Where I have a form to register a client)
2.find.xhtml(Where I have a table for the registered clients, where I can edit and exclude them)
In the find.xhtml page I have a context menu with the edit option, if I click on it, it'll open a <p:dialog> with the same insert.xhtml registration form, except for the submit button that have a different name and action-listener.
I also have other registrations that needs a client reference on it, ex.: registering a car sell to a registered client. The way I select an already registered client to add it to the sell form is by calling a popup with the same code in the find.xhtml table and select a client there, except this table have a button on its footer called select.
So what I'm asking is a way to reuse those forms/table codes being able to add a few components on them as needed. Is there a way to do it?
EDIT: Just like a template
EDIT2: Nevermind, I just solved it by using <ui:decorate>.
I am not sure if <ui:decorate> is the best solution. I have seen many examples of templating where it is used a composition. I like a lot this tutorial from IBM:
http://www.ibm.com/developerworks/java/library/j-jsf2fu2/index.html
they explain in detail how to create a template.
I'm employing a custom webpart that is made by an unaffiliated third party. I've created a feature which adds this webpart to a page. It's working mostly fine, except that I can't figure out the name of a specific property that needs to be defined. I tried obvious ones that match the display name on the tool pane view, adding the company's name in front of said display name, and many similar permutations. All of which to no avail. I would much prefer to include the property to the feature, as this will be necessary to deploy across multiple sites in the future. Manually configuring it every time will be a pain for my client.
The short, obvious answer is "Ask the third party". This can potentially work, particularly for this specific one (it is a CodePlex webpart and the author has posted a comment as recent as last week). But my experience with previous third party solutions has been less than optimal, usually even getting no response until they ask me three weeks later if I still like their product. So, since this is not always a reliable method to obtain this information, I was thinking the best option is to find out a way to figure out the name of properties in a webpart that I can use not just with this particular one, but in all future situations.
I did check out this earlier question which addresses a similar topic. However, I don't have access to the class for the webpart so I can't just find a convenient property in the code to modify. Or, at least, if I do have access to it in some fashion, I'm certainly unaware of it.
Thank you in advance!
From what I understand, you are trying to set a certain webpart property for which you do not know the corresponding XML attribute name.
Did you try to export the web part? One possible check might be to try to export the webpart to see what properties come up in the webpart XML. If it is a common property, chances are the webpart XML will have that property already defined with no value e.g.
<data>
<properties>
<property name="Your property Name" type="yourType"></property>
<properties>
</data>
To export the webpart, go to Edit Page mode, click the down arrow on the webpart and choose Export.
Also, if you have the webpart code in a dll, can you use reflector to open it and see what properties are being set in code?
Hope this helps.