Why?
End users experience Portal buttons as part of the solution, not as generic web client launches. Today, the app execution window location is not controlled per starting point, which can make the experience feel inconsistent or less tailored to the user workflow.

What?
Allow a designer to define the app execution screen location individually per Portal button.

As an alternative or fallback, allow the end user to set and save the screen location per started app, regardless of whether it was launched from a button, double-click, or another start action. The saved location should be remembered per started app.

Acceptance Criteria:
[ ] Best case but optional: A designer can configure the app execution screen location for each Portal button .
[ ] Apps launched from different buttons can open in different configured locations.
[ ] If user-defined positioning is supported, the selected location is saved per started app.
[ ] The saved location is reused the next time the same app is started.
[ ] The behavior works consistently whether the app is started from a button, double-click, or another supported launch action.