Conversation
Evonsys
US
Last activity: 19 Aug 2025 10:59 EDT
How can I hide the Cancel button in a flow action (assignment shape) in Constellation UI?
I’m working with Pega Infinity 24.2. In a flow, I have an assignment shape that uses a flow action.
By default, Constellation renders Submit, Save for later and Cancel buttons.
For this particular step, I only want Submit and Save for later to be available and need to hide the Cancel button.
Is this achievable?
Pegasystems Inc.
GB
@MaleeshaW this is the prescribed part of the Constellation Design System, you can not hide this or any other OOTB buttons with configuration.
If you want to be able to extend Constellation UI to bring in elements of your own design system and approaches, then you can start exploring DX Components and SDK route. There are pro's and con's to this approach, so I can't comment on your exact needs, this Documentation outlines them pretty well.
If you have a very specific need to remove cancel, then you could do so with a DX component - I have seen this implemented on a few projects where there was such need. However, it is not well advised if its just a "i don't like it" requirement. Cancel is there for a reason:
- I could just close the browser, if you remove cancel from me then I'll just do that
- if this flow action is called from a modal (create or local action) then our prescribed design system has close/cancel UI actions, this is also prescribed
- what i accidently clicked a button and need to cancel out of it
Be good to understand the use case further but this isn't one I'd recommend
What can you configure?
@MaleeshaW this is the prescribed part of the Constellation Design System, you can not hide this or any other OOTB buttons with configuration.
If you want to be able to extend Constellation UI to bring in elements of your own design system and approaches, then you can start exploring DX Components and SDK route. There are pro's and con's to this approach, so I can't comment on your exact needs, this Documentation outlines them pretty well.
If you have a very specific need to remove cancel, then you could do so with a DX component - I have seen this implemented on a few projects where there was such need. However, it is not well advised if its just a "i don't like it" requirement. Cancel is there for a reason:
- I could just close the browser, if you remove cancel from me then I'll just do that
- if this flow action is called from a modal (create or local action) then our prescribed design system has close/cancel UI actions, this is also prescribed
- what i accidently clicked a button and need to cancel out of it
Be good to understand the use case further but this isn't one I'd recommend
What can you configure?
You can control the names of these buttons, same as you could in Traditional UI, as outlined https://docs.pega.com/bundle/platform/page/platform/case-management/con…. I have submitted feedback (FDBK-131450) so that this document is updated with which bits are Constellation specific, that could definitely be improved.
Pegasystems Inc.
PL
@MaleeshaW can you explain business need behind this request? Why keeping Cancel button is not acceptable? Clicking Cancel navigates back to case view and close (on UI) the assignment, that is it.