Creating Actionable Grids With SXP Extensibility

First published on: 03/20/2025/12:00 pm

An actionable grid can be created via the project assets page, using the add asset menu. 

When adding via the datastore, your datastore will be pre-populated. 

Connection settings 

• Datastore – The datastore that will be used for the grid. 
• View –  A subset of the datastore based on defined criteria.
  • Go to the 'View' section to see details. 

Grid settings 

• Allow users to add new rows – Allow the grid user to add new records. 
• Save event workflow – The workflow from the project that will be fired when SAVE is clicked on the grid. 
• Edit mode – A form or connector screen that will be loaded when editing a record of the grid. 
• Enable conditional forms in edit mode – Lets users select several forms to be opened based on the values of one or more fields in a record. 

Format Columns/Data 

The type is driven by the datastore definition, and the format can be configured based on the type. 

• Calculated field – See a grid's advanced options. 
• Group by header – Group the grid by header. 
• Allow user update – Allows the grid user to update the field values.
  • Required fields are set to true by default and cannot be unset. 
• Enable lookup – See a grid advanced options. 
• Drop down – Available for string-type fields.
  • Field values will be displayed as a drop down with pre-defined values.  
• Values – When the field is a drop down or symbol, the grid designer can set the list of valid values.

• Default value – When adding a new record, this is the default value.
  • The default value can be a constant or driven by a user profile parameter. 

• Slicer – When this checkbox is open, the field will be added to the slicers/filter options on the grid view and allow slicing/filtering the data based on its values.
  • See more about slicers in the 'Visualizations' advanced section. 

You can now save your settings and preview the grid. 

New added/updated rows will appear in yellow until saved. 

Use the undo options in the top panel to revert the changes. (Note: Changes cannot be undone after saving.) 

Blue indicates the selected row. 

Users can edit the row inline or use the edit option on the side panel, which will slide open the related form. 

Now your grid is ready.  

Calendar View 

When a datastore contains one or more date fields, a user can configure a calendar view for the grid.

When a calendar view is defined, it will be the default view for the grid. 

To set up the calendar view, navigate to the grid settings 'calendar view' section. 

When only one date field exists in the datastore, that field will be pre-populated and used as the start date. 

When more than one date field exists in the datastore, the user can populate a start and end date. This will determine the event's length on the calendar. 

Description – What information will show in the calendar cell. 

Title format – Optionally, format the information defined in the description.  

Resource ID and title fields – Optionally, group the events by any field in the weekly view. 

Now you can save and go back to preview your grid. 

You can navigate (in red), using the arrows, to the next and previous period (next/previous year, month, week) or easily find your next/previous/last/first event (blue). 

The grid menu now has a new 'View' selector. 

Table – Shows the grid representation 

The monthly/yearly/weekly views will show your data in a calendar. 

The weekly view will show your items based on the weekly view configuration. 

• Slot duration – Shows the fraction of the time on the view. (15 min, 30 min, 1 hour) 
• Slot label – Shows how often we'll show the time label. 
• Min/max time – Shows the minimum and max hours in the day. 
• If there are no times in your data, hours will not appear on the view.
  • Otherwise, the event will be placed in the appropriate slot. 

No time: 

With time: 

• Yearly view setup – Configure how to present the yearly view.
  • It's not recommended to show all 12 months in large data sets, as this will significantly harm performance.  

Drag and drop: 

Use drag and drop on any view. Click and hold the event to move it around. 

Moving an event in the monthly/yearly view will update the start and end date but keep your hours the same.

On the weekly view, you can move the event to a different date or expand or shorten the duration, which will update the hours in addition to the date.

You can also drag and drop the event into a different resource, which will update the relevant column value. 

Note: Drag and drop is possible when the relevant columns are editable (start date, end date, resource). 

Clicking on the cell will launch the same form editor panel as the table view edit option. The user can update the values and save. 

Datastore Views 

Datastore views (created via an actionable grid setup page) allow the grid designer to filter the displayed results based on several column values and limit and re-order the displayed columns. This can be used to show rows relevant only to specific users, date ranges, etc. 

To set up a new view, navigate to the grid, open the connection settings, and click 'Add New View'. 

This will open the new view dialog. 

The user can set one or more conditions and select 'Match All (AND)' or 'Match Any (OR)'. 

A condition must specify the column condition (greater than, equals, contains, etc.). 

When specifying the value, we can set the a value OR set to user-supplied parameter. When this option is selected the user will be prompted to provide a value in runtime and the data will be filtered based on the evaluation. 

The last part shows what columns will be displayed for this view and in what order. A view can contain only column selections without any filters. 

Once setup is done, close this window and save your grid. 

Now, the parameters option is opened on the left navigation and the created filter is populated in the connection settings. 

Click on the parameter setup option. 

For each parameter defined as user-supplied, the grid designer will have to specify the source of the data. 

Profile — The value will come from the end user's profile parameters, such as first name, last name, email, and any other parameters defined at the user level. 

User-entered – The value will be provided by the user in runtime of the grid. When the parameter field type is text, we can use a predefined manual list of values, open text, or a list of distinct values in the datastore column. 

If we save and go back to the preview, we will see a new parameters section.