Creating custom chunking buttons in cell-based tables


You can customize a table to have its own next and previous chunk buttons, whether content clipping is enabled or not, by using either the PERFORM-ACTION-TABLE-PREV-CHUNK or PERFORM-ACTION-TABLE-NEXT-CHUNK Run Process action in the active link.

By using the following keyword and workflow commands, a developer can calculate whether the next and previous chunking buttons should be enabled or disabled based on the current contents of the table:

  • $LASTCOUNT$
  • PERFORM-ACTION-TABLE-GET-CHUNKSIZE
  • PERFORM-ACTION-TABLE-GET-CURRENT-CHUNK

Workflow should enable the custom control for retrieving the next chunk when the following arithmetic operation evaluates to true:

$LASTCOUNT$ > value of PERFORM-ACTION-TABLE-GET-CURRENT-CHUNK * value of PERFORM-ACTION-TABLE-GET-CHUNKSIZE

Similarly, workflow should enable the custom control for retrieving the previous chunk when the following arithmetic operation evaluates to true:

value of PERFORM-ACTION-TABLE-GET-CURRENT-CHUNK > 1

For information about keywords, the Run Process action, and workflow commands, see Defining-workflow-to-automate-processes.

When content clipping is enabled for a cell-based table, PERFORM-ACTION-TABLE-GET-CHUNKSIZE returns the current visible chunk size of the table. The current visible chunk size is the number of cells that can be displayed in the available space, and can be less than or equal to the value defined in Developer Studio. For non-content clipped tables, PERFORM-ACTION-TABLE-GET-CHUNKSIZE returns the chunk size defined in Developer Studio.

When content clipping is enabled for a cell-based table, the custom chunking buttons do not update when a table resizes. The custom chunking buttons do not update because there is no event, and the event table refresh occurs just before the actual refresh of the table.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*