The Batch Configurations section in Admin Center > Batch allows administrators to define global settings that control the behavior and output of batch processes in Assette. These configurations standardize document naming, email behavior, file conversion, and packaging rules for batch operations initiated by the system or users.
Configuration Fields #
Each configuration item in this section serves a specific operational purpose, contributing to automation, consistency, and traceability of batch processes.
Batch Initiation Alert Email Sender Address #
This field specifies the email address that will appear in the “From” field of batch initiation alert emails. It is used to notify recipients when a batch process starts.
Default Value: ClientService@Assette.com
Batch Initiation Alert Email to Addresses #
This field defines the recipients of the batch initiation alert emails. These alerts provide early visibility into the start of a batch process.
Default Value: ClientService@Assette.com
Mime Types to Convert #
This setting lists the MIME types of documents that should be converted during the batch process. Documents matching these types are automatically processed for conversion.
Configured Values:
- pptx
Package Blank Page #
This Boolean setting determines whether a blank page is inserted at the end of each document in a package.
Value: False
A value of False means no blank page will be added, helping preserve space and document continuity.
Email From Address / Email From Name #
These optional fields define the email sender’s address and display name when documents are emailed as part of the batch delivery process. Leaving these fields blank will apply the system default or configured fallback address/name.
Mandatory Bcc Email List #
This field specifies one or more email addresses that will be blind copied (Bcc) on every batch-generated email. This is often used for compliance, auditing, or support monitoring purposes.
Recipient Packet Name Format #
This field defines the naming convention used for the recipient packet created during a batch process. It utilizes a templating format to dynamically include recipient-specific metadata.
Template:
{{recipientName}}_{{AsofDate(MMM-dd-yyyy)}}
Example Output:
JohnSmith_Aug-31-2025
Smart Doc Name Format #
This field defines how the names of smart documents are generated based on the delivery context (TargetType) and related metadata. It uses conditional logic and date formatting.
Refer to the Smart Doc Name Format article for a detailed explanation of this format.
Data Docs Name Format #
This field works similarly to the Smart Doc Name Format but is applied specifically to data documents. The naming convention adapts based on TargetType (e.g., adhoc, email, portal) and includes metadata such as account name, product name, language, and as-of date.
Like the Smart Doc Name Format, it uses templating language with conditional logic.
Examples of included variables:
- ContentType
- Organization
- AccountName (when Purpose == “Clients”)
- ProductName (when Purpose == “Sales”)
- AsOfDate with different formats depending on delivery type
- Timestamp,
Language,Currency, and others
Administrators can tailor this template to reflect organizational naming conventions and document tracking preferences.
Best Practices #
- When editing any of the template-based formats, test the output in a non-production environment to ensure document names generate correctly.
- Avoid using characters in the format string that are invalid in file names (e.g.,
/,\,:,*,?,",<,>,|). - Keep all email-related fields up to date to ensure proper notification and compliance coverage.
- Periodically review the MIME types list to ensure newly supported file formats are included if conversion is required.