In Assette, artefacts such as Data Blocks, Brand Themes, and Smart Docs are often created and re-used in various contexts. Understanding when to create a new artefact versus reusing an existing one is critical to building scalable, maintainable client reporting and sales materials. Making the right decision ensures streamlined project execution, reduces technical debt, and improves ongoing support. This guide outlines best practices for determining when to create a new artefact in Assette, helping users maintain efficient and high-quality deliverables.
Create a New Artefact When… #
A new artefact must be created whenever there are fundamental structural differences between the intended outputs. For example, two Smart Pages that are visually transposed versions of each other must be separate Smart Pages, even if the underlying data remains identical.
Similarly, if two Smart Pages display identical data but one uses a table format while the other uses a chart, two separate Smart Pages are required. Although the Data Object can remain the same because it can support both table and chart visualizations, Assette does not support dynamically toggling between visualization types conditionally.
Likewise, a new Smart Shell must be created when the layout of the data changes meaningfully — such as reversing columns and rows — though, it is important to note that this still applies even if the Data Object used in both cases remains unchanged.
For Data Objects specifically, a new artefact is necessary if the fundamental structure of the data changes, such as transposing rows into columns. Data Objects allow users to dynamically group or filter data, but they do not transform the data’s fundamental orientation; such transformations must occur in a new Data Block. Similarly, when managing brand visuals, a new Brand Theme must be created if different color palettes or fundamental style changes are needed between strategies or product lines.
Reuse an Artefact When… #
You are encouraged to reuse existing artefacts when differences are superficial or setting-driven, rather than structural. For instance, if two tables differ only in the presence or absence of a few columns — and the columns exist within the Data Object — dynamic visibility settings can handle this without requiring a new Data Object. Likewise, if two Smart Pages differ only based on account, strategy, or “as of” date selections, and these are governed through configured settings, the same Smart Page can be reused across multiple outputs. Smart Docs can be flexibly reused as well when pages are selectively hidden or included through Content Classifications and Limitations settings.
Similarly, occasional data availability gaps, such as missing 10-year performance history for certain accounts, do not necessitate new artefacts. Provided the “Hide when no data is available” option is configured in the Data Object, the same artefact can serve multiple accounts without issue. Branding differences alone also do not require creating new Smart Pages or Smart Docs; instead, users should apply different Brand Themes to achieve the desired visual distinction across deliverables without fragmenting underlying artefacts.
When considering Data Blocks, the decision is nuanced: users should reuse Data Blocks when they deliver the same data from the same source, such as sector attribution data from FactSet. However, best practice discourages combining distinct datasets into a single Data Block unnecessarily. For example, sector attribution and regional attribution should be maintained as separate Data Blocks to keep designs clean, readable, and easier to troubleshoot. Overly generalized artefacts introduce confusion and technical risk during later template updates, particularly when formatting client data tables or managing custom table settings in Assette.