Posts Tagged ‘the’


NOTE: ALL THE CUSTOMIZATIONS I’M MENTIONING HERE ARE TESTED AND WORKING.
CONFIGURE THE SEARCH RESULTS SCREEN OF DASH INTERFACE IN FATWIRE:

Case 2: Modify the columns of the search results screen in the Dash Interface.

Explanation: By default, in the search results screen of the Dash UI, the following columns/fields are available: Name, Type, Modified, Locale, Start Date, End Date. In this article, we will see where and how to modify these fields.

Solution: For this customization to take place, we need to do modifications in the UIADMIN.PROPERTIES file.

The file is available in the following location:

C:\FatWire\JSK\7.5Patch5\App_Server\apache-tomcat-6.0.18\webapps\cs\WEB-INF\classes

Open the UIADMIN.PROPERTIES file.

We have a property in that file called “searchtableattrcols”, which specifies the columns that should be displayed in the UI.

The property is set by default as follows:

searchtableattrcols=AssetType,name,updateddate,locale,startdate,enddate

The search results screen of the Dash UI displays the following fields:

We need to change the above value to what ever we want.

Lets remove the Start Date and End Date values from the property, and see what happens. The property looks as follows:

searchtableattrcols=AssetType,name,updateddate,locale

Save the UIADMIN.PROPERTIES file.

Check the Dash UI’s Search results screen for the changes to reflect.

In the search results, we can find that the Start Date, End Date are omitted.

That’s it…! The customization has been done.

Stay tuned for more customizations in my upcoming articles.


Its always interesting to customize the existing out-of-box features given by the software vendor. Apart from being interesting, we might ght some times to customize the interface according to the clients requirements. We will discuss some of the customizations to the user interface, especially the DASH interface of Fatwire, in few of my upcoming articles.

NOTE: ALL THE CUSTOMIZATIONS I’M MENTIONING HERE ARE TESTED AND WORKING.
CONFIGURE THE SEARCH RESULTS SCREEN OF DASH INTERFACE IN FATWIRE:

Case 1: Change the SEARCH RESULTS COUNT of the search feature in the Dash Interface.

Explanation:  This customization is related to the search feature of the UI. We need to change the number of assets returned through search. For example, I would like to limit the search results to a 100 assets, instead of displaying the entire results. Hence, we need to find the properties file, in which we need to do modifications.

Solution: For this customization to take place, we need to do modifications in the UIADMIN.PROPERTIES file.

The file is available in the following location:

C:\FatWire\JSK\7.5Patch5\App_Server\apache-tomcat-6.0.18\webapps\cs\WEB-INF\classes

Open the UIADMIN.PROPERTIES file.

We have a property in that file called “searchresultscount”, which specifies the maximum assets that should be returned in the results, through the search performed by the user.

The default value of searchresultscount is 500 ,i.e., the following property is set by default:

searchresultscount=500

When searched for an assets of a particular asset type, the search results screen of the Dash UI displayed the following:

We need to change the above value to what ever we want. For example, if I want the results to be limited by 100, then I would set like this:

searchresultscount=100

Save the UIADMIN.PROPERTIES file.

Check the Dash UI’s Search results screen for the changes to reflect.

When searched for the same assets of the asset type searched above in the Dash Interface, and we can observe that the search results are limited. Verify the screen below:

That’s it…!

Stay tuned for more customizations in my upcoming articles.


When to Use the Flex Asset Model in Fatwire?

Flex assets means FLEXIBLE ASSETS. Meaning, that we can add fields at any moment to the asset. You can update your site at any time, adding new fields, without disturbing the existing content.

FLEX ASSET MODEL has been the favorite model for the developers who concentrate on developing WEB EXPERIENCE MANAGEMENT applications. The Flex model helps in achieving the website’s goal of targeting the audience/visitors, and hence improving the overall business by the websites. The Flex Asset Model is the choice of developers, when the data has the following characteristics:

  • MANY ATTRIBUTES:  The assets have very large number of attributes, like some hundreds of attributes.
  • NEEDS HIERARCHY:  The assets need to inherit attributes from their parents.
  • UNPREDICTED ATTRIBUTES: This means that we know that we cannot predict what attributes might be necessary in the future.
  • NAVIGATION: Visitors browse your site by navigating through “drill-down” searches that are based on the attribute values of your data.
  • ENGAGE: You want to use Engage.

If implemented correctly, the Flex asset model yields major benefits for the business through websites.

But, to build a Flex asset model, a lot of complex work needs to be done. The following needs to be kept in mind, while choosing this Flex asset model.

  • COMPLEX DATABASE: The underlying database structure of flex assets is pretty complex.
  • SLOW RATE: Asset creation is slower that Basic assets.
  • SEARCH: Searching attributes requires complex code.

render:lookup

The render:lookup tag is one of the important tag, which is used in looking up a  map value for a given Template or CSElement. We will now see the syntax of this tag, and its usage.

USAGE:

This render:calltemplate tag is used to Look up a map value for a given Template or CSElement.

SYNTAX:

The following is the JSP syntax of the render:calltemplate tag. This is in reference with the “Tag Reference” guide.

<render:lookup
        key="name of lookup key"
        varname="output variable name"
        site="site name"
       [tid="id of template or cselement"]
       [ttype="CSElement|Template"]
       [match="x|x:|:x"]
/>

We will now discuss the some important arguments which are specified above.

1. Key:  The name of the key corresponding to the value. The key is the only thing that can be hard-coded in a template; hard-coding asset names, types, or values is discouraged.

2. Varname: The output variable name to contain the value corresponding to the key.

3. Site: The name of the site corresponding to this mapping. (mapped values differ across sites).

4. Tid: The id of the template that owns the mapping (defaults to the id of the current template). If this tag is present in a CSElement, then the default is the CSElement id, and ttype must be set to CSElement.

Example usage of render:callelement:
<%-- Look up the name of the layout template --%>
<render:lookup
        site='<%=ics.GetVar("site")%>'
        varname="LayoutVar"
        key="Layout" 

<%-- Look up the name of the wrapper page's site entry.
     Note we want the asset name only, so we must specify
     the match filter. --%>
<render:lookup
        site='<%=ics.GetVar("site")%>'
        varname="WrapperVar"
        key="Wrapper"
        match=":x"/>

render:calltemplate

The render:calltemplate is one of the well know tag, which is frequently used by the fatwire coders. We will now see the syntax of this tag, and its usage.

USAGE:

This render:calltemplate tag is used when we would like to invoke a Template, or a CSElement, as either a PAGELET (A small part of the page), or an Element, for rendering an asset.

Though we have another tag  “render:callelement” to invoke CSElements, this render:callelement tag is used to invoke both Templates and CSElements as well.

SYNTAX:

The following is the JSP syntax of the render:calltemplate tag. This is in reference with the “Tag Reference” guide.

<render:calltemplate
        site="site name"
        slotname="name of slot"
        tid="caller Template or CSElement id"
       [ttype="caller Template or CSElement"]
       [c="asset type"]
       [cid="asset id"]
       [tname="target Template or CSElement name"]
       [context="context override"]
       [style="pagelet or element or embedded"]
       [variant="template variant name"]
       [packedargs="packed arguments"]>

   [<render:argument name="variable1" value="value1"/>]

</render:calltemplate>

We will now discuss the some important arguments which are specified above.

1. site:  This is a required field. This specifies the name of the site containing the Template to be invoked.

2. slotname: This is also a required field. This attribute defines an user friendly name for the “slot” that is being filled with the called template.

3. tid: This is also a required field. This specifies the id of the template in which this tag is located. If this tag is located in a CSElement, then the value of this attribute should be the id of the CSElement, and ttype should be set to CSElement.

4. context: This is an optional field. If c, cid, and tname are not specified, then this attribute value will be examined to determine which template to call and which asset to render using the specified template.

5. tname: This is an optional field. This field specifies the name of the Template to be called. Typeless templates must be prefixed with a ‘/’. This is required if c and cid are set. If these three attributes are not set, the called template will be determined by looking at context data.

6. style: This is an optional field. The possible values for this field are pagelet, element, embedded.

7. c: This is an optional field. This field specifies the asset type to be rendered by the called Template. The value of this attribute will be passed to the called code.

8. cid: This is an optional field. This field specifies the id of the asset to be rendered by the called Template. The value of this attribute will be passed to the called code. This is required if c is set.

Example usage of render:callelement:

<render:calltemplate tname='<%=ics.GetVar(“ViewTypeVar”)%>’
site='<%=ics.GetVar(“site”)%>’
tid='<%=ics.GetVar(“tid”)%>’
slotname=”PageView”
c='<%=ics.GetVar(“c”)%>’
cid='<%=ics.GetVar(“cid”)%>’
ttype=”Template”>
</render:calltemplate>

In our next post, we will learn how to deal with the “render:lookup” tag, which is frequently used in combination with “render:calltemplate” tag.


The sites which are created in Fatwire can be listed using the tag  publication:list. In this article, we are going to display the list of sites created in Fatwire content server.

Following is the code piece:

<%@ taglib prefix="publication" uri="futuretense_cs/publication.tld" %>

//This library helps in the usage of the publication tag

//To retrieve the list of the sites, we are going to use the following code snippet
<publication:list list="mysites"/>

//Now, to display the sites, the following code snippet is used. We are going to display the sites using the listloop and listget tags:
<ics:listloop listname="mysites">
	    ID OF SITE: <ics:listget listname="mysites" fieldname="id"/>,
	    SITENAME :<ics:listget listname="mysites" fieldname="name"/>
</ics:listloop>