|Oracle Fusion Middleware Data Visualization Tools Tag Reference for Oracle ADF Faces
dvt:timelineItem timelineItem timeline item
UIComponent class: oracle.adf.view.faces.bi.component.timeline.UITimelineItem
Component type: oracle.dss.adf.timeline.TimelineItem
The TimelinelItem component must be placed inside of a TimelineSeries component. It represents an event item inside of the Timeline.
The following tags are allowed as children of the TimelineItem:
This component must be a child of the <dvt:timelineSeries> component.
How the item is represented in the timeline overview can be customized by specifying a <dvt:marker> using the overviewItem facet. Only the following properties from the dvt:marker tag are supported:
shortDesc attribute:The summary property must be specified. The summary should describe the purpose of the component.
Apply Request Values
|Event delivered to describe an attribute change. Attribute change events are not delivered for any programmatic change to a property. They are only delivered when a renderer changes a property without the application's specific request. An example of an attribute change event might include the width of a column that supported client-side resizing.|
|overviewItem||the overview item facet is used to represent the timeline item in the timeline overview. Currently dvt:marker is the only valid child. As with JSP pages, when using Facelets, multiple components are not allowed in this facet.|
|attributeChangeListener||javax.el.MethodExpression||Only EL||a method reference to an attribute change listener. Attribute change events are not delivered for any programmatic change to a property. They are only delivered when a renderer changes a property without the application's specific request. An example of an attribute change events might include the width of a column that supported client-side resizing.|
|binding||String||Only EL||an EL reference that will store the component instance on a bean. This can be used to give programmatic access to a component from a backing bean, or to move creation of the component to a backing bean.|
|endTime||java.util.Date||Yes||the end time of the event represented by this timeline item.|
|group||String||Yes||the group in which the item belongs to.|
|id||String||No||the identifier for the component|
|inlineStyle||String||Yes||the CSS styles to use for this component. This is intended for basic style changes. The inlineStyle is a set of CSS styles that are applied to the root DOM element of the component. Be aware that because of browser CSS precedence rules, CSS rendered on a DOM element takes precedence over external stylesheets like the skin file. Therefore skins will not be able to override what you set on this attribute. If the inlineStyle's CSS properties do not affect the DOM element you want affected, then you will have to create a skin and use the skinning keys which are meant to target particular DOM elements, like ::label or ::icon-style.|
|partialTriggers||String||Yes||the IDs of the components that should trigger a partial update. This component will listen on the trigger components. If one of the trigger components receives an event that will cause it to update in some way, this component will request to be updated too. Identifiers are relative to the source component, and must account for NamingContainers. If your component is already inside of a naming container, you can use a single colon to start the search from the root, or multiple colons to move up through the NamingContainers - "::" will search from the parent naming container, ":::" will search from the grandparent naming container, etc.|
|rendered||boolean||Yes||Default Value: true
Specifies whether the component is rendered. The default value is true.
|styleClass||String||Yes||a CSS style class to use for this component. The style class can be defined in your page or in a skinning CSS file, for example, or you can use one of our public style classes, like 'AFInstructionText'.|
|value||java.util.Date||Yes||the time of the event represented by this timeline item.|
|visible||boolean||Yes||Default Value: true
the visibility of the component. If it is "false", the component will be hidden on the client. Unlike "rendered", this does not affect the lifecycle on the server - the component may have its bindings executed, etc. - and the visibility of the component can be toggled on and off on the client, or toggled with PPR. When "rendered" is false, the component will not in any way be rendered, and cannot be made visible on the client. The default value is true.