Managing Actions | ION Factory OS 2.0
[This manual has been deprecated.
Read the new manual](https://docs.firstresonance.io/)
For the complete documentation index, see llms.txt. This page is also available as Markdown.
Creating and Managing ION Actions
Objective
This SOP outlines the steps to create, manage, and understand ION Actions within the ION platform, ensuring that users can effectively implement business logic in their organization.
Key Steps
1. Overview of ION Actions
- Ion Actions are programmatic rules and validations that align digital processes with physical outcomes.
- Users can manage these actions through a new interface.
2. Viewing and Managing Actions
- Access the list of all deployed ION Actions in your environment.
- Actions can be enabled or disabled as needed, especially in sandbox environments before production deployment.
3. Enabling and Disabling Actions
- Use multi-select checkboxes next to action IDs to toggle actions on or off.
- To select all actions, click the header of the action table.
4. Searching for Specific Actions
- Use the search function to find actions related to specific keywords (e.g., 'QL' for quality levels).
- Understand the target and trigger of each action.
5. Accessing Action Details
- Click on an action to view details such as creator, last update, and specific action settings.
- Edit action details, including target and title, which affects error messages.
6. Sharing Actions Across Environments
- Use the share functionality to copy the mutation for an action.
- Paste the mutation into the GraphQL editor of another environment to replicate the action.
7. Understanding Context for Actions
- Context is crucial for actions as it determines what data the rule can access.
- Test context queries against different run IDs to ensure proper validation.
8. Editing Action Logic
- Modify the code that defines the validation logic for the action.
- Use the context query to reference attributes needed for comparisons.
For advanced use cases you can also leverage the changes dictionary that is provided each time an ION Action is ran. While you do not have visibility into the exact changes dictionary, this documentation will help you understand the formatting of that dictionary you have to work with.
9. Saving Changes
- Click the save button to apply any changes made to the ION Action.
- Be cautious with changes to avoid unintended updates.
10. Monitoring ION Actions
- Regularly check which ION Actions are enabled and their intended outcomes.
- Stay updated on new features and improvements in the ION Actions interface.
Cautionary Notes
- Always test changes in a sandbox environment before deploying to production.
- Be careful when editing action logic to avoid introducing errors that could block processes.
Tips for Efficiency
- Utilize the search function to quickly locate specific actions.
- Regularly review and document changes made to actions for future reference.
- Familiarize yourself with GraphQL to streamline the sharing and editing process.