Gantt Chart

A Gantt chart shows the expected and actual timings for a Record. In the example above this is showing the expected and actual start and end dates for each WorkPlan. The X-axis is a timeline that the target and actual start and end dates for each WorkPlan are plotted against.

You can also enable a click-through on this report which allows the user to drill down into the records that the dates relate to. 

Example Chart

Configuration

To generate a Gantt Chart, you first need to be in the 'Reports' section where you will then be able to click 'Add Report' in at least one of the highlighted locations below. 

By clicking the button it should bring you onto a report selection page where you are shown various reports and some information about them. To choose a 'Gantt Chart' find the card containing the 'Gantt' chart then click on 'Create'. Alternatively, you can find it by searching and selecting 'Gantt' on 'Filter Types'.

Consequently, this presents you with the Report configuration options below:

Title: The title is the reference to the Report that will appear in the App for the users. It will appear in the left pane menu for the and also in the breadcrumb (header bar) at the top of the page which tells the user where they are on the site.

Sub Title: The subtitle is a banner that appears at the top of the screen beneath the title that allows you to give a short description the report, this can be useful for keys and user audience.

Identifier: This should reflect the label. The identifier is a system ID for referencing a Report. This ID must be unique per Report and must contain only letters and numbers starting with a letter. It must also be a minimum of three characters.

Report Type: Chart has to be selected for the options to see a Cumulative Matrix

Group: The Report Group is used if you need to group reports together. A Report Group will appear on the left pane, and once clicked, show the Reports in it below. They are collapsed when the App is first launched and expandable as required. 

Note: Report Groups will always display below non-grouped Reports.

Is Default: The default Report is the Report that the user will be directed to the first time that they open the App. If no default has been set then the user will be navigated to the Report with the lowest display order.

Note: Once a user navigates to a different Report, this preference will override the default option the next time they view the App if they haven't logged out in-between.

Is Hidden: This will hide the report from all users. It is commonly used whilst a Report is being reconfigured or if a Report needs to be removed temporarily to be reinstated at a later date.

Background Image URI: This option allows you to have an image behind the Chart by entering the image's Uniform Resource Identifier (URI). This generally is a character sequence identifying a resource, usually on the internet. In this context it identifies your chosen image, which can be useful to indicate zones within the chart, for instance, a RAG background, or simply for more tailored branding. For more information, click here

Example RAG Background - https://pixabay.com/illustrations/red-yellow-green-orange-lime-650676/

Chart Type: Choose from over 15 Chart Types - Here you will need to select 'Gantt'.

In-App Data Source Field: Some chart types can be created from Grid Field data to produce In-App Charts To select the Grid Field that the data will come from you can choose this as the In-App Data Source Field.

Base Filter: If the report is to always show a subset of Records, then the Base Filter can be used to apply a permanent Filter to the report. This Filter is always applied, and then user-defined filters and searches are compounded on top when the report is being used - For more about configuring base filters click here

Target Click-Through Report - With 'Target Click-Through', you can select a List Report for the user to drill down into to display more information about the Records that meet the criteria for that Matrix cell. It will apply the appropriate filters to that List Report to only show the relevant records. This can make an effective navigation tool for the App. 

Height: Define the height of the Chart - Denote with px i.e. 700px

Order By Date: By selecting this property it will ensure that the Records are displayed down the Y-axis in date order by Planned Start Date. If there is no Panned Start Date then they will order by Actual Start Date

Label: These are the labels that will appear in the UI for the chosen chart elements.

Base Field: This is the Field from the Record that will then define chart Field types.

Chart Field Type: 

• ProjectName: The value from this field in the Record will appear in the Y-axis as the title for that row. This Field is required before the chart can display data.
• ActualStart and ActualEnd: These are the two Fields in the Record that state the actual start date and the actual end date of the WorkPlan. These Fields need to be either Date or DateTime Fields. For each Record, a bar will appear between these two dates to represent the actual time taken.
• PlannedStart and PlannedEnd: These are an optional extra and will appear as a grey bar below the Actual timings. It can be used to give a comparison of the Planned active period against what really happened. These Fields also need to be either Date or DateTime Fields.
• Status: The bar to represent actual timings can have a colour associated with it to indicate the status of that item. This is done by choosing a RAG or RAGBB Field and then the bar for actual timings will appear in the colour value for that Field. 
• Hover Text: This is for additional text that displays when the user hovers their mouse over a Record on the chart.

Report Visibility

Similar to how app visibility works this can be set to hide your reports from certain users or teams, this can be great for hiding reports from certain teams or guests, for example, if you have employee-based performance reports that you only want management to see so you set it so just that team can see it.

Make sure to click the 'Save' button when making any changes in order for them to be added to the next app version. Once you have made all the changes you need to an application you are then ready to publish it to workspace.