Users can share key events of a case with portal users in a timeline view.
Users have the following options to configure the component:
Options | Explanation |
Heading | The heading text of the 'timeline' component. It can be a maximum of 100 characters. |
Worksheet | The source worksheet is a compulsory item to decide where the information is drawn from. A worksheet with date entry must be created before it could present as an option. |
Filter | Information can display under certain level of filtering. Filter options include date, party responsible, procedural step, status, date added, added by, date updated and updated by. |
Card | The card view to use when displaying records. A card must be created before it could present as an option. (click here for more information about card) |
Form | The form view to use when displaying records. A form must be created before it could present as an option. (click here for more information about form) |
Date column | The date column is a compulsory item to decide the information to be displayed. Users can choose the display the date of the event, the date the event is added or the date the event is updated. (Date is the most suggested option) |
Primary sort field: Field | Users can choose a field as a primary sort field. |
Primary sort field: Order | Users can set the order as 'A to Z' or as 'Z to A'. |
Height | The display area of the portal page can be chosen from fit to content; at least half a page or at least a full page. |
Display example of 'timeline' component:
'Procedural Timetable' is the heading text. The 'find' option on the top left-hand corner helps users to navigate to an event by using the metadata; and 'more' option helps applying filters for more precise navigation. Below that, it indicates the of time that is displaying. On the right, it shows the number of event entries happened during the period. Users can pick and drag to the left or right to view the rest of the timeline. The timeline shows the events that are stored in the selected worksheet within the platform, with visible metadata fields that are designed in the 'card'.