This document provides an overview of the Salesforce UI API, which allows developers to build custom user interfaces using record data and metadata. It discusses key features of the UI API like CRUD operations and dependent picklists. Elements of the UI API like records, layouts, and actions are also explained. The presentation concludes with a live demo, considerations for the UI API, available resources, and time for questions.
About Me • SoftwareEngineer Trainee and a part of Center Of Excellence team at SaaSfocus • Independent Salesforce Consultant • Blogger and YouTuber at SFDC Stop
3.
Today’s Agenda • Introductionto User Interface API • UI API - Features • Elements of UI API • Live Demo – User Interface API Implementation • Considerations for UI API • Available Resources to learn UI API • Q & A
4.
User Interface API– An Introduction • Salesforce Developers needed a new API to build Lightning Experience • It came up with UI API which consists of the layout, metadata and record data altogether to build custom and dynamic UI • With UI API - you don’t have to take care about field level security, sharing rules, layouts and even picklists.
5.
Features of UIAPI • UI API provides you the record information along with the layout information • It also provides you the data and metadata about the actions implemented in the UI like:- Standard and Custom Buttons, Quick Actions etc. • You can perform CRUD operation on records with UI API • It also gives you the information about list views as well as makes it easier to render dependent and independent picklists
6.
Elements of UIAPI • Records • Layouts • List Views • Actions • Favorites • Lookups • Active Theme
Considerations for UIAPI • List of Supported Objects:- https://developer.salesforce.com/docs/atlas.en- us.uiapi.meta/uiapi/ui_api_get_started_supported_objects.htm • UI API uses the Salesforce API Limits. If the limit is exceeded, you’ll receive 503 Service Unavailable Error • To access salesforce resources, we have to add our custom host to CORS in Salesforce so that the requests are permitted • If you are building lightning components don’t use UI API, use Lightning Data Service instead