Rules and publishing settings

Availability: these connected controls pass local checks. Their Dev workflow checks remain open. The sample workspace has separate, simpler rules.

Choose an organization in the account workspace. Readers can view and test rules. Edit access adds save, order and delete controls. Saving settings affects later work; it does not approve or send letters.

Add or change a rule

In Workflow Rules, choose Add New Rule or Edit beside a rule.

1. Choose Rule type. Do Not Acknowledge stops a matching row. Notifications chooses notification recipients. Create Package chooses how to prepare the row.
2. Enter Rule Condition, using the names under Template fields. For example, [Amount] > 1000. First select a completed CSV under Files → CSV schema if no fields appear.
3. Set the needed Notification Email, Template, Package and Signature. Separate email addresses with commas or semicolons. Use choices from this organization.
4. Choose Save. Test the result before using it for a run.

A condition can contain up to 4,096 characters and 256 tokens. A token is one part of the expression, such as a field, number or operator. Notification lists allow up to 100 addresses. A rule can save without every publishing input, so a saved rule alone does not prove the letter can render.

In Edit Rule, Move up and Move down change the order within that type. The first matching Do Not Acknowledge rule stops the row. Otherwise, the first matching notification rule and first matching package rule can both apply. A rule's signature takes precedence over its package's default signature. Delete asks you to confirm. Changes do not rewrite earlier output.

If another edit changed the rule, close the form, reopen it, and review the current values before saving again.

Test rules

Test rule checks one saved expression. Test all rules shows the selected actions for one row. Enter a JSON object with text values, for example {"Amount":"100","Name":"Sample donor"}. Include the full row: a condition that checks for a missing value can match when you leave out a field.

Field names ignore case and outer spaces. Do not supply the same name twice using different case or spaces. Values keep their original text. A matching rule does not prove its files or delivery settings are ready.

For a whole file, select Data CSV, then Preview Data Results. Template CSV uses the active schema sample. Use Previous CSV choices and More CSV choices to find files on another page. Preview allows up to 1 MiB, 1,000 rows and 100 rules. Preview Summary shows processed, stopped, notification and unmatched counts. Download detailed results saves each row's choices. Tests and previews do not change files, send notifications or start jobs.

Signature and content profiles

Open Signature profiles or Content profiles. Choose Add profile, enter a Name and optional Description, then Save profile. Readers use View. Editors can change or delete a profile; a package or rule that uses it can block deletion.

Profile saves use the version you opened. These local safeguards await Dev acceptance. If a save or delete fails, your draft stays open. Copy any text you need, then choose Reload profiles and reopen the saved profile. Reload asks before discarding changed text. Do not create another profile after an unknown result until you check the list; the first save may have worked. Refresh profiles reads the list without changing anything.

A signature profile stores Image file ID, Image path, Merge field and Placement settings (JSON). Use an existing image from this organization. An image path is a relative file path, not a web address. There is no image-upload control on this form. A content profile stores Content settings (JSON).

Names allow 256 characters and descriptions 4,096. JSON settings can be blank; otherwise they must be valid JSON, up to 65,536 characters. These forms store settings. The full set of supported layout and content options still needs a defined format and rendering checks. Ask your administrator for tested values; saving arbitrary JSON does not prove it changes a letter.

Pause or change automatic checks

Open Settings. Pause publishing stops new automatic jobs; it does not cancel a running job. Resume publishing allows checks to continue. Pending prepared jobs wait while publishing is paused.

Enter a whole number from 1 to 1,440 in Check for new files every (minutes), then choose Save interval. The default is 15 minutes. The page may show a Stored schedule, but that schedule does not run. The worker uses the interval.

If a save fails or its reply is lost, reopen the page and check the saved value before trying again. A pause is not a recall of letters already sent.

Check saved CSV fields

Availability: built locally; Dev checks are pending.

In Workflow Rules, choose Check CSV fields. Rules need attention lists conditions that use fields missing from the selected CSV template. Choose Edit rule to fix one, or View rule if you have read access only.

Use Next page even if the current page has no issues. Each page checks up to 50 rules. Refresh field check checks the current page again. Saving a rule refreshes the open check.

If the check fails, it has no result. Check Files → CSV schema, then try again. This check does not test rule syntax or donor values, and does not send letters. Use Test rule or Preview Data Results to evaluate conditions.

Validate a rule condition

Availability: built locally; Dev checks are pending.

When adding or editing a rule, choose Validate expression under Rule Condition. It checks your text against Template fields. Valid expression means that check passed. Errors show where to look; positions count from zero, so position 0 means the first character.

Changing the text clears the result. Check again after edits. A failed request has no result; you can try again without losing your text.

The check does not save the rule or test donor data. Save still checks the current rule, its actions and your access. Use Test rule or Preview Data Results to evaluate conditions against data.