[UnifiedDataTable] Add support to Flyout Pagination in the UnifiedDataTable component

[opauloh]

Motivation

Currently, the UnifiedDataTable component doesn't provide a way to allow us to have Flyout Pagination controls, the primary goal is to implement that support in a way that Flyouts opened by the CloudSecurity DataTable have paginations, a secondary goal is to add that support in the shared UnifiedDataTable itself, so all consumers can enable Flyout pagination if desired.

Definition of done

• The Flyouts opened by the CloudSecurity DataTable has pagination
• Pagination in the Flyout as an optional property of the UnifiedDataTable: showExpandedDocPagination: true | false
• The property in the UnifiedDataTable is optional and defaults to false

Out of scope

• Advanced controls or customizations for the Flyout Pagination

Team tag

@elastic/kibana-cloud-security-posture

Related

#169247

[kfirpeled]

moved to 8.14

[opauloh]

Update: It looks like Flyout Pagination is now supported by the Unified Data Table

I'm going to confirm that information and we agreed in the Findings enhancement sync that we are going to prioritize this ticket in case in case the support is already implemented and we just need to "enable" it

[opauloh]

Update:

Flyout pagination is possible using the setExpandedDoc method, as currently implemented here by the DiscoverGridFlyout component, alternatively is also possible to use the Discover Flyout since it's possible to add custom tabs, this way we would get the benefits of having the Actions available in the Table tab.

[kfirpeled]

Hi Paulo, happy to hear there's a possibility to add the support for pagination through our flyout

this way we would get the benefits of having the Actions available in the Table tab.

I don't see how these actions are relevant to our use case. So in that case, would that be a limitation for us if we don't want to include that?

[opauloh]

If we use the DiscoverGridFlyout we get access to the paginations, Actions on the Header, and Actions on the Table

The compromise is that we can't customize the Title as we have today, and also that the Flyout doesn't have an overlay background.

I don't see how these actions are relevant to our use case. So in that case, would that be a limitation for us if we don't want to include that?

If the benefits are not appealing to include in our use case, it's best if we add the pagination to our flyout using the setExpandedDoc method than trying to disable the features we don't want to in the DiscoverGridFlyout, there's no limitation on handling the pagination ourselves.