Alfresco Share Form based association - node selection - alfresco

Is there anyway to restrict which nodes are selectable in Share's object finder popup when selecting a node for an association?
The problem I seem to be having is that I also have some custom types that are specialised versions of cm:content.
<type name="mymodel:mytype">
<parent>cm:content</parent>
These seem to have the + button next to them if navigated to within the folder/file navigator window of the object finder/file picker. Are sub-types of cm:content always considered to be selectable types for the object finder or is there a way to restrict the selectable types to only allow cm:content and not derived types?

Related

How can i use a common header in Cognos among many report pages?

I have a Cognos report and i have created 3 pages and 1 common prompt page. According to a radio selection in the prompt page i show the appropriate among these 3 pages.
In each page i have a block that is the header and there i just show title, current date and the selected values of the prompt controls (parameter values).
This header is the same among all pages and i want to find a way to create only 1 header section and then assign it on the top of each page. So if later i want to change anything in the header i will do it in one place.
Any ideas?
Re-using parts of a report (either from the report or other report in Cognos Connection) can be achieved with the help of layout component refenrences which are inserted into your report page and which refer to other existing components.
To use them proceed as follows:
Indentify the layout component(s) to be re-used (e.g. a table or a text or more or less anything less).
In the property list of that component go to the name and give it a unique name.
In the report page that is supposed to re-use the component drag an instance of the layout component reference to the appropriate location in the page.
Specify the target of the reference by choosing the report and within the report the named component (same name as given above).
Example
A block component (which could be incorporated into a header) is to be re-used. Give the block a name, e.g. my_block:
From the toolbox drag the layout component reference
to the report page. A dialog box opens which permits choosing the target component:

How do I promote text fields to custom form properties in Adobe Livecycle?

I am new to Adobe Livecycle and have created an XML dynamic form using Livecycle Designer ES4. I am looking for a way to promote a text field from the form to a custom property in the Forms Properties. An example would be the user fills in the field "TextField20" and after making that entry the custom property "Project Objective" in the forms properties is updated to reflect that information. Is it possible to promote metadata like this in Livecycle or is there another solution that I may not be thinking of? I tried researching online, but couldn't find anything related, which may be due to searching the wrong Adobe terminology/taxonomy.
I assume that you're talking about Variable tab in the form properties dialog.
In which case every property added creates a node in the form hierarchy with the name of the variables.
You only have to set this variable on the exit event of TextField20.
nameOfTheProperty.value = this.rawValue;
And that's it !

Creating a component that copies field values from another component

I am trying to create a Component1 in Tridion 2011 SP1. I also have Component2 which has already been created.
While creating a Component1 in Tridion, I have two fields for that Component, one is called 'SelectedType' which is a drop-down having values A,B,C which are options defined in the Schema. The other field called 'Name' which is also a drop-down, but its values should be retrieved from the second Component according to the value selected from 'SelectedType' field.
Component2 has the following fields named 'A', 'B','C'. Each field in Component2 is multivalued and is of type text.
So for example if I Select value 'A' from 'SelectedType' drop-down filed then my 'Name' drop-down field should get populated with the values fetched from field 'A' of Component2.
This functionality should not be implemented by adding any Extensions to the Tridion UI, or using any .NET code.
This should be purely implemented using the available functionality in Tridion.
Is there any scope of implementing event Handlers/Listeners in Tridion which populates values to the next drop-down field when an event has occured for the value change in first drop-down field?
This is not built-in functionality of Tridion, so you'll have to write some sort of extension. If you stick to the statement "without a GUI extension or .NET code" then the answer is a simple "no".
If you are willing to consider writing an extension AND you are on Tridion 2011 (or later), then you might be able to get this done using a Data Extender since the dependency you want is between two Components (and not fields within the same Component).
This will not be possible without creating a GUI extension I'm afraid. This functionality is not currently out of the box with SDL Tridion 2011. This is why the GUI is extendable.

Drupal views exposed input as form select (/jumpmenu)

I have content type called news. I have a view thats lists all the news. But now I would like to filter those by year and type. User could select from select menu / dropdown the publish year (2010, 2011, 2012 so on) and also the type of the news (taxonymy terms).
I was playing around with views exposed but I only got a text input field. Can I somehow get a select menu instead of normal input field? And also how can I list all the publish years when news are published to that select menu?
Should this be done even with views?
====
PAGE
Filter dropdowns: -type- -year-
Press releaseses listed down here according the filters.
Select boxes will only be used in Views exposed filters when there is a finite number of possible values. In other words, if your field you want to filter on has something set in the 'allowed values' section you should have the option of a select box if you choose "FIELD NAME - Allowed Values" as the field to filter on in Views.
If your field has an unlimited amount of possible values, you could always write a custom module to create a block with a form that presents your select boxes and directs the user to the view (using the filter parameters of the view).

can i make view of views?

how can make view of more than one views 6.Please give me solution.Is any module in drupal 6.If it is not then how to customiz the view so that we make view of views.
I enable the view module and homebox module.pls gv me solution.
If you want to make a list of views, the simplest option is to create each View as a block and place all the blocks on the same page.
Other alternatives are:
Views attachments (see http://www.cmsquickstart.com/blog/drupal6-attachment-display-views)
Viewfield module
Viewfield provides a field that holds a reference to a View and
renders it whenever the entity containing the field is displayed.
adding a View area as part of the header/footer of a view (only available in D7, I think) -- see http://drupal.org/files/vfv-cant-select-display.jpg

Resources