Actions

Factorial is a programmable system, letting organizations tailor Factorial to their use case.

Factorial's behavior can be modified using Actions. Actions can do things like fire HTTP requests to external services, validate a business rule before allowing an operation to proceed, or kick off another operation within Factorial. For example a work order can be configured to modify a custom field on an inventory line automatically.

Actions are evaluated atomically within the request, so if any part of the request fails, the action rolls back (with the exception of HTTP requests, which clearly cannot be unsent). This maintains data integrity even with complex rules.

Subscribable Entities

Actions can subscribe to lifecycle events from the following entities. The context passed to an action depends on the event.

Entity	Example events	Available context
Inventory	Created, received, installed, uninstalled, split, merged, moved, consumed, scrapped, or adjusted	Part definition, quantity, location, parent and child inventory, kits, work orders, and operator
Work orders	Created, started, held, resumed, completed, or canceled	Procedure, steps, built inventory, kitted inventory, assigned operators, and schedule
Steps	Started, held, resumed, completed, or field updated	Parent work order, parent inventory, assigned inventory, captured field values, and operator
Users	Invited, activated, deactivated, added to a team, or role changed	User, organization, teams, roles, and initiating user
Comments	Created, edited, deleted, or mentioned	Comment, author, mentioned users, and the entity the comment belongs to

More entities and events are coming soon.

Actions

• Send HTTP request (for example send message to Slack)
• Create entities (inventory, work orders, comments, etc)
• Modify custom fields on inventory, work orders, comments, steps, etc
• Leave comment
• Send email