Iris API functions

This section documents all host functions available in Iris Jyro scripts. These functions extend the Jyro scripting language with Iris-specific capabilities for managing organizations, persons, facets, secrets, notifications, and more.

Function Categories

Organizations

Functions for managing organization entities:

Persons

Functions for managing person entities:

Facets

Functions for managing facet definitions and instances:

Fields

Functions for managing field definitions and instances:

Hybrid Lists

Functions for managing hybrid list definitions and instances:

Entitlements

Functions for managing entitlement definitions and granting entitlements to organizations:

Roles

Functions for managing person roles:

Secrets

Functions for managing encrypted secrets:

Notepads

Functions for persisting and retrieving script output data:

Notifications

Functions for real-time notifications via SignalR:

Email

Functions for sending emails:

Templating

Functions for template rendering:

Articles

Functions for news/article management:

Data Import

Functions for reading external data files:

File Generation

Functions for generating files:

Blob Storage

Functions for persistent file storage using Azure Blob Storage. Requires tenant configuration (see Blob Storage Setup):

External Blob Storage

Functions for working with external Azure Blob Storage accounts (not the tenant’s configured storage):

File Handles

Functions for working with downloaded file handles:

PDF Processing

Functions for extracting data from PDF documents:

SQL Database

Functions for querying external SQL Server databases:

SharePoint Integration

Functions for uploading files and creating folders in SharePoint Online:

Context

Functions for accessing current execution context:

Audit

Functions for accessing audit trail data:

Utility

Core utility functions:

  • Log - Write to application logs
  • CancelAction - Cancel current operation (Before hooks only)

Usage Context

These functions are available in three execution contexts:

  1. Event Hooks - Scripts triggered by domain events (BeforeOrganizationCreated, AfterPersonUpdated, etc.)
  2. Dynamic Endpoints - Custom API endpoints powered by Jyro scripts
  3. Ad-hoc Scripts - Administrative scripts executed on-demand

For detailed information about the Data object structure passed to scripts in each context, see the Data Context Reference.

Jyro Syntax Reminder

Remember that Jyro uses its own syntax, not JavaScript:

# Conditionals
if condition then
    # code
end

# Loops
foreach item in items do
    # code
end

# Boolean operators
if isActive and age > 18 then
    # code
end

See the Jyro documentation for complete language reference.

Best Practices

  1. Always validate inputs - Check for null/empty values before using
  2. Use appropriate log levels - Debug, Information, Warning, Error
  3. Handle errors gracefully - Check return values and log failures
  4. Use CancelAction wisely - Only in Before hooks, with clear reason
  5. Keep scripts simple - Complex logic belongs in the domain layer

Back to top

Copyright © Globetrotter. All rights reserved.