Content tab

These options let you set content-specific options, such as the character set in which an application’s text displays. The options on this tab are:

Name – a unique name for the application that contains this element.

Content Type – the type of content the application displays. You can select any of these options from the drop-down list:

Application/msword
Application/pdf
Application/x-msexcel
Application/x-mspowerpoint
image/gif
image/jpeg
text/html
text/plain
text/rtf
text/xml
Add New

XSL template – displays only when you select “text/xml” as the Content Type. Select an existing XSL template, or create a new one to apply to the application’s content.
Output Type – displays only when you select “text/xml” as the Content Type. Select the type of output in which the application’s content displays.

Charset – the character set in which the application’s content displays.

Content Cache Interval – the interval at which the content of an application is refreshed for the defined source. If this value is not Real Time, the content is held by the cache for the duration of the specified interval. All requests made during this interval receive the cached content.

The default is Real Time, which means that application content is retrieved from its source on every playback request.
Specify custom values by selecting Add New from the drop-down list. Select the minute/second drop-down list and enter a value in the text box.

Using content caching can save time when the application loads, especially if the application contains a lot of data. When content cache expires, the next time the application is loaded, the content is pulled from the source again, and the new content is stored in the cache. In the case of data-heavy applications, this can take some time. One way you can avoid slow loading of applications is to create an agent to run the application periodically so that the agent refreshes the cache when it is run after the cache expires. See “Using agents”.

Parameter – create an invisible parameter to which you can assign click-across events.

Invisible parameters is a Portal Interface feature. The idea for this feature comes from client-side click-across when the event is across pages. In an across-page client-side event, focus is shifted to the page where the listener portlet resides. However, if the portlet you want to shift focus to has no parameters, it cannot be a client-side listener and therefore you cannot shift focus to the portlet’s page.

To fix this problem, check the Invisible Parameter option for the application that should receive the focus to create a fake parameter on the application. Using this fake parameter, you can define listeners on the application, enabling it to receive focus in across-page client-side events.

On the Define Listeners window the fake parameter name appears as “Portlet Param.”

Secure – whether this is a secure application.

In Context – indicates that the click-thru session should remain in context (that is, continue to use the internal HTTP client to retrieve destination pages pointed to by links on the page), rather than opening a separate browser connection to each link’s target.

The In Context option helps address capture problems when a session state is associated with a played-back page, and the user clicks an application link and the linked content displays in a new browser window, which results in the session state being lost.

No URL Stretch – disables URL stretching (rewriting) on played-back application. If you are having problems with broken images in a played-back application, this sometimes solves the problem.

On BlackBerry devices, when using the Sync with Images option on the Sync All screen, the images do not display correctly unless you select this option.