Types of Snippets
Snippets allow users to adapt their data presentation to specific needs. Both sheets and models contain some snippets created by default to enable input, read data, and view audit history. These default snippets cannot be edited or deleted. Users can create their own snippets for input, reporting, and visual creation. These snippets come in various types, each tailored to serve distinct purposes. They can be updated according to the requirements.
Standard Snippets
These snippets are accessible by clicking on the level 2 header of models and sheets. They are present in the snippet public section.
Input Snippet: This is displayed as the sheet name in the snippet list, available only for sheets. The purpose of this snippet is to enable input and data upload to the sheet.
Data Snippet: This snippet name is the same as the sheet/model name followed by the word "Data" in the title. It is used to review all the data contained in a model or sheet. This includes entered as well as calculated data.
History: This snippet contains the details of changes made to the sheet/model data over time. The snippet title appears as the sheet/model name followed by the word "History." This is also created by default and cannot be modified. This detailed history is contained in a tabular format, with columns such as:
Column |
Description |
|---|---|
Fields |
Contains detail of the selection for the field. |
Metric |
Name of the metric containing the value. |
Measure |
The value entered or calculated. |
Source model |
Name of the model the Snippet belongs to, blank in case of a sheet. |
Updated by |
Name of user updating the snippet. |
Updated at |
Name of the update made. |
Category |
Nature of the update, e.g., Input. |
Task |
Name of the task to which snippet is assigned, blank if unassigned. |
Reference |
Detail on the update nature, e.g., Update because of the Formula update. |
Event ID |
Unique ID to identify changes made in same event. |
Event Type |
Type of event, e.g., input, update. |
IP Address |
IP of the system from which update was made. |
Client |
Detail of the client system from where update was made. |
The time range for extracting history can be set. Data can also be filtered by scenario, entity, etc. The data history can also be exported.
User Defined Snippets
These snippets are created by users and can be modified. They can be private or public, depending on their configuration, v25.12: but OData snippets can only be public.
Report
- Purpose: Designed primarily for data viewing. They provide a structured layout that allows users to easily peruse data.
- Benefits: The layout of report snippets can be adjusted at any time, enabling the creation of data subsets for in-depth analysis. They are particularly valuable for scenarios where data is meant to be read-only, offering a clear and organized representation of information.
Visual
- Purpose: Brings data to life through dynamic visuals. They allow users to visualize system data in various ways.
- Benefits: Visual snippets offer different types of data visualizations, including comparisons, trends, compositions, and indicators, each with numerous ways to represent data. These visuals make data interpretation more intuitive and actionable, helping users gain insights at a glance.
Input
- Purpose: Input sheet snippets function similarly to reports but with an exceptional capability - users can enter data directly into them.
- Benefits: Data entry through various sources is supported, and just like report snippets, the layout and field members can be dynamically adjusted to match specific needs. Moreover, data saved in input sheet snippets is immediately updated in the JustPerform system, ensuring real-time data accuracy. This bidirectional functionality allows for the conversion of reports into input sheets and vice versa.
v25.12: OData
- Purpose: OData snippets function similarly to reports but without Columns. Additionally, a new field, Technical ID, has been introduced in OData snippets to enable exposing them as OData services.
- Benefits: OData snippets enable automated extraction of specific snippets without the need for manual export via API. This reduces dependency on UI-based interactions and allows consumers to fetch only the required snippets using filters and query options, such as $filter in OData. Additionally, OData snippets provide up-to-date data access directly from the source system.