Views and record workflows
Caraer views give users ways to work with records, including tables and flow-style workflows. An object’s enabled traits add supported behaviours and determine which experiences are available for that object.
Why integrate
Section titled “Why integrate”Data written by your integration can appear in the same views people use for their daily work. Your product can supply a result or status while the customer chooses how to organize, filter, and act on those records in Caraer.
What you could build
Section titled “What you could build”A qualification service could add a score and review status to a customer-selected object. The customer could use a filtered table to find records needing attention and a supported flow view to manage the next steps.
Start integrating
Section titled “Start integrating”Inspect the target object’s traits and existing views in the API reference. The views API lists and manages view definitions; record queries and filters retrieve the underlying data. Use app-bar actions when a user needs to invoke your product from a view.
A view is a presentation and workflow configuration, not an additional permission grant. Verify the actual object’s traits and fields before assuming that a particular layout or workflow state exists. Keep record changes, view configuration, and any external processing as explicit parts of your integration.