Explore Data & Insights is for Developers and End Users:
- A Self-Service capability, calling it ‘like report browser’ doesn’t quite do it justice but yes it fulfils that use case for business users
- Design Time - Developers, using App Studio, can run Explore Data from that studio (not Preview), and they have additional design time configurations available to create reports (Insights) and Dashboards for business users and cases. (See item 4 below)
Just to further quantify here:
- “Reports” can be created two ways (just to reiterate my point earlier):
- Lists Views are their own rule type (Rule-UI-View), these are created from the UX tab and backed by a Data Page
- Insights are their own rule type (Rule-UI-Insight), these are created from Explore Data
- Explore Data > Insights are backed by your default data source defined on the case type / data object (data page). That data page must be queryable and has some other rules you need to follow to ensure Insights reporting works.
- The Insight created from Explore Data on this data object is not back purely from the Data Page or it’s Report Definition, a virtual report definition is created off the back of this and other elements in this class/object (so you will see more than what is just in this data page).
- You should set this data object with the properties (relevant records), embedded data (optimised properties) and data references (associations) it needs access too for reporting needs in Insights (see Some insights into Insights (and Explore Data))
- IF you want to run Insights directly from a Data Page then you must uncheck queryable and then in Explore Data (Design Time from App Studio) you can source Insights directly from that data page. (But again there are some limitations here, as some Constellation features are uniquely tied to queryable datapages)
