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
      • 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
    • Quickbooks
    • Ramp
    • Silkline Integration
    • Slack
    • Smartsheet
    • SOLIDWORKS
    • Teamcenter
  • 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

Set Close by Run Step on Issue Creation

Automatically set a run step in the "resolve issue by step" field on ION Issues. Configurable as either the next run step or the last step in the run.

PreviousAutomatically Send Purchases to SuppliersNextIntent Management / Grade / Tier / Pedigree

Last updated 1 year ago

Was this helpful?

TERMS TO KNOW:

Term: Run Step ID & "issue close by step"

Definition: The run step that the issue resolve by will be set to.

USE CASE:

Issues in ION are a key piece to any manufacturing systems ability to trace and provide quality product. The feedback that results from issue resolutions drives continuous improvement activities.

This automation ensures that issues are closed out either before runs continue with subsequent run steps or are completed in full. This leads to better issue resolution rates, faster root causing actions, and will force that an issue is resolved / will be noticed before teams lose context of the issue. The automation will be triggered when an issue is created on a run. Upon deploying this automation, you have the choice between two configurations. For setting the run step to resolve the issue as the next step choose the next step configuration. For setting the run step to resolve the issue as the last step in the run choose the last step configuration. See the details below for an example of these two deployments.

CONFIGURATIONS:

"Next Step" Configuration: This style of configurations will assign the close issue by Run Step ID to the next step. Example: If the issue is created on step 2 of 5, and step 3 is in state CANCELED, the Run Step ID assigned will be that from step 4. If all subsequent run steps are in state CANCELED then a new run step will be created in status REDLINE.

"Last Step" Configuration: This configuration will assign the issue close by Run Step ID as the last step in the run. If the last step in the run is in CANCELED state then a new run step will be created in status REDLINE.

PROCESS:

  1. In ION, navigate to integrations, and go to the marketplace. Activate the "Set Close by on Issue Creation" integration. Go to the configuration.

  2. Choose your configuration option, "Next Step" or "Last Step".

  3. Complete the deployment by clicking finish!

VERIFICATION:

Where can I view the resultant close (resolve) by step?

See the example bellow where on the right hand side of the issue page there is a section titled "Resolve issue by step". Clicking on this Run Step will also populate the Run Step ID in your URL as follows.

Run Step ID that issue must be closed by: 37441

Follow prompts to input your API credentials, clientId and clientSecret. If you need to setup your .

API credentials look here
Configurations Visual
Result of the "Next Step Configuration" being used where an issue on the third step get set to be resolved by the fourth step.