Grid Controls

can be defined as spreadsheets or table data display according to the appropriate Data Model or data input type

imply that data listings are represented as a grid but without recurring to Grid Controls

Dataset Views are represented to the end-user as a grid that takes the entire page of the Layout. 

• grids: data is shown in grids only

each of the data representation forms of the Dataset View is configured separately and can be displayed to the end-users as 

• grid
• tiles
• board
• custom configuration form with expanded and hidden data display forms

• preview
• browsing and filtering  displayed data
• sorting columns of the grid (ascending/descending order)

Extra options for data modification:

• editing
• adding new records 
• deleting records

• preview (main purpose)
• browsing and filtering  displayed data
• sorting columns of the grid (ascending/descending order)

a basic grid type that presents records of the spreadsheet or a database table as rows and columns.

Displayed data has a pre-defined static structure of the columns, for instance: 

is used to group and display a set of dependent objects attached to an independent one, for instance:

• Object 1:  created incident (independent object);
• Object 2: a list of time tracking records created due to the work completed within the scope of a specific incident.  It is a dependent object with its own particular data structure.

We recur to the Multi Fragment Grid in order to show how long did it take to complete specific actions required for the incident resolution, implying that without the relation to a specific incident the time tracking record will make no sense:

Thus the Multi fragment grid objects are in subordinate dependency where one object directly relies on another.  The subordinate Object has its own structure and cannot exist without another stand-alone Object.

is used to group and display data of the independent objects having established relations due to some context or circumstances, for instance:

• Object 1: a list of created incidents ;
• Object 2: a list of services that can be ordered by the user.

By linking these independent and previously created Objects we recur to the Object Relations Grid in order to show all services that were affected by a specific incident.

Displayed data has a pre-defined static structure or the displayed columns, for example: 

 At the same time, each incident is a stand-alone object of the system that can have one, multiple or even do without the relation to any of the services.

Services are also represented in the system as stand-alone objects, as they are assigned or detached from the incident, ticket or problem and will still be available in the service catalog and can be ordered multiple times by different users.

is used to group and display a set of related and additionally filtered objects. 

Objects Grid can be considered as  a stand-alone type of grid as it:

1. displays objects of a specified type;
2. displayed objects are additionally filtered by specified criteria.

Objects Grid is widely used in Wizards,  for example, a list of  available services that can be added to the catalog:

The Object Grid displays all services that are available in the system (related service as an object) but were not added to the currently edited catalog (currently excluded services as a filtering criterion).

is used to group and display data that doesn't have a static structure  of the displayed columns, as each time their number depends on the data from the initial input source and therefore may vary,  for instance: 

• the data source has a pre-defined structure of the input data and holds a specific number of columns that can be shown;
• a page with a dynamic grid displaying does not have any pre-defined  fixed column structure;
• each time the data source has to be previewed on the page, the dynamic grid flexibly adjusts to the number of columns to be shown according to the data initially provided in the data source.

For instance, there is a data source which should be imported into the application. The data source is provided in a certain format with a specific structure of the data (text file, .csv,  .xml,  .xlsx, MSSQL data etc.) but each time the data and its structure differ. Uploaded file preview renders the data in the dynamic grid  according to the provided data source as follows:

defines end-user interaction rules with the standard components of the currently edited template element, such as:

• allowing or removing grid header row displaying with all the search filters;
• disabling grid items browsing;
• managing ranking or position of the entries in the grid;
• managing entries creation or deletion options.

defines the rules of the edited element displaying based on the end user's device type and screen resolution:

• desktop;
• tablet;
• mobile.