Quality of Life Improvements in the ODC Deployment Cycle
Dependency Overview, when deploying an end-user application, it’s helpful to see a detailed overview of dependencies that might compromise the deployment. While this is a valuable feature, it could be even more effective if it allowed direct interaction with those dependencies—such as clicking on them to initiate their deployment or making the process more seamless. Currently, if multiple core applications (e.g., 8 or more) must also be deployed, you need to manually track and list them, which can be cumbersome.
Navigation During Deployment, if you decide not to proceed with deploying a specific application after selecting a revision, it would be useful to have an option to navigate directly back to the application selection screen via the left-side menu. At present, the process involves either restarting by going back to the “Deployments” screen or clicking "Back" multiple times, which is not ideal for efficiency.
Improving Feature Toggle, managementFeature toggles are essential for enabling parallel development and hotfixes, aligning with best practices recommended by OutSystems. While it's possible to organize feature toggles using folders in the development studio, this structure doesn’t carry over to the cloud interface, where you manage toggle values. Improving toggle management in the cloud would significantly enhance deployment workflows, as it directly impacts the flexibility and control required during deployments.
A last one that also goes hand in hand with the deployments are the secret settings that you might need for API's (just an example). Whenever you make use of a new settings or app that uses an existing api you will need to fill in the setting its value. Because they're secret and always filled in with a default prompt you can not tell that its value is already filled in and if it's filled in that it's correct. Obviously this is intended but it can make big deploys with multiple applications hard to manage. An easy way to fix this could be an 'updated on' field that shows when the value was changed if changed at all so you can easily see if you have already updated the value.
Thanks in advance for all already made improvements.
Kr,
Owen