ComposerAI gets smarter about how you generate, where you generate, and what shows up in each document
This release is about removing the remaining friction points in the AI template workflow — generating documents from wherever you're already working, handling multi-record runs more flexibly, and making your templates smart enough to show the right content for every record automatically.

Generate AI template documents directly from Ascendix Search
Until now, producing a document from an AI template meant opening Composer, navigating to the template, and triggering publication. If you were already working in Salesforce — looking at a listing or reviewing a contact — it meant switching contexts to find the document you needed.

That extra step is gone. You can now generate publications from AI templates directly from the Ascendix Search window inside Salesforce, the same way you'd generate from a standard Composer template.

How it works:

1. In Salesforce, open Ascendix Search and find the record you want to generate a document for.
2. Click the Composer icon as you normally would.
3. Select your AI template from the template list — AI templates now appear alongside your standard templates.
4. Confirm and let Composer fill and generate the publication in the background.

The result lands in your publications list in the Composer app and on the selected records, as usual, ready to review and export. You never had to leave Salesforce to get there.

Choose between a single combined PDF or separate files when generating for multiple records
When you generate a publication from an AI Template for more than one record at a time, you now decide upfront how the output should be packaged.

Separate PDF per record — each record gets its own standalone document. This is the right choice when you're producing individual property briefs, client-specific materials, or documents that go to different recipients.

Single combined PDF — all records are merged into one document in sequence. This is what you want when you're building a portfolio, a multi-listing overview, or comp reports.

How to use it:

• In Salesforce: “Single PDF” is a default behavior, no action is needed. To switch to “Separate PDF per record” select the corresponding checkbox on the Ascendix Composer window in Salesforce.

• In Composer: when you click Generate Publication and select multiple records, Composer will ask which format you want before confirming. Pick the one that fits your use case — and Composer handles the rest.

  

Control what appears in each document with conditions in AI templates
AI templates now support conditions — rules that determine whether a section or element is shown, hidden, or replaced with different content depending on the data in the record being generated.

This is particularly useful when one template needs to serve multiple scenarios. Instead of maintaining separate templates for sale listings and lease listings, or for different asset classes, you can build one template and let conditions handle the differences automatically.

What you can do with conditions:

• Show a section only when a specific field has a particular value (show "Investment Summary" only when Listing Type = For Sale)
• Hide a block entirely when the data isn't relevant (hide the rent schedule section for sale listings)
• Replace content based on field values — swap out a header, a paragraph, or a callout block depending on what the record contains, without removing the element from the template structure

How to set a condition:

• Select the element or section you want to control in the AI Template editor.
• Open its settings panel and look for the Conditions option.
• Define your rule — choose the field, operator, and value — then save. The condition is evaluated fresh on every publication run against the actual record data.

  

  Tips for working with conditions:

  • Field values in conditions are case-sensitive — make sure your condition matches the exact value stored in Salesforce.
  • You can add conditions to individual text blocks, image elements, and entire sections.
  • Test your conditions by generating from a record where the condition should trigger and one where it shouldn't — confirm both outputs look correct before sharing the template with your team.
  • Conditions don't affect the template layout in the editor — you'll always see all elements while editing. The conditions only apply at generation time.