New Destinations UI available now in BETA version

[yogananda]

A new Destinations UI for managing destination configuration objects is now available as a BETA version in the SAP BTP cockpit, side-by-side with the current UI. It is not yet at feature parity with the current UI, but feel free to try it out and send us your feedback.

Old Destination UI

Getting Started with the New Destinations UI

To start using the new Destinations UI, follow these steps:

1. Access the SAP BTP Cockpit: Log in to your SAP BTP account and navigate to the cockpit.
2. Navigate to Destinations: In the cockpit, go to the Connectivity section and select Destinations.
3. Explore the New UI: you can access to the BETA version, you will see the new interface. Take some time to explore the different features and options available.
4. Create a New Destination: Click on the "Create Destination" button and fill in the required details, such as the destination name, URL, and authentication method.
5. Save and Test: Save your new destination and test the connection to ensure everything is configured correctly

Check Connection


Export Destination in (JSON, YAML & Properties)

Benefits of the New Destinations UI

The new Destinations UI offers several benefits for SAP BTP users:

• Efficiency: The streamlined workflow and enhanced configuration options save time and reduce complexity.
• Usability: The intuitive interface makes it easier for users to manage their destinations, even if they are new to SAP BTP.
• Flexibility: The ability to configure advanced settings and custom headers provides greater flexibility in connecting to remote systems.
• Visibility: Improved visibility into destination details helps users quickly identify and address any issues, ensuring smooth operation of their applications

Conclusion

The new Destinations UI in the SAP BTP cockpit is a significant step forward in simplifying the management of destination configuration objects. As a BETA version, it offers a glimpse into the future of SAP BTP, where usability and efficiency are at the forefront. If you have access to the BETA version, be sure to explore the new features and provide feedback to help shape the final release.

[MatthiasL]

1) Why does your first screen says "Do not enter". Should we not use it anymore? Or is it more of a joke to push towards using the beta.

2)  The favorite button doesn't do anything
3) It doesn't seem to remember when you 'resize the columns'
4) Feature request: Would it be possible to introduce access control for Destinations? We don't want everyone to be able to see/use every Destination.
5) It would be nice of the UI/UX was a bit more smooth / modern and to be able to change the view (like more filtering and/or columns)

[yogananda]

@MatthiasL Thank you for trying out the Beta UI for Destinations
Point 1 - Its Old UI to create new/modify Destinations.. so having that stamp to ask Users not to create in the OLD way 🙂
Point 2-5 - Already many users have provided their feedback as well  and its on the development side.. could you provide the feedback via Survey link provided below.


https://sapinsights.eu.qualtrics.com/jfe/form/SV_7VZeDjYI5FSHJCS?source=destination 

[TomD]

While I'm happy to see a more usable UI and to no longer be faced with the page load / paging bug when viewing Destinations, this was a bit of a missed opportunity to streamline this more. Is there any reason not to have a drop-down option for existing Cloud Connector Location IDs and exposed resources at this point? Why do I still need to copy paste that ID and URL from the Cloud Connector tab?

Beyond that, the first time I tried to modify a destination I got n error:
"Failed updating the destination / Recieved response `400` with body: Property 'Name' has to be present only as path parameter"
Which apparently is an error that comes up whenever you try to edit the name of an existing destination in the Beta UI. Still works fine in the original. So that's not the greatest first impression. 🙂

Finally, I wouldn't expect to see this clearly marked "(BETA)" function available on our productive subaccounts which are clearly flagged to not enable beta features.