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. API
  2. Examples

Notifications

Describes process for notifying users upon configurable events. For example, if a run of a specific procedure is completed, notify the production manager.

ION boasts a comprehensive notification system seamlessly integrated into the application's processes, offering both native functionality and user-configurable options through ION's API. For instance, imagine you're assigned to handle an approved issue disposition. In such cases, as the assignee, you'll promptly receive a toast notification (if you're actively using the application) and a notification within the designated notifications tab.

Toast notifications elegantly pop out from the upper left-hand corner of the interface, ensuring immediate visibility. ION diligently checks for toast notifications every 30 seconds, so you might experience a brief delay of up to 30 seconds before one appears.

To view all notifications in detail, simply navigate to the notification page by clicking the envelope icon in the top left corner and selecting "SHOW ALL."

When creating automations or integrating external systems, it's essential to keep users informed about pertinent events. ION's robust notification features empower you to do just that. Utilize the dispatchNotification mutation to craft custom notifications. Refer to the following example for guidance:

mutation notification($input:DispatchNotificationInput!){
  dispatchNotification(input: $input){
    response{
      messageId
    }
  }
}

Query Variables:

{
  "input": {
    "userId": 3660,
    "notificationType": "WARNING",
    "description": "Purchase order versioned and PDF file generated. Please refresh.",
    "title": "PO Versioned & PDF Generated",
    "linkText": "This is the link",
    "path": "https://staging.firstresonance.io/"
  }
}

Explanation of Query Variables:

  • userId: Specifies the ID of the user to whom you want to send the notification.

  • notificationType: Defines the type of notification being dispatched. In this case, "WARNING" signifies a critical notification.

  • description: Provides a brief description of the notification's content, informing users about the specific event or action taken.

  • title: Sets the title of the notification, which is displayed prominently in the toast notification.

  • linkText: Indicates the text to be displayed as the link within the notification page, directing users to further details or actions.

  • path: Specifies the URL path users will be directed to when clicking either the toast notification or the notification within the application.

For clarity, here's a brief overview of notification types within ION:

  • EXTERNAL (BLUE): Indicates notifications originating from external systems, typically used for general updates.

  • SIGNOFF (YELLOW): Reserved for notifications requiring user attention or signoff.

  • WARNING (RED): Signals events that may not be favorable, ensuring users are promptly informed of potential issues.

PreviousExamplesNextRuns

Last updated 11 months ago

Was this helpful?