Allow Users to Explore Data with Self-Service Analytics

Overview

Appian Records allows developers to stitch together data from multiple sources into a single, unified data fabric. With your data in a central location, you can build applications faster. But it's not just developers who benefit from Appian's data fabric. You can allow any user to explore your enterprise data so they can discover new business insights.

With Appian's self-service analytics capabilities, users can browse enterprise data and build their own custom reports. When they partner with Appian AI Copilot, users can dig deeper into their data using AI generated insights to identify patterns, trends, and outliers.

Self-service analytics allows any user to answer common questions about enterprise data on their own, which frees up developers to build the more complex, data-rich reports and processes that need their full expertise.

To allow end users to leverage Appian's self-service analytics capabilities, you must:

• Review security on your record types.
• Allow users to build reports.
• (Optional) Prepare data for end users.
• (Optional) Enable Appian AI Copilot.

About self-service analytics

Self-service analytics allows end users to reuse your application data so they can explore and analyze data on-demand. In this section, you'll see how the data concepts you already know are presented to end users, and how they can leverage that data to uncover new insights.

Datasets

As a developer, you’re familiar with the record type and how relationships and record type security let you access data from the record type and its related record types. To end users, we use datasets to represent this same capability so they don't need as much familiarity with the technical details of your data fabric.

Each dataset is made up of a record type and its one-to-one and many-to-one related record types. For example, the image below illustrates the Customers dataset, where the Customer record type is the base record type. Based on the one-to-one and many-to-one relationships configured on the Customer record type, this dataset would include data from the Customers, Districts, Addresses, and Credit Cards record types.

A dataset will not include data from one-to-many relationships. So if the Customer record type has a one-to-many relationship to the Order record type, it would not appear in the Customers dataset. Instead, a user could explore order and customer data together using the Orders dataset, so long as the Order record type has a relationship to the Customer record type.

Users can learn more about a dataset by hovering over the vendor logos. The following image highlights the elements that make up a dataset:

#	Element
1	The data source of the base record type, represented by the vendor logo. In the example above, the Appian logo represents the Appian Cloud database. Users can hover over the logo to see the source type and the source name of the base record type.
2	The number of rows in the base record type as of the last full sync.
3	The number of data sources included in the dataset. This number includes the data source of the base record type.
4	The data source of each related record type, grouped by vendor. Only the unique vendor logos will display here. Users can hover over each logo to see which data comes from each source.

Reports

Using any dataset as a starting point, users can further explore and analyze their data by displaying hand-picked fields in a grid or chart, and formatting that data to meet their specific needs.

While previewing self-service analytics, users cannot save their reports. However, they can still gleam real-time insights to answer on-demand business questions.

Chat powered by AI Copilot

Once a user builds a grid or chart, they can gain new insights about their data using Appian AI Copilot.

Users can ask AI Copilot questions about their data, or select from a list of suggested questions to discover potential areas of improvements and next steps.

AI Copilot can only analyze aggregate data. This means that AI Copilot is only available for reports that either group data or apply a calculation to their data (like sum, count, or average).

Review security on record types

Before you allow users to explore your data fabric, you should review the security on your record types.

By default, any record type with data sync enabled will be available as a dataset to end users.

Each dataset will inherit the record type object security and record-level security configured on the record type and its related record types. If you've already secured these aspects of your record type, there's likely no additional configuration necessary.

Users can only view data from a record type if they have the following security configurations:

• At least Viewer permission on the record type.
• Record-level security that allows them to see the appropriate records (or rows of data in the dataset).

To view all the data in a dataset, a user must have the above security configurations on the base record type and on any related record types.

Allow users to build reports

Once you've given users the appropriate record type security and record-level security, you must allow them to build self-service reports.

To allow users to build their own reports, you must add them to the Data Fabric Report Creators system group.

Once added to the system group, a user can start using Appian's self-service analytics capabilities by selecting Data Fabric Analytics from the navigation menu.

Prepare data for end users

Self-service analytics gives users the flexibility to explore your record types as datasets.

Each dataset will reflect the name, description, fields, and relationships configured on a synced record type. To provide users with the best experience, you should review the follow elements of your record type since they will be visible to end users.

Record type display name

Each dataset is labeled with the Display Name (Plural) value from the record type.

Review the record type's display name to ensure that it does not include an application prefix and that it can be easily understood by end users.

To edit the record type’s display name:

1. In your record type, go to Settings > Properties.
2. Update the Display Name (Properties) as needed.
3. Click SAVE CHANGES.

Record type description

When a user hovers over a dataset, they will see the record type’s description.

Review the record type's description to ensure it does not include any developer terminology (like "record type" or "data sync enabled"), and that it is useful to an end user. The description should help users understand whether or not this is the information they’re looking for.

To edit the record type’s description:

1. In your record type, go to Settings > Properties.
2. Update the Description as needed.
3. Click SAVE CHANGES to close the dialog.
4. Click SAVE CHANGES to save the record type.

Field names

When a user selects a dataset, they will see a list of fields from the base record type and any one-to-one and many-to-one related record types. They can use these fields to build a grid or chart that aggregates, filters, or sorts the dataset.

To ensure users can easily find the fields they need:

• Use camel case formatting for all record field names. A dataset will convert any camel case field names to title case field names so they're easier to read. For example, if you have a record field called lastName, it would be converted to Last Name in the dataset.
• Logically group record fields together. The fields in a dataset will appear in the same order as the fields in the record type. Ensure that fields like firstName and lastName, or address and zipCode are grouped together in the record type's data structure. This will ensure that the fields appear next to each other when a user selects fields for their report. Note that you cannot reorder custom record fields.

The image below illustrates how the fields in the Customer record type appear to end users in a dataset:

To edit the name and order of a record field:

1. In your record type, go to Data Model.
2. Click MAP RECORD FIELDS.
3. To rename a field, update the Record Field Name.
4. To reorder a record field, click Drag to reorder and place the field in the proper order.
5. Click FINISH.
6. Click SAVE CHANGES.

Relationship names

When a user selects a dataset, the data from any one-to-one or many-to-one relationships will appear under the relationship name. For example, the image below displays the Customers dataset, where the related data appears under the relationship names.

Review your relationship names to ensure that they are easily understandable and do not include an application prefix. For example, if you have a relationship name like ARregion, you should update the name to region so it displays as Region in a dataset.

To edit a relationship name:

1. In your record type, go to Data Model.
2. Under RELATIONSHIPS, click the relationship name you want to edit.
3. Update the Relationship Name as needed.
4. Click OK.
5. Click SAVE CHANGES.

Data source logos

Each dataset will display the data source of the base record type and its related record types using vendor logos. The vendor logos that appear on a dataset are the same as the logos that appear in the record type relationship diagram.

A dataset will automatically display the logos for any Appian supported databases and certain connected systems.

The following connected systems will not automatically display a vendor logo, but you can manually configure a logo to display:

• HTTP Connected System.
• OpenAPI Connected System.
• Custom JDBC Connected System.

To display a vendor logo for these connected systems, select an image for the System Logo in the connected system's properties.

Troubleshooting and limitations

As a developer, you may be asked to troubleshoot or explain certain aspects of self-service analytics to your users. Use the section below to troubleshoot and address user questions.

Unavailable datasets

If a record type fails to sync, the data in the end-user workspace will be unavailable. This means that users cannot select the corresponding dataset, or use the data in a report.

To ensure that your data is syncing successfully, you can check the status and history of syncs associated with your record type.

See troubleshooting data sync for information on how to resolve sync issues.

Inability to save a report

While previewing self-service analytics, users cannot save their reports. However, they can still gleam real-time insights to answer on-demand business questions.

Unanswered questions from AI Copilot

If AI Copilot cannot analyze a report, it may be because:

• The report does not contain any aggregated data. Users must either group data or apply a calculation (like sum, count, or average) to aggregate data for analysis.
• The report is too large. User should remove fields or apply a filter to reduce the number of rows.
• The user has exceeded the token limit of the Azure OpenAI Service license. This will require the user to start a new session.

Sessions and token limits

A session is a conversation between a user and AI Copilot. During a session, a user can ask AI Copilot questions about their data. At some point, a user may receive a message from AI Copilot indicating that the conversation has reached its limit. This occurs when the user exceeds the token limit on a given session. The number of questions a user can ask AI Copilot in a given session is determined by the token limit of your Azure OpenAI Service license.

If a user hits the limit, they will need to start a new session to continue asking questions about their report. Users will either be promoted to start a new session, or they can click Restart your conversation with AI Copilot to manually start a new session.

AI Copilot won't remember questions from a previous session. If a user starts a new session, AI Copilot won't have any context about the previous conversation. This means AI Copilot won't have answers to follow-up questions from a previous session. Users will need to provide AI Copilot with the necessary context at the beginning of each session.

Learn more about AI Copilot.

Self-service analytics on mobile devices

Self-service analytics is not supported on mobile devices.

Accessibility

Self-service analytics is not fully accessible. Users with disabilities including blindness, low vision, color perception, and mobility limitations may experience difficulty performing some tasks or functions in the workspace.

Feedback