In Assette, Content Types define the structure, classification, and intended use of various content elements that support report generation and data workflows. Among the available classifications, Input File Content Types serve a distinct and highly specific role: they are designed to receive structured data from uploaded files, typically Excel (.xlsx) or CSV (.csv) files, for use in generating dynamic reports.
This article outlines how to create a new Content Type with the Input File Content Class, including key considerations, configuration steps, and best practices.
What Is an Input File Content Type? #
An Input File Content Type is used when the uploaded file acts as a data source, not a content object for report inclusion. This type of content is essential in workflows where users need to provide structured datasets—such as portfolio performance, benchmarks, or custom attributes—which Assette uses to generate dynamic content for client or sales reporting.
Unlike Fixed Content (which may also be Excel or CSV files but is treated as a static document), Input Files are ingested and parsed to supply underlying data into Assette’s reporting engine.
Key Purposes of Input File Content Types: #
- Enable users to upload files with structured data
- Feed dynamic content templates with up-to-date information
- Integrate external data sources into Assette workflows
- Distinguish between files used for reporting (Fixed Content) and files used in reporting (Input Files)
Accessing the Content Type Management Interface #
To begin creating or editing a Content Type, follow these steps:
- Ensure you are logged in with Admin access.
- From the main navigation menu, select “Manage Content Types.”
- Click “Create New” to start a new Content Type.
- To edit an existing one, click the pencil icon next to the relevant entry.
Defining an Input File Content Type #
On the content type creation screen, you will need to complete several required fields. The table below explains how each field should be configured specifically for an Input File.
| Field | Required | Input for Input File Content Type |
|---|---|---|
| Code | Yes | Enter a unique code that identifies the content type. Cannot be changed once saved. Example: BENCHDATA-001 |
| Content Name | Yes | Provide a business-recognizable name for the input file. Example: “Client Benchmark Upload” |
| Content Class | Yes | Select Input Files. This ensures the file is treated as a data source and made available to dynamic content and reporting logic. |
| Content Group | No | Optionally choose a group like “Client Reports” or “Other” to help with content filtering. |
| Purpose | Yes | Choose Sales or Clients, depending on how the uploaded data will be used: • Clients – Data tied to client portfolios (e.g., benchmark uploads) • Sales – Data tied to product-related content (e.g., strategy performance figures) |
| Description | Yes | Describe how the data file will be used in Assette. Be clear about when and by whom the file should be uploaded. Example: “Used to load benchmark performance data for institutional client reports.” |
| File Name Pattern | Yes | Choose a filename pattern that Assette will use to recognize the uploaded file. These patterns ensure correct identification and ingestion. Common patterns include. |
File Name Patterns: Critical for Recognition #
Input Files require a defined file name pattern so Assette can automatically detect and associate the uploaded data with the correct content type and usage context. Selecting the correct pattern is essential for ensuring data is routed and parsed correctly.
If the appropriate file name pattern does not appear in the list, reach out to Assette Client Service to request that a new pattern be added.
Important Notes #
- Once saved or published, a Content Type cannot be deleted.
- You may hide an Input File Content Type from users by clicking the eye icon.
- Content in this class is not delivered to clients directly but used behind the scenes to populate client-facing outputs.