Page Comparison

...

"buttons": {
"deleteButton": false,
"revokeButton": false,
"submitButton": true,
"recalculateButton": true,
"workflowDenyButton": false,
"workflowViewButton": false,
"denyClaimItemButton": false,
"asyncPublishingButton": false,
"rejectClaimItemButton": true,
"workflowApproveButton": false,
"approveCalimItemButton": true,
"workflowWithdrawButton": false,
"cancelComputationButton": false,
"validateClaimItemButton": false,
"workflowAddWatcherButton": false,
"workFlowAddApproverButton": false,
"allocationGridClaimItemButton": false,
"asyncPublishingClaimItemButton": false
}

Buttons can be hidden on tab or document (root) level. Criteria for dynamic display of buttons are defined in the same way as for tabs or steps, using hard-coded columns, attribute columns or attribute extensions. See How to Hide Custom Form Buttons Using JSON Configuration for a configuration example.

How button visibility is determined between root and tab settings:

• Button visibility is defined on tab level → the button on this tab behaves according to this definition.

• Button visibility is not defined on the tab level → the button behaves according to the root-level definition.

• If button visibility is not defined neither on the root level, the button is displayed because no definition means that the button is always visible.

• Button visibility is defined on the root level → the button on the list page behaves according to this definition.

• Button visibility is not defined on the root level → button is displayed on the list page.

Note: After the button visibility setting is changed in the Claim Type, you must refresh the web browser to see the changes in the UI.