Genpact Cora Knowledge Center


Customize the Grid Menu


Portal grids display a menu with the actions available for the user handling a case. Graphical user interface, text, email

Description automatically generated

You define the commands available for each grid by:

  • Editing the Commands Name block in the ServiceMetadata file
  • Editing or creating copies of the config files in the Commands folder. You can add, remove, and create new commands as necessary for your solution.

After editing the files, you must add them to the Commands folder, otherwise your changes don't take effect. 

The file name must begin as defined in the Commands Name block in the ServiceMetadata file.

Commands folder 


Description automatically generated

Location: ~\Shared Resources\Components\Flowtime\Config\ServiceMetadata\Commands

ServiceMetadata files 

Graphical user interface, text

Description automatically generated with medium confidence

Location: ~\Shared Resources\Components\Flowtime\Config\ServiceMetadata

ProcessInstances: Used for the instances grid of a specific workflow (In the portal, go to All Cases and then select a specific workflow.)
UserInstances: Used for the Cases I Started grid

Example of the message grid command config file


Description automatically generated


Description automatically generated

Config files code blocks

The Commands config files include several code blocks. 

You can create, edit, or remove code blocks to customize which commands to display in the grid menu.

ContextMenu IdDefines the commands that are displayed for each record in the grid.
This block references several ContextMenuItem blocks.
ContextMenuItemDefines the details and functionality of each menu command.
ToolBar IdDefines the commands that are displayed from each grid’s toolbar. This block references several ToolBarItems blocks.
ToolBarItemDefines the details and functionality of each toolbar command.
Each Command/ToolbarItem block contains the following fields:

Id: The Id of the commands

Command: The command function

CssClass: The CSS class that defines the display of the command

TextThe command text. Take this text from the relevant resource file.
DisplayRulesDefines which commands to display based on a set of rules.

The commands functions are stored in a Command Table block, which is also part of the config file. The Command Table can include several types of commands.

  • JavaScript
  • OpenWindow
  • Custom command 

To ensure that your JavaScript code is not lost with application upgrades, place it in the folder: ~\Shared Resources\externals\portal\js

JavaScript commands

JavaScript commands contain the following tags:

  • Id: The Id of the command
  • FunctionName: The name of the JavaScript function in the system
  • Parameters: The parameters to pass to the function, which can be an expression.
    For example, for the Menu>Open command, you must pass the Id of the item you have selected, so that the value of the parameter is the expression: $Item.Id.


Description automatically generated

Create a new command (example)

Create a new custom Service.config file, ServiceMetadata file, and Comand.config file named as follows:

  • Services.Custom.config
  • MessagesServiceMetadataCustom.config
  • MessagesServiceMetadataCustom.default.config


  1. In Services.Custom.config file reference the custom ServiceMetadata file: MessagesServiceMetadataCustom.config.Graphical user interface, text

Description automatically generated

  2. In MessagesServiceMetadataCustom.config, reference the custom command config file: MessagesServiceMetadataCustom.default.config.

The grid component contains the ConfigName property, which maps the grid component to its configuration file. For example, when you set ConfigName=”Custom”, the grid takes its configuration from Services.Custom.config.


The DisplayRules code block defines which commands to display based on a set of rules.


The $item context object holds the row’s data item properties.

For more details, see this article.

Make sure that you deploy the board and grid customization via the project template only and create the required XML transformations as described in this article.