> For the complete documentation index, see [llms.txt](https://docs.santacruzsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.santacruzsoftware.com/gemini-home/reference/completion-methods.md). # Job Completion & Output Methods Comprehensive reference of all available job completion, file transmission, and email distribution methods in BrandingUI. When a user completes customization of a template, package, or form, BrandingUI triggers one or more defined **Completion Methods** to deliver the finalized assets. Administrators configure these settings under **Global Settings -> Completion**. Methods can be required and hidden, selected by default, optional for the user, or unavailable for a particular asset. Templates and Packages can define allowed file types, a PDF preset, JPEG resolution, and whether approval is required. A JPEG resolution of `0` uses the size defined by the asset designer. *** ## Available Completion Methods Administrators can configure multiple output methods of any of the following types: ### End User Downloads Allows the end-user who customized the asset to download their high-resolution results directly from their browser. * **If approvals are required**: The user receives an email notification with a secure download link once their job has been approved. * **If approvals are not required**: The user can download their finalized assets immediately after clicking **Finished**. ### Approver Downloads Final Results Restricts downloads of the high-resolution final results to authorized **Approvers** only. The standard user cannot access the final high-res output. ### Notify Someone to Download Files Automatically sends a notification email with secure download links to designated recipients immediately after a job completes. * Useful for dispatching final print files straight to external production shops or printing partners. * Recipients do not need to have accounts on the BrandingUI site. ### Transmit Files via FTP Transmits a ZIP archive containing the finalized outputs directly to an external FTP server. * An XML metadata file containing the full job specifications is automatically included inside the ZIP file. * Supports **Explicit SSL** (explicit FTPS over port 21). * Features a built-in **Test** button to verify network connection and FTP authentication immediately in the settings panel. ### Transmit Files via the Internet (HTTP POST) Transmits a ZIP archive containing the final outputs as an HTTP POST request to a defined destination URL. * An XML metadata file with complete job details is included inside the ZIP. * Supports **HTTPS** (highly recommended; prefix URL with `https://`). * A client ID query parameter (formatted as `c=`) is automatically appended to the destination URL during transmission. * Additional custom query parameters can be specified directly in the URL field. * Includes a **Test** button to verify destination endpoint reachability. ### Email via Silverpop (Santa Cruz / PrintUI HTML Email Add-on) Integrates with the Silverpop email service to automatically schedule and transmit customized HTML emails to designated contact lists. * *Note: Requires HTML output options enabled on your BrandingUI subscription and template files designed with companion HTML email modules.* * **Required Parameters**: * **API URL, Client ID, Client Secret, & Refresh Token**: Sourced from your Silverpop account settings. * **API Timezone**: Must match your Silverpop account's default timezone to prevent scheduled transmission errors. * **Base Query ID**: Used to map Silverpop contact lists to Department names in the Business Structure. (Set to `0` to query the entire database, though this may run slowly). * **Upload Folder**: Specifies where the generated email templates will be deposited (named using dates and template names). * **Sender Name & Email**: The name and email shown to email recipients. * **Templates Header & Footer**: Custom raw HTML blocks inserted dynamically into the header/footer placeholders of the companion email templates. ### Email via MailChimp (Santa Cruz / PrintUI HTML Email Add-on) Integrates with MailChimp to deliver customized emails to contact lists. * *Note: Requires HTML output options enabled on your BrandingUI subscription and templates containing companion HTML email elements.* * **Required Parameters**: * **API Key & Upload Folder**: Sourced from your MailChimp administrator dashboard. * **API Timezone**: The local timezone for scheduled emails. * **Sender Name & Email**: The default sender details for email recipients. * **Templates Header & Footer**: Raw HTML code inserted into the header/footer placeholder elements. ### Upload to a Connected DAM When LinkrUI and a destination DAM are enabled, completed and approved outputs can be uploaded individually to a selected DAM folder. BrandingUI records the upload history on the job so administrators can audit which outputs were sent and where. ### Form Completion Forms use approval and completion settings but do not require the same output file-type selection as Templates and Packages. Email completion methods are not exposed in exactly the same way for Forms, so test Form-specific outcomes separately. ## Additional Completion Options Administrators can fine-tune global output behaviors in **Global Settings -> Completion -> Other Options**: * **CC the Final Results**: Input up to three email addresses to automatically receive carbon-copy summaries of all finalized and approved jobs, along with view-only links. * Administrators can choose which output types CC recipients may access and which PDF preset their links use. * **Include Category in Download Name**: Prefix output filenames (such as generated PDFs or images) with the asset's active category name (e.g. `Flyers_MyBusinessCard.pdf`). * **Auto-Complete Inactive Jobs**: Specify a duration (in days) after which incomplete, inactive jobs are marked completed automatically. This prevents ancient drafts from triggering endless automated reminder emails. * **Lock Digital Package Outputs**: Prevent end-users from overriding the specific output parameters (like PDF presets or JPEG/PNG preferences) defined by the InDesign designer. ## Output File Naming Conventions (Digital Packages) For digital package outputs containing multiple artboards, files are automatically generated using a standardized naming layout to ensure perfect sorting and clear identification. * **Standard Format**: ` - - .` * *Example*: A customized social ad block output would save files named `Promo Banner - Instagram Square - 1200x1200.jpg` or `Promo Banner - Facebook Cover - 820x312.jpg`. * **Extensions**: BrandingUI standardizes all raster image package outputs using the lowercase `.jpg` file extension (instead of `.jpeg`) for consistent compatibility across modern corporate DAM platforms. Other downloaded filenames can incorporate the asset name, an optional Category prefix, and the submitted job reference. BrandingUI removes invalid server characters automatically. ## Pre-Approval Download Protection To safeguard intellectual property and ensure quality control, standard users are restricted from downloading high-resolution files for any job configured with approval-dependent completion settings (e.g., "Enduser downloads after approvals"). * While a job's status remains **Pending**, the standard user's hamburger menu on the Job Details page will hide or disable the **Download Job** options. * Download permissions are instantly unlocked once an Approver or Administrator changes the job's status to **Approved** or **Completed**. ## Troubleshooting: Bad Email Addresses BrandingUI tracks delivery failures to protect SMTP domain reputations: * **Bounce Tracking**: Permanent delivery failures (e.g. invalid user or mailbox not found errors returned by receiving SMTP servers) place the affected email address on a system-wide **Bad Email List**. * **Blocking**: To comply with SMTP provider limits, BrandingUI blocks all subsequent email notifications to any address flagged on the Bad Email List. * **Removal Diagnostics**: 1. Resolve the underlying email account issue on your mail servers. 2. Navigate to **Notifications Settings**. 3. Enter the flagged address and click the **Test Email** button to send a verification message. 4. If the test email is delivered successfully, the address is instantly removed from the Bad Email List. *Note: Running this SMTP test is the only way to unflag a bad email address.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.santacruzsoftware.com/gemini-home/reference/completion-methods.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.