Before getting started, ensure:

• Infowise Ultimate Forms is installed and activated on your SharePoint list or library.
• You have sufficient design permissions.
• You are working in a Modern SharePoint interface for full compatibility with new features.

Step 1: Open the Action Designer

1. Go to your SharePoint list or library.
2. Click Design from the command bar.
3. Select Actions, then click New Action.

Step 2: Add a new Action and Choose an Action Type

    1. Click Add new action

    2. Choose an Action Type

Available action types include:

• Update List Item
• Create List Item
• Delete list item
• Copy list item
• Manage attachments
• Create list
• Create site
• Send Email
• Run workflow
• Run DB stored procedure
• Call Application or service
• Manage Permissions
• Manage Active Directory
• Print list items 
• Calculate summary
• Run PowerShell 
• Generate Associated Tasks
• Manage Exchange 
• Manage Teams
• Execute Import
• Action Group

Full list of types: Action Types Overview

Step 3: Set the Trigger

Specify when the action should run:

• On item add, edit, or delete
• Manual execution via Run Action panel
• Timer-based(e.g., daily, weekly)

Step 4: Define Action Logic

Configure the action:

• Set values for fields using tokens like [Status], [Today], or [Priority]
• Create new items in other lists
• Set calendar appointments or Teams meetings
• Assign or remove permissions

Tip: Use dynamic field values and expressions to make actions smarter.

Step 5: Apply Conditions (Optional)

Use conditional logic to control when an action should run:

• Example: Only run when [Status] = "Pending" and [Due Date] < [Today]
• Combine with AND/OR logic
• Nest condition groups for complex logic

Step 6: Save & Test

1. Save the action.
2. Trigger it via form entry, edit, or the Run Action panel (for manual).

Tips & Best Practices

• Use Action Groups to chain multiple logic steps together.
• Add manual buttons to forms to allow users to run actions on demand.
• Combine with Dynamic Rules to show/hide form sections based on data.
• Test in a dev list before applying to production.
• Always test in a development list or test site first—check Action History for logs and troubleshooting.