ION Factory OS
  • Welcome to ION
  • Features
    • Procedures
      • Steps
        • Content
        • Datagrid
        • Fields
        • Attributes
      • Dependencies
      • Part-Procedure Relationship
      • Attributes
      • Standard Steps
      • Installation Requirements (Beta)
      • Nested Steps and Nested Standard Steps
      • Procedure Best Practices
    • Runs
      • Run Execution Overview
      • Runs And Step States
      • Batching Runs
        • Batching 2.0 Changes
      • Workcenter execution
      • Split Inventory on a Run
      • Redlines
      • Export run data
      • Scheduling runs
      • Time Tracking
      • Attributes
      • Outside Processing
      • Runs Best Practices
    • Parts Library
      • As-built Bill of Materials (aBOM)
        • Editing aBOM build requirements
        • aBOM Beta Changes
          • aBOM actions for developers
      • Inventory
        • Inventory status
        • Inventory splitting
        • Inventory merging
        • Inventory scrapping
        • Kitting
        • Inventory Movement Automations
      • Manufacturing bill of materials (mBOM)
        • mBOM versions
        • Made on Assembly (MOA)
        • Part Substitutes
        • Reference designators
      • Part Attributes
      • Part revision interchangeability
      • Supplier Part Numbers & Purchase Unit Conversions
    • Kitting and Inventory Fulfilment
      • Kit Statuses and Workflows
      • Inventory requests
      • Kitting and runs
      • Fulfilling Multiple Kits
      • Kanban Kitting
    • Purchasing
      • Purchase Orders
        • Types of Purchases
        • Purchase Order Approvals
        • Purchase Order FAQs
        • Supplier Part Numbers & Unit Conversions
        • PO Requirements, Terms, and Quality Clauses
        • PO lines editability changes
      • Receiving/Inspection
      • Outside Processing
      • Consigned Parts
    • Barcode Labels
      • Templating
        • ION barcode minimum sizes
        • Sample templates
      • Printing
        • Configuring Zebra Browser Print
        • Server Based Barcode Printing (PrintNode)
      • Scanning
        • Scan barcodes from other systems
    • Quality
      • Issues
      • Further Actions - CAPA
      • Issues States, Dispositions, and Resolutions
      • Quality Best Practices
    • Tools
    • Locations
    • Attributes
    • Labels
      • Deleting labels
    • Notifications
    • Search
    • Settings
      • Role based access control
        • Full Glossary of ION Permissions
    • ION Actions
      • ION Actions examples for Quality
      • ION Actions examples for Runs and Procedures
      • ION ACTIONS examples for Supply Chain
  • Analytics
    • Inventory valuation
    • Part impact analysis
    • Users, Roles, Teams
    • Analytics FAQ
    • Data Connector
    • Data Products
  • Plans and Autoplan
    • Autoplan
    • Autoplan glossary
    • Preparing to use Autoplan
    • Clear to build reporting
    • Running Autoplan on a schedule
    • Firm and blocked plan items
    • Location constraints
    • Autoplan suggested suppliers and procedures
    • Reorder point
    • Plan input serial numbers
    • Applying a calendar
    • Plan Reservations
    • Independent schedules
    • Drive demand from kits
    • Drive demand below buy parts configuration
    • Group plan items with the same date
    • Manualy Changing Autoplan Status
  • API
    • How to create an App with ION
    • Access Tokens
    • About GraphQL
    • Interactive API explorer
    • API Keys
    • Examples
      • Notifications
      • Runs
      • Automatically updating fields in runs
      • Parts and Part Revisioning
      • mBOMs
      • Part Inventory and Kitting
      • aBOM (As-built Bill of Materials)
      • Edit time-tracking session data
    • Changelog
    • Webhooks
    • Pagination
  • Automations
    • Auto-checkout of Run Steps
    • Auto-Consumption of Lineside Inventory
    • Automatically Send Purchases to Suppliers
    • Set Close by Run Step on Issue Creation
    • Intent Management / Grade / Tier / Pedigree
      • Data Imprinting
      • ION Actions for Intent
    • Auto-Update mBOM Revision on Part Revision Update
    • Auto-approve part-procedure relationships
    • Purchase Order PDF and Versions
    • Auto Populate PO Line Attributes
    • Imprint Attributes from One Object to Another on a Desired Event
  • Integrations
    • Deploying Integrations and Automations
    • Arena
    • Cofactr
    • Datum
    • Duro
    • NetSuite
      • Purchasing in NetSuite, Receiving in ION
      • Work Order/Assembly Builds
    • Procurable
    • PDF Generator
    • Ramp
    • Silkline Integration
    • Slack
    • Smartsheet
    • SOLIDWORKS
    • Teamcenter
    • Integrating with ERP Best Practices
  • Training
    • Standard Operating Procedures
      • Cycle Counting
      • Tool Utilization
    • Guided Flows
    • ION Sandbox
    • Chat Support for ION
  • Troubleshooting
    • Resetting your password
    • Resetting your Multi-Factor Authentication
    • You have no roles... error
  • Changelog
  • Adminstration
    • Security
      • Backups and Security FAQ
      • Single Sign-On (SSO)
        • Okta SAML connection setup
      • Export Control
      • Report Generator Disclaimer
    • Browser and Device Compatibility
    • Authentication
      • My company is new to ION, logging in for the first time.
      • I'm told I'm not authorized to access the application
      • My account has been deactivated
    • Login Page
  • Tickets Portal
Powered by GitBook
On this page

Was this helpful?

  1. Automations

Purchase Order PDF and Versions

PreviousAuto-approve part-procedure relationshipsNextAuto Populate PO Line Attributes

Last updated 4 days ago

Was this helpful?

Purchase Order Versions:

Use ION's prebuilt marketplace automation to manage versions.

Every time a purchase order is moved to either "APPROVED" or "ORDERED" (configurable) the purchase order "Version" attribute will be incremented. When you move a purchase order to the "APPROVED" or "ORDERED" status a PDF/XLS of the purchase order is generated and uploaded to the file attachments for that purchase order. The generated document will be titled with the version attribute at the time of order.

DISCLAIMER: This automation utilizes Carbone for PDF generation. Please see Report Generator Disclaimer for more information.

PDF Generator

This automation can use any one of the following 3 implementations of Carbone:

  1. First Resonance's PDF Generator (default)

  2. Your PDF Generator account (i.e. Carbone) account

  3. On-premise implementation of your PDF Generator

Setup:

  1. Navigate to the integrations page via the arrows on the left-hand side

  2. Search for and locate the integration called "Purchase Order PDF"

  3. Select the integration and click the Add Instance button

  4. Optionally modify the Name of the automation. This is helpful if you are deploying multiple instances of the same automation (i.e., one is pointing to staging and one is pointing to production)

  5. Configure the integration with your ion-api credentials and select the environment. See API Keys for more information on how to get your credentials.

  6. Select the purchase order status that will trigger the creation of the PDF. You can choose either APPROVED or ORDERED

  7. If you would like to use an on premise installation of your PDF Generator, you must set the On-Prem Carbone setting to true and specify the On-Prem Carbone URL. The default is false which will use the standard cloud implementation of Carbone.

  8. Specify the Carbone TemplateId to use to generate the PDF. The default template id will use an out-of-the-box generalized purchase order template. Contact your customer success manager if you would like to use a customized purchase order template.

  9. Specify the type of file to generate. The default is pdf. You can also opt to generate xls spreadsheets.

  10. Specify the Carbone API Key and Carbone Version. If you are not using your own PDF Generator account, then use the default values.

  11. Specify the Organization Name. This value is used in naming the document that is generated.

  12. Optionally, enable the Send Notification setting if you would like a notification to be when whenever the PO is versioned and/or a document is generated.

  13. Press Finish