Alteryx — customer portal or Alteryx Marketplace
The production candidate is not Alteryx Marketplace certified. Alteryx does not document a universal public self-service submission workflow for this package. Do not invent a submission status or publish until an authorized Alteryx representative provides and accepts the current intake process.
1. Prepare one approved release
- Verify written Yanbor LLC authorization for the customer or marketplace channel, DataAI version, Alteryx Designer release, AMP engine, environments, users, and commercial rights.
- Obtain the direct YXI, complete Alteryx production ZIP, and
ARTIFACTS.sha256from the controlled production release. - Recompute SHA-256 for every file and compare it with the manifest. Stop the release for any mismatch.
- Install the YXI in a clean Alteryx Designer 2026.1 test profile. Confirm tool name, icon, category, configuration fields, AMP behavior, help links, license notice, and removal/reinstall behavior.
- Run the separate DataAI Spark smoke test, then run the fictional Alteryx sample through an approved
spark-submitruntime. Verify success, validation failure, Spark failure, timeout, output schema, and log redaction. - Prepare approved listing assets: product name, short/long descriptions, logo/icon, screenshots with fictional data, supported Designer/AMP versions, package version, vendor/support/privacy/license URLs, documentation, release notes, and known limitations.
2A. Fulfill through the Yanbor customer portal
- Create an authenticated, customer-specific entitlement after the commercial agreement/order is complete.
- Upload the immutable YXI, complete ZIP, and checksum manifest to the production-only download area. Keep evaluation files separate.
- Set the entitlement's customer, version, allowed users or organization, start/end dates, authorized environments, and support contact.
- Test with a new customer-equivalent account: sign in, download all authorized files, verify hashes, install the YXI, and open the linked installation and usage guides.
- Send the portal link, exact filenames, hashes, order/license reference, supported environment, installation/usage guides, and support path to the approved customer contact.
- Record customer acceptance and revoke portal access when authorization ends.
2B. Request Alteryx Marketplace publication
- Use Yanbor's Alteryx partner contact or Marketplace contact to request the current custom-tool/YXI publisher onboarding and submission requirements.
- Provide the requested legal company profile, product owner, support process, privacy/license terms, security response contact, tax/payment information if applicable, and proof of rights to the listing assets.
- Confirm whether the Marketplace accepts the exact YXI/tool architecture and whether its policies allow commercial entitlement to be completed outside Marketplace. Follow Alteryx's answer; do not assume.
- Create the Marketplace draft with the approved metadata and compatibility claims. Upload only the specific reviewed YXI/build and any assets requested by the current intake.
- Explain that the Alteryx tool invokes a customer-selected Spark runtime and that the commercial DataAI libraries remain subject to Yanbor authorization. Identify all external prerequisites before download.
- Submit for technical, content, security, and commercial review using the partner workflow supplied by Alteryx. Track every requested change by build/version.
- When Alteryx provides a preview or restricted listing, install from that listing into a clean supported Designer environment and repeat the complete functional test.
- Publish only after written Alteryx acceptance and Yanbor release approval. Replace “candidate” status only when the live listing is verified.
3. Update and withdrawal procedure
- Use a new semantic version and new hashes for every changed YXI or ZIP.
- Retest against each claimed Designer/AMP version and submit Marketplace updates through the same review channel.
- Keep the previous authorized version available for the agreed rollback window, then retire access according to policy.
- For a critical issue, suspend direct fulfillment, notify authorized customers, and ask Alteryx to unlist or replace the affected Marketplace version.