Setting the list-rendering context | HCL Digital Experience
Learn about how you set the list-rendering context in Digital Data Connector (DDC) for HCL Portal.
About this task
To establish the list-rendering context, you add the following
tag to your presentation template:
[Plugin:ListRenderingContext action="set"
extension-id="bean list provider id"
profile="profile name"]
Replace
the bean list provider id
variable
by the ID that identifies the DDC plug-in instance through which you
want to render this list. If the addressed DDC plug-in is the generic
XML DDC plug-in or a DDC plug-in that delegates its requests to that
provider, you must identify the list-rendering profile. The XML DDC
plug-in uses the identified profile to transform the XML data into
bean list objects. Custom DDC plug-ins might or might not require
this profile parameter.To address one of the two DDC plug-ins
that are provided with HCL Digital Experience Version 8.5, use one of the following
values for the
extension-id
parameter:- ibm.portal.ddc.xml
- Use this value for addressing the generic XML DDC plug-in.
- ibm.portal.ddc.sr
- Use this value for addressing the DDC plug-in that is used by the social lists feature.
Depending on your choice, the addressed DDC
plug-in can support or even require that you pass extra information
through the attribute
parameters. For details about
which information is supported or required with the DDC plug-ins,
read the documentation about the DDC plug-in that you use.
Example
[Plugin:ListRenderingContext action=”set” extension-id=”ibm.portal.ddc.xml”
profile=”ibm.portal.atom”
attribute=”source=https://www.ibm.com/connections/communities/service/atom/catalog/public”
compute=“always“]
Note: If
you want to test this example, you might have to adjust your proxy
configuration to allow your portal to access the source URL. For more
information, read the information about proxy configuration in the HCL Digital Experience documentation.
Note: If you want to test this example, you
probably must adjust your outbound HTTP connection to allow your portal
to access the source URL. For more information, read Outbound
HTTP connection.