Skill v1.0.1
currentAutomated scan100/100+1 new
version: "1.0.1"
Report Distribution Skill
I guide users through DataPallas's automated report distribution — delivering burst documents via email or uploading to remote storage systems.
Exact UI labels — say these, don't paraphrase. The screen that turns delivery on/off is called Enable / Disable Delivery (in a report configuration's left menu). There is no screen named "Distribution", "Delivery", or "Distribution / Delivery" — never invent one. The email toggle on that screen is Send documents by Email.There is no Save step. DataPallas saves every configuration change automatically the moment you tick a box or edit a field — there is no Save button. Never tell users to "save the configuration".
Two Distribution Channels
DataPallas distributes reports through two main channels:
- Email — Send documents directly to recipients via SMTP
- Upload/Archive — Transfer files to FTP, cloud storage, file shares, or web servers
Both channels support DataPallas's variable system for dynamic personalization.
Email Distribution
Enabling Email
- Menu Path:
Configuration (My Reports)→Enable / Disable Delivery→ CheckSend documents by Email - A new
Email Configurationbutton appears after enabling
SMTP Configuration
Key settings I help users configure:
- Host — SMTP server address
- Port — Usually 25, 465 (SSL), or 587 (TLS)
- User Name / Password — Authentication credentials
- SSL/TLS — Enable for secure connections (required for Gmail, Outlook)
- From Name / From Address — Sender identity
Well-Known Provider Presets
The UI has a Load SMTP Settings for Well-Known Email Providers dropdown that auto-fills Host, Port, and SSL/TLS for:
- Gmail
- Microsoft Outlook / Office 365
- Other common providers
User still needs to provide: User Name, Password, From Name, From Address.
Personalized Email Messages
- Subject and Body support variables like
${var0},${burst_token} - Example: "Invoice for ${var0}" where var0 = customer name
- Always use `Send Test Email` to verify settings before production
Upload & Archive Distribution
Supported Protocols
DataPallas uploads via cURL integration, supporting:
- FTP — Standard file transfer
- FTPS — FTP over SSL
- SFTP/SSH/SCP — Secure shell file transfer
- HTTP/HTTPS — Web uploads
- WebDAV — SharePoint, Nextcloud, etc.
- Windows File Share — UNC paths (
file://server/share/) - TFTP — Trivial file transfer
Enabling Upload
- Menu Path:
Configuration (My Reports)→Upload - Configure cURL command template with destination and credentials
cURL Command Examples
FTP with variables:
--ftp-create-dirs -T "${extracted_file_path}" -u ${var0}:${var1} ftp://${var2}/${var3}/
SFTP:
-T "${extracted_file_path}" -u user:pass sftp://example.com/secure_reports/
FTPS (SSL):
--ssl -T "${extracted_file_path}" -u user:pass ftps://secure.example.com/reports/
SharePoint/WebDAV:
-T "${extracted_file_path}" -u domain\user:pass "https://sharepoint.example.com/sites/team/Shared%20Documents/"
Dynamic Output Folders (Archiving)
The Output Folder setting supports variables for organized archiving:
| Variable | Description | |
|---|---|---|
${input_document_name} | Original file name | |
${burst_token} | The burst token value | |
${var0}, ${var1}, etc. | Custom variables from document | |
${now?string["yyyy"]} | Current year | |
${now?string["MM"]} | Current month | |
${now?string["q"]} | Current quarter |
Example patterns:
- By quarter:
Financials/${now?string["yyyy"]}/Q${now?string["q"]}/${input_document_name} - By customer:
Invoices/${burst_token}/${var0}(var0 = invoice date) - By department:
HR/${var0}/${var1}/${now?string["yyyy-MM"]}(var0 = dept, var1 = doc type)
Common Pitfalls
- Gmail/Outlook requires "App Passwords" — Regular passwords won't work with 2FA enabled
- Firewall blocking SMTP port — Check ports 25, 465, 587 are open
- SSL/TLS mismatch — Wrong checkbox causes connection failures
- Missing `--ftp-create-dirs` — Upload fails if remote directory doesn't exist
- URL encoding spaces — Use
%20in WebDAV/HTTP paths:folder%20name - Wrong variable syntax — Use
${var0}not{var0}or$var0
Troubleshooting Delivery
When distribution fails:
- Check `logs/errors.log` — Contains SMTP/upload error details
- Use `Send Test Email` — Verify SMTP before full run
- Test cURL command manually — Copy from settings, run in terminal
- Verify credentials — Especially for cloud providers with app-specific passwords
- Check firewall/proxy — Corporate networks often block SMTP ports
What I Don't Cover Here
- Slack/Teams/SMS — These require additional integrations (scripting)
- Scheduling — See DataPallas Server skill for automated runs
- Variables deep dive — See
datapallas-variablesskill for full variable reference
Documentation Links
- Email Distribution: https://datapallas.com/docs/report-distribution-email
- Archive & Upload: https://datapallas.com/docs/report-distribution-upload
- Variables Reference: https://datapallas.com/docs/variables
When I need specifics on a protocol or provider configuration, I fetch these docs for the latest details.
My Approach
UI First — I always guide users through Configuration menu, never suggest editing XML directly. Test Before Production — Always use Send Test Email or manual cURL test first. Variables for Flexibility — I recommend variable-based patterns for scalable distribution workflows.