A timeline zone contains one or more "lines" where each line shows when significant events have occurred. For example, you can set up a timeline zone that has two lines: one that shows when payments have been received from a taxpayer, and another that shows when forms have been posted for the taxpayer.
For a complete description of the numerous features available on a timeline zone, refer to Timeline Zone.
The following points describe how to set up a timeline zone:
Determine which portal you wish the zone to appear on. For example, you may configure the zone to appear on 360 Degree View - Account, 360 Degree View - Tax Role or for implementations still using Control Central, the Control Central Account tab.
Set up an algorithm for each line in the zone. These algorithms will reference an algorithm type that is plugged into the Zone - Timeline Line plug-in spot. Note that the base product supplies pre-configured algorithms for many of the timeline zone algorithm types that may be used if the configuration is acceptable. Click here to see the algorithm types available for this plug-in spot along with any pre-configured algorithms supplied with the product. Please note the following about the parameter values defined on these algorithms:
Most timeline algorithms are designed to display information about the account in context. However, three are several that are designed to display information for an account or for a specific tax role in context (for use on the 360 Degree View - Tax Role tab). If the algorithm includes a Restrict by Entity flag, indicate the appropriate value to control the data that should be shown.
Each timeline algorithm allows you to define the appropriate foreign key reference that controls the "info string" that appears as well as the navigation option. The object's info string appears in the zone's info area. When a user clicks on an "info string", they are transferred to an appropriate page (typically the one used to maintain the object).
You can set up a timeline algorithm to show BPA scripts when a user clicks on an event on a timeline. For example, if you click on a payment event, BPA script descriptions can appear in the info area. When a user clicks on one of these descriptions, the script will execute and guide them through a respective business process (e.g., transfer a payment). You define the scripts in each timeline algorithm's parameters.
When a script is initiated from a timeline, the system puts the prime key of the event into a field in the page data model. The name of the field is the column name(s) of the event's prime key. For example, when a script associated with a payment event is kicked off, the system populates a field called PAY_ID with the prime-key of the selected payment.
The script can use this page data model field to navigate to the pertinent pages. For example, if you were setting up a script to transfer a payment, the first line of the script would reference a navigation option to transfer the user to the payment page where they can initiate the transfer. This navigation option will contain context fields that matched the names of the fields in the page data model (this is how field values are passed to pages).
Set up one or more zones that reference these algorithms. The zones should reference the F1-TIMELINE zone type.
Configure the zone's visibility parameter to define an appropriate visibility script so that the zone only displays when the relevant data is in context:
Update your users' portal preferences and security rights so they can see the zone in the desired location on the portal(s).
You can set up many timeline zones. For example,
You might want different zones to appear on a portal depending on the type of user. For example, you might want one timeline for collection clerks, and a different one for customer service representatives.
For aesthetic reasons, you might want multiple simple timeline zones to appear on a given portal rather than one complex timeline zone. Each separate zone includes its own date range controls.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.