Card Footer Action
The card footer is a clickable strip below the message card that lets users act directly from a message. Each template has this single action, configured with a name and a trigger action. The strip can also be turned off for messages that only need to be read.
Footer Configuration
| Item | Description |
|---|---|
| Show footer | Turns the strip on or off. When off, the card keeps only its other content and has no click target |
| Name | The text shown in the footer strip, followed by a right arrow. Keep it short and action-oriented, such as View details or Open task |
| Trigger action | The action executed on click: open content details, an internal route, or an external URL |
Internal Route
Use an internal route when the footer should open a page inside the product. The target must start with / and must not contain spaces.
The routes below are available on the user side. Admin routes should not be used for user-facing footer actions.
Fixed Routes
| Internal Route | Purpose |
|---|---|
/workspace-apps | Opens the workspace app entry |
/workspace-apps/approval-center/approval-records | Opens approval records |
/notifications | Opens the message center |
/visualization | Opens visualization |
/visualization/design/new | Creates a chart |
/visualization/dashboard/design/new | Creates a dashboard |
Dynamic Routes
Replace {xxx} with the real value. Field variables can also be used to build the route.
| Internal Route | Purpose |
|---|---|
/forms/runtime/{formApiName} | Opens a form record list |
/forms/runtime/{formApiName}/new | Opens a form create page |
/forms/runtime/{formApiName}/view/{recordId} | Opens form record details |
/forms/runtime/{formApiName}/edit/{recordId} | Opens a form record edit page |
/workspace-apps/{appCode} | Opens a workspace app |
/notifications/detail/{inboxItemId} | Opens a message detail page |
/visualization/view/{chartId} | Opens a chart view page |
/visualization/dashboard/view/{chartId} | Opens a dashboard view page |
/visualization/dashboard/menu/{chartId} | Opens a dashboard menu page |
/visualization/design/{chartId} | Opens a chart design page |
/visualization/dashboard/design/{chartId} | Opens a dashboard design page |
Dynamic Route Examples
| Example | Description |
|---|---|
/forms/runtime/contract/view/{{record.data.recordId}} | Opens the current contract record details |
/forms/runtime/contract/edit/{{record.data.recordId}} | Opens the current contract record edit page |
/workspace-apps/approval-center | Opens the approval center app |
/notifications/detail/{{record.id}} | Opens the matching message detail page |
/visualization/dashboard/view/{{record.data.dashboardId}} | Opens a dashboard |
External URL
Use an external URL when the footer should open a trusted external destination. External targets must use https://.
Examples:
https://example.com/contracts/{{record.data.contractCode}}
https://docs.example.com/process
Variables In The Footer And Target
The trigger action can contain field variables, which is useful when the destination depends on the record. The footer name is limited to 16 characters, so keep it a fixed action phrase and build the dynamic part inside the route or URL.
| Example | Purpose |
|---|---|
View details | Fixed footer name for every record |
/forms/runtime/contract/view/{{record.data.recordId}} | Opens the matching internal record |
https://example.com/orders/{{record.data.orderNo}} | Opens a matching external page |
Test variable-based targets carefully before enabling the template.