C3 AI Documentation Home

Change log for uiGanttChart

All notable changes to the package uiGanttChart made in master are documented here.

Version 8.8

Bug fixes

  • Fixed a bug where the page freezes after multiple user interactions on the event elements.

Version 8.6.8

Improvements

  • UiSdlGanttChart
    • Adding new config to group config in UiSdlGanttChartEventGroup, this allows users to decide from data side (for each event instance) or from metadata side (JSON, for all instances) from which side of the event will the line be shown for both fromSide and `toSide, which is the event group parent and the event group target. For more information check C3 AI Type definition for UiSdlGanttChartEventDataSpec.

Bug fixes

  • Fixed gantt not highlighting events when selectionChangeGanttEventAction was triggered.

Version 8.6.7

Improvements

  • UiSdlGanttChart
    • Adding the ability to highlight related dependencies on event hover while dimming unrelated dependencies.

Version 8.6

Improvements

  • UiSdlGanttChart
    • Adding the ability to define highlight areas on independent resource, previously users were able to define calendars per resource and those calendars would be highlighted in the chart when dragging an event but it would make all the resources show their calendars. Now you can define a specific calendar attached to an event and make it highlight only on specific resources by executing a collectAvailableResources function defined in your project on its own .c3typ file.
    • Solved a bug where bryntum was crashing when filtering over start and end data of the chart.
    • Added a new action GANTT_X_AXIS_START_END_TIME_SET to define xAxis config for gantt chart. You can either define a single setting or both at the same time.

Version 8.5.12

Bug Fixes

  • UiSdlGanttChart
    • Solved a bug that was adding selected and deselected events arrays to the events array in the data source state, this was not good because it was messing with the original data structure. Also there was an issue with having selectedEventIds and deselectedEventIds in the component state because it was triggering many rerenders but it was fixed. In conclusion, selectedEventIds and deselectedEventIds are now part of the component state and should be consumed with getConfigFromState.

Version 8.5

Improvements

  • UiSdlGanttChart

    • Adding the option to configure a time zone in the chart. You can add a timeZone property that defines a time zone id and the whole chart will show the data according to the time zone. All the different fields that deal with dates will have to be defined to be either a global date (using utc time) or local times (no UTC config).
    • Fixed a bug where the component was flickering upon performing changes to the data such as filtering or rerendering. There's a new approach for the data management inside the component.
    • Changed the source of truth for the component to listen to data changes, previously, the component relied on a set of fields in the component state that were exposed to be consumed in the redux actions side such as events or resources. Now, we no longer rely on these fields as it may cause important performance issues and conflicting data updates. If you want to manipulate the component data, instead of doing getConfigFromState(componentId, state, ['events']) or setConfigInState... you need to do a getDataFromState and setDataInState using the component data source ID. The component data source id can be retrieved using getCollectionDataSourceId function from UiSdlConnected. This function will retrieve the correct data source id to be passed to the getDataFromStateFunction. For example, if you want to check the events data you can do:
    JavaScript
    const dataSourceId = getCollectionDataSourceId('eventDataSpec', componentId);
const eventsData = getConfigFromState(dataSourceId, state, false);

    This will retrieve the data stored in entities => modified => 'componentId'_eventDataSpec_ds => {}

Bug Fixes

  • UiSdlGanttChart
    • Solving a bug where GANTT_RESOURCE_EXPAND_REQUEST and GANTT_RESOURCE_COLLAPSE_REQUEST were mutating the data structure from Object to Array and vice versa.

Version 8.4.1

Bug Fixes

Breaking Change

  • UiSdlGantt
    • Actions GANTT_RESOURCE_TREE_EXPAND and GANTT_RESOURCE_TREE_COLLAPSE were renamed to GANTT_RESOURCE_TREE_EXPANDED and GANTT_RESOURCE_TREE_COLLAPSED to make clear these actions are dispatched after the resources are collapsed or expanded.

Breaking Change

  • UiSdlGantt
    • Actions GANTT_RESOURCE_TREE_EXPAND and GANTT_RESOURCE_TREE_COLLAPSE where renamed to GANTT_RESOURCE_TREE_EXPANDED and GANTT_RESOURCE_TREE_COLLAPSED to make clear these actions are dispatched after the resources are collapsed or expanded.

Improvements

  • UiSdlGantt

    • Event drag action and now provides an array of event records.
    • Event drop action now provides an array of event records.
    • Event resize start action now provides the event record.
    • Event resize end action now provides the event record.
    • Added the actions GANTT_RESOURCE_EXPAND_REQUEST and GANTT_RESOURCE_COLLAPSE_REQUEST that triggers a request to collapse/expand a resource.

  • UiSdlGanttChartEventColor

  • Added 4 more new colors:

    • RED
    • GREEN
    • YELLOW
    • BLUE

Version 8.4.0

Improvements

  • UiSdlGanttChart
    • Added lag and lagUnit to the dependency object in UiSdlGanttChartEventDataSpec. These fields let you define the distance between one event and its dependant events.
    • Added support for many to many and one to many dependencies.
    • Added additionalFields option in eventDataSpec field to allow users to list additional data fields that can be retrieved from back end and stored in the state

New Features

Was this page helpful?