Tableau — Tableau Exchange or customer portal
Tableau's published process limits contributed Accelerators on Tableau Exchange to managed Salesforce partners working with a partner account manager. A TWBX cannot securely contain the proprietary JAR entitlement or customer credentials.
1. Separate the two deliverables
- Keep the Exchange workbook self-contained with fictional sample data, explanatory dashboards, supported connection instructions, and no customer data or credentials.
- Keep
dataai-spark-tableau-1.0.0.jarand the core DataAI modules in the authenticated customer fulfillment channel. - State that no DataAI
.tacoconnector is required: Tableau connects through its supported native Spark SQL, Databricks, or database connection to the output tables. - Obtain Yanbor legal, product, security, and branding approval for the public workbook, listing text, screenshots, license link, privacy/support URLs, and claims.
2A. Fulfill through the customer portal
- Obtain
DataAIETL-Tableau-1.0.0.zip, the Spark production ZIP when needed, and the production checksum manifest. - Compare hashes, extract to a clean validation environment, open the TWBX in a supported Tableau Desktop version, and run the DataAI Spark/Tableau adapter smoke tests.
- Create a customer-specific authenticated entitlement after the commercial agreement/order is complete.
- Upload the immutable ZIP/checksum files and set customer, version, users, environments, entitlement dates, and support owner.
- Test a clean customer download, hash match, Spark library installation, output generation, workbook opening, and replacement of the fictional data source with the governed customer source.
- Send the portal link, filenames/hashes, order/license reference, installation/usage guides, supported versions, output contract, and support path.
2B. Submit the Accelerator to Tableau Exchange
- Confirm that Yanbor LLC is a managed Salesforce partner eligible to contribute Tableau Accelerators. If it is not, contact Salesforce/Tableau partner channels; do not represent the workbook as Exchange-submittable until eligibility is confirmed.
- Work with the assigned partner account manager to obtain the current Accelerator proposal, design, quality, localization, licensing, and submission requirements.
- Validate the workbook against those requirements: clear business scenario, coherent dashboard flow, meaningful fictional data, editable connections, no secrets, no broken links, acceptable performance, accessible titles, and approved Yanbor branding.
- Package the final reviewed workbook as TWBX. Reopen it on a clean machine and confirm that the embedded fictional data renders without access to Yanbor or customer infrastructure.
- Prepare the listing name, short/long descriptions, use case, industries, required Tableau versions, screenshots, setup instructions, public legal/privacy/support URLs, and explicit prerequisites for separately licensed DataAI ETL.
- Submit the proposal and build through the channel specified by the partner account manager. Track reviewer feedback by workbook version and preserve the exact submitted hash.
- When a preview is available, acquire it using a clean Tableau identity and test the complete workbook flow plus the link to commercial fulfillment.
- Publish only after Tableau/Salesforce approval and Yanbor release approval. Verify the live Exchange page and download before announcing availability.
3. If Exchange eligibility is unavailable
- Continue controlled fulfillment through the customer portal.
- Tableau Public may be used only for an approved public workbook with fictional data; it is not a channel for proprietary JARs or commercial entitlement.
- Do not use “Tableau Exchange,” “Exchange approved,” or equivalent wording until the live listing exists.
4. Maintain releases
- Use a new semantic version/hash for changed proprietary packages and a traceable workbook revision for every TWBX update.
- Retest extracts, live connections, field mapping, refresh, dashboard filters, and supported Tableau versions.
- Submit Exchange changes through the partner review path and revoke portal access when customer authorization ends.