IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#TechXchangePresenter
 View Only
Expand all | Collapse all

Portlet properties... wm_universalpicker vs textbox

  • 1.  Portlet properties... wm_universalpicker vs textbox

    Posted Mon August 01, 2011 11:41 AM

    Hi,

    I’m just comparing the example wm_portlet_links/multiple_portlets with my own. In multiple_portlets, there is a property portlet_id of type String. Nevertheless, when published to MWS, the property isn’t available as textbox, but with an button “browse” invoking the wm_universalpicker (screenshot).

    First I guessed portlet_id could be a special keyword invoking this behaviour. But it doesn’t seem to be… I’m still getting a textbox in my own portlet.

    Am I missing a setting?

    A second topic: I’ve observed the following behaviour: A property that contains a dash, like “C-ID”, no picker is popping up when selecting “Other” from the dropdown-box for wiring. I haven’t found that constraint in the documentation…

    Regards,
    Gregor


    #MWS-CAF-Task-Engine
    #webMethods
    #webMethods-BPMS


  • 2.  RE: Portlet properties... wm_universalpicker vs textbox

    Posted Mon August 01, 2011 11:59 AM

    Uh, just found the way to do: element property-editor in wm-portlets.xml

    
    <property>
    <param>
    <name>validationRegexp</name>
    <value></value>
    </param>
    <param>
    <name>displayAliasButton</name>
    <value>1</value>
    </param>
    <param>
    <name>xtypes</name>
    <value></value>
    </param>
    <param>
    <name>multiple</name>
    <value>2</value>
    </param>
    <param>
    <name>availableStart</name>
    <value></value>
    </param>
    <param>
    <name>disabled</name>
    <value>2</value>
    </param>
    <param>
    <name>onchange</name>
    <value></value>
    </param>
    <param>
    <name>selectable</name>
    <value></value>
    </param>
    <param>
    <name>validationRegexpMsg</name>
    <value></value>
    </param>
    <param>
    <name>basetypes</name>
    <value></value>
    </param>
    <param>
    <name>roots</name>
    <value>folder.public</value>
    </param>
    <param>
    <name>unselectable</name>
    <value></value>
    </param>
    <param>
    <name>style</name>
    <value>5</value>
    </param>
    </property>

    But a way to set this via the GUI would be nice.

    PS: [ code][ /code] as well as

     
    are hiding some parts of the elements… it’s called property-editor not property… and some attributes are not shown, too.


    #webMethods
    #MWS-CAF-Task-Engine
    #webMethods-BPMS


  • 3.  RE: Portlet properties... wm_universalpicker vs textbox

    Posted Mon August 01, 2011 12:00 PM

    The important part is property-editor type=“portal-resource-popup”


    #webMethods
    #MWS-CAF-Task-Engine
    #webMethods-BPMS


  • 4.  RE: Portlet properties... wm_universalpicker vs textbox

    Posted Mon August 01, 2011 07:57 PM

    These are legacy portlets and there is a legacy portlet editor (see the 6.5.2 Portal Design Guide at: http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/wmsuites/wMdoc/_webM_suite_65/Access%20and%20Portal/Accessand%20Portal%206.5.2/webMethods%20Portal%20Design%20Guide%206.5.2.pdf)

    Check the forums for more information about how to enable the Legacy Portlet Editor in Designer as well.

    Hope this helps.
    –mark


    #webMethods-BPMS
    #webMethods
    #MWS-CAF-Task-Engine