Overview
PowerUX’s AI-Generated Flows feature allows you to create sophisticated UX flows using natural language descriptions. Simply describe what you want your flow to do in plain English, and our generative AI will create the complete flow with all the necessary action steps, logic, and configurations.Why Use AI-Generated Flows?
Speed
Simplicity
Accuracy
Learning Tool
Getting Started with AI Flows
Step 1: Start Creating a Flow
From the UX Flows list, click + New Flow to open the flow creation dialog.Step 2: Select Flow Type
Choose the type of flow you want to create:- Form - For model-driven app forms
- Command Bar - For ribbon buttons
- Function - For reusable functions

Step 3: Choose “Create with AI”
In the flow properties screen, you’ll see several options. Click on Create with AI - the first option with the sparkles icon.
Step 4: Describe Your Flow
A text area will appear asking you to “Describe Your Flow in Plain Text”. This is where the magic happens!
- When it should happen (trigger)
- What it should do (actions)
- Conditions if any (logic)
Step 5: Configure Flow Properties
After describing your flow, set the standard flow properties:Step 6: Create Your Flow
Click the Create button. PowerUX AI will:- Analyze your natural language description
- Determine the required action steps
- Configure the proper logic and conditions
- Generate a complete, ready-to-use flow
Writing Effective AI Prompts
The quality of your AI-generated flow depends on how clearly you describe your requirements. Follow these best practices:Be Specific About Triggers
Good Trigger Descriptions
Good Trigger Descriptions
- “When the form loads”
- “When the user clicks the Save button”
- “When the Status field changes”
- “On form load, after data is loaded”
Avoid Vague Triggers
Avoid Vague Triggers
- “Sometimes do this”
- “When needed”
- “Usually when…”
Describe Clear Actions
Good Action Descriptions
Good Action Descriptions
- “Show a notification with the message ‘Record saved successfully’”
- “Hide the Credit Limit field”
- “Set the Status field to ‘Active’”
Avoid Ambiguous Actions
Avoid Ambiguous Actions
- “Do something with the field”
- “Update stuff”
- “Handle the record”
Include Conditions Clearly
Good Condition Descriptions
Good Condition Descriptions
- “If the Account Type equals ‘Enterprise’”
- “When the record name contains ‘Test’”
- “If the Annual Revenue is greater than 1000000”
- “When the Status is not ‘Active’ and Priority is ‘High’”
Avoid Unclear Conditions
Avoid Unclear Conditions
- “If it’s the right type”
- “When appropriate”
- “If needed”
Example AI Prompts
Simple Notification
Prompt:- Form OnLoad trigger
- Condition checking if Name contains “Test”
- Form notification action with an appropriate message
Field Visibility Control
Prompt:- Field OnChange trigger for Account Type
- Branching condition based on field value
- Show/Hide control actions for Credit Limit field
Data Validation
Prompt:- Form OnSave trigger
- Email validation logic
- Error display on field
- Cancel save action if invalid
Automated Record Creation
Prompt:- Form OnSave trigger
- Condition checking Status change
- Create Record action with proper field mappings
- Success notification
Complex Business Logic
Prompt:- Form OnLoad trigger
- Multiple branching conditions based on user roles
- Field visibility controls for each scenario
- Form mode changes
- Conditional notifications
Advanced AI Prompt Techniques
Use Context from Multiple Fields
Prompt:Specify Complex Workflows
Prompt:Reviewing and Refining AI-Generated Flows
After AI generates your flow:Review the Flow
Test the Logic
Refine if Needed
Add Details
Publish
Tips for Best Results
Start Simple, Then Iterate
Start Simple, Then Iterate
Use Field Names Correctly
Use Field Names Correctly
Be Sequential
Be Sequential
Specify User Experience
Specify User Experience
Common Use Cases
Conditional Field Visibility
Dynamic Field Requirements
Calculated Fields
User Notifications
Record Status Management
Troubleshooting
Flow doesn't do what I expected
Flow doesn't do what I expected
Some fields are not found
Some fields are not found
Logic is too simple or too complex
Logic is too simple or too complex
Need to combine multiple scenarios
Need to combine multiple scenarios
Comparing AI vs Manual Creation
Create with AI
- Quick prototyping
- Common scenarios
- Learning PowerUX
- Time-sensitive projects
Manual Creation
- Very specific requirements
- Complex custom logic
- Edge case handling
- Fine-tuned optimization
AI Generation Limits
- Complex multi-branch logic may need manual refinement
- Very specific custom requirements might need manual implementation
- Integration with external systems may require additional configuration
- Some advanced scenarios are better built manually
Privacy and Data
- Your natural language descriptions are processed securely
- No sensitive data from your environment is stored
- AI learns from patterns, not your specific data
- All standard PowerUX privacy policies apply
Best Practices Summary
- ✅ Write clear, specific descriptions
- ✅ Use proper field names
- ✅ Mention triggers explicitly
- ✅ Describe desired user experience
- ✅ Review and refine as needed
- ❌ Vague or ambiguous descriptions
- ❌ Assuming AI knows your custom fields
- ❌ Overly complex single prompts
- ❌ Expecting perfection without review
- ❌ Using technical jargon unnecessarily
Related Resources
Reusable Functions
Action Steps
Triggers
FAQs
How accurate is the AI?
How accurate is the AI?
Can I edit AI-generated flows?
Can I edit AI-generated flows?
What if the AI doesn't understand my description?
What if the AI doesn't understand my description?
Is there a cost for using AI generation?
Is there a cost for using AI generation?
Can AI create Functions too?
Can AI create Functions too?

