AAE-29971 Buttons for dynamic component

[tomaszhanaj]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation
• Other... Please describe:

What is the current behaviour? (You can also link to an open issue here)

What is the new behaviour?
https://hyland.atlassian.net/browse/AAE-29971

Does this PR introduce a breaking change? (check one with "x")

• Yes
• No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

[eromano]

@tomaszhanaj can we add some unit test?

[dutta-arnab1]

Can Dedicated Screens be rendered without a mat-card? Intention of Dedicated Screens would be more of a full screen complex screen. I don't have a strong opinion on this but a point to consider.

[tomaszhanaj]

I tried solution without mat-card. This is how it looks

and this is with mat-card

and I think that there is no big difference. Mat-card is used for all tasks. Workflow for tasks is like: show it within table and when the user wants it to be fullscreen, there is a button to do it. So your component needs to provide function to make component fullscreen and it should fit space that is left by parent.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud