App Management Overview

Article Type: Concept
Audience: App Administrators (New), Application Designers, Partners
Module: App Management
Applies to Versions: All Versions

1. Overview

App Management provides centralized configuration and operational control for Fuuz applications, enabling administrators to customize behavior, automate processes, and manage system-generated features without writing code. This section of the App Admin menu consolidates five essential capabilities: application-wide Settings that control user experience and display formats, flexible Configurations for business logic parameters, Flow Schedules for time-based automation, Notifications for event-driven communications, and Sequences for automatic number generation. Together, these features empower App Administrators to tailor applications to specific business requirements, maintain operational consistency, and reduce manual administrative overhead.

2. Architecture & Core Concepts

Key Principles

• Configuration Over Code: App Management features provide declarative configuration interfaces that eliminate the need for custom programming for common administrative tasks.
• Per-Application Scope: All configurations are specific to individual applications, enabling different settings for different business domains within the same Fuuz instance.
• Per-Environment Isolation: Build, QA, and production environments maintain separate configurations, supporting safe development and testing workflows.
• Package-Based Migration: Most App Management configurations can be packaged and migrated between environments, ensuring consistency while maintaining environment-specific overrides where needed.
• Role-Based Access: Access to App Management features is controlled through the platform's policy-based permission system, enabling granular delegation of administrative responsibilities.
• Audit Trail: Changes to App Management configurations are tracked in Data Change History, providing accountability and change management capabilities.

Feature Categories

App Management features can be categorized by their primary purpose:

3. Feature Summaries

Settings

Purpose: Control application-wide display formats, localization, and user interface preferences with a three-tier inheritance system.

Key Capabilities:

• Configure date, time, and number formats using Moment.js and Numeral.js libraries
• Set language, currency, timezone, and regional preferences
• Customize theme colors (primary, accent, background)
• Manage measurement units (metric vs. imperial)
• Three-tier inheritance: User Settings → Role Settings → Default Settings

Common Use Cases:

• Multi-national operations requiring regional date/time/currency formats per location
• Role-based formatting (executives see abbreviated numbers, operators see full precision)
• Department-specific color themes for visual identification
• User preference override allowing personal customization within corporate standards

Who Manages: App Admins set defaults and role-level settings. End users can modify their own user-level settings via Avatar → Profile.

Configurations

Purpose: Store and validate business parameters, application-specific data structures, and configuration values that drive custom logic without code changes.

Key Capabilities:

• Define JSON Schema (Config Schema) that validates configuration data structure
• Store actual configuration values (Config Json) conforming to schema
• Support complex types: strings, numbers, booleans, arrays, objects, table references
• Use inputProps with table references for validated dropdown selections from data models
• Organize configurations into Modules and Module Groups for logical packaging
• Access via GraphQL queries in screens, flows, and integrations

Common Use Cases:

• Mobile menu structures defining screen navigation hierarchies
• Business thresholds (approval limits, alert levels, timeout values)
• Integration endpoints and API keys per environment
• Feature flags for controlled rollout and A/B testing
• Holiday calendars and business rules referenced by flows
• Production changes without code deployment

Who Manages: App Admins and Developers define schemas. App Admins update configuration values in production without code changes.

Flow Schedules

Purpose: Automate data flow execution on time-based schedules using flexible patterns including cron expressions, calendar rules, and interval timers.

Key Capabilities:

• One Schedule supports multiple Frequencies, each with independent timing patterns
• Four schedule types: TIME (intervals), DAILY (day-of-week), MONTHLY (day-of-month), CRON (expressions)
• Calendar-style UI that generates cron expressions or manual cron entry
• Per-frequency timezone configuration with automatic DST handling via Moment.js
• Input Schema validation for payload data passed to flow executions
• Async execution with flow-level parallelism controls
• Monitoring via Status Messages, Last Execution, Estimated Next Execution

Common Use Cases:

• Weekday-only order synchronization (Monday-Friday at 6:00 AM)
• Business-hours-only API polling (every hour 9:30 AM - 4:00 PM)
• Monthly report generation (1st of month at midnight)
• Multi-timezone operations (8:00 AM local time per plant location)
• Batch processing with variable intervals (15 min during business hours, hourly overnight)
• Data synchronization with external systems on schedules

Who Manages: App Admins and Developers create schedules. Web Access users with explicit policies can also manage schedules. All executions run as "system" user.

Notifications

Purpose: Configure event-driven notification channels and subscription rules for alerting users about system events, data changes, and business conditions.

Key Capabilities:

• Define notification channels (email, webhook, in-app notifications)
• Configure subscription rules based on data model events
• Support role-based and user-based notification routing
• Template-based message formatting with dynamic data injection
• Integration with flow-generated notifications for custom alerts

Common Use Cases:

• Alert approvers when work orders require approval
• Notify quality team when non-conformances are created
• Send daily summaries of production metrics to management
• Alert IT when integration errors occur
• Notify users when assigned tasks are updated

Who Manages: App Admins configure notification channels and subscription rules.

Sequences

Purpose: Generate system-managed unique identifiers automatically using configurable patterns with prefixes, suffixes, increments, and zero-padding.

Key Capabilities:

• Two types: String (with prefix/suffix) and Int (numeric only)
• Configurable increment values (1 for consecutive, 10 for process steps, etc.)
• Zero-padding for consistent digit counts and proper sorting
• Unique constraints trigger separate sequences per data model relation key
• Integration with data model field defaults, flows, and imports
• Set sequence value for migration scenarios or reset for testing

Common Use Cases:

• Work order numbers: WO-0001, WO-0002, WO-0003
• Non-conformance reports: NCR-16, NCR-17, NCR-18
• Purchase orders: PO-2025-0001, PO-2025-0002
• Process routing steps per product: Product A gets 10, 20, 30; Product B gets 10, 20, 30 (separate sequences)
• Serial numbers with high starting values after migration
• Lot numbers combining prefix, date, and sequence

Who Manages: App Admins and Developers create sequences. Web Access users with RBAC policies can also manage sequences.

4. Navigation and Access

App Management features are accessed through the App Admin left navigation menu:

Menu Structure

App Admin Menu
├── App Admin Home
├── Access Control
│   ├── Access Requests
│   ├── App Users
│   ├── Roles
│   ├── Policy Groups
│   └── Policies
├── Data Management
│   ├── Data Changes
│   ├── Custom Fields
│   ├── API Tree Viewer
│   └── Import Data
└── App Management
    ├── Settings
    ├── Configurations
    ├── Flow Schedules
    ├── Notifications
    └── Sequences

Access Requirements

Note: RBAC (Role-Based Access Control) policies provide granular permissions including view-only or edit access. Configure policies in Access Control > Policies and assign to roles.

5. Decision Framework: Choosing the Right Feature

App Management features overlap in some capabilities. Use this decision framework to select the most appropriate feature:

Settings vs. Configurations

Configurations vs. Data Models

Sequences vs. Custom Data Models

6. Getting Started Guide for New App Admins

Recommended Configuration Sequence

For new applications, configure App Management features in this order:

Phase 1: User Experience Foundation (Settings)

1. Review and configure Default Settings for organizational standards
2. Set appropriate date/time formats for primary user base
3. Configure currency and number formats for financial data display
4. Set default timezone for application
5. Optionally configure role-specific settings for different user groups

Phase 2: Data Generation Setup (Sequences)

1. Identify entities requiring unique identifiers (work orders, NCRs, POs, etc.)
2. Create sequences with appropriate naming conventions
3. Configure prefix/suffix patterns matching business requirements
4. Set zero-padding for proper sorting behavior
5. Link sequences to data model field defaults
6. Test sequence generation in build environment before production

Phase 3: Business Logic Parameters (Configurations)

1. Identify application-specific parameters that may change without code updates
2. Work with developers to define Config Schemas with proper validation
3. Create configurations and populate Config Json values
4. Test configuration access from screens and flows
5. Document configuration purpose and schema for future administrators

Phase 4: Automation (Flow Schedules)

1. Identify processes requiring time-based automation
2. Ensure Data Flows are developed and tested manually first
3. Create schedules with appropriate Input Schemas for payload validation
4. Configure frequencies with timezone considerations
5. Test in non-production environment before enabling in production
6. Monitor execution via Data Flow Metrics Dashboard

Phase 5: Communications (Notifications)

1. Define notification channels (email, webhooks, in-app)
2. Configure subscription rules for data model events
3. Create notification templates with dynamic data
4. Test notification delivery in non-production first
5. Monitor notification logs for delivery issues

Common Pitfalls to Avoid

• Mixing Imported and Generated Sequences: Don't use Fuuz Sequences for data imported from external systems with different schemas - use custom data models instead.
• String Sequences Without Zero-Padding: Always use zero-padding for String type sequences to ensure proper alphanumeric sorting in screens.
• Forgetting Environment Isolation: Remember that configurations don't auto-replicate between build, QA, and production - plan migration strategy.
• Not Testing Flow Schedules: Always test flows manually in Flow Designer before creating schedules - schedules just trigger execution, they don't control flow behavior.
• Missing Flow-Level Logging: Flow Schedules don't provide automatic logging - configure logging within flows themselves.
• Resetting Production Sequences: Never use "Reset Sequence" in production - it causes duplicate values. Only use for testing environments.
• Over-Complicating Configurations: Start simple - don't create complex schemas until actual business need is clear.
• Ignoring Timezone Impacts: Consider DST transitions and multi-timezone operations when configuring Flow Schedules and Settings.

Best Practices Summary

• Document Everything: Use Description fields in all App Management features to document purpose, dependencies, and configuration decisions.
• Follow Naming Conventions: Adopt consistent naming patterns (e.g., dataModel_fieldName for sequences, descriptive names for schedules).
• Test in Non-Production First: Always validate configurations, sequences, and schedules in build or QA before production deployment.
• Leverage Data Change History: Review audit trails regularly to understand configuration changes and troubleshoot issues.
• Use RBAC Appropriately: Grant Web Access users only the minimum App Management permissions they need - full admin access is powerful.
• Plan for Migration: Include App Management configurations in application packages when migrating between environments.
• Monitor Execution Health: Regularly check Flow Schedule status messages and Data Flow Metrics Dashboard for automation issues.
• Validate Type Matching: Ensure sequence types match data model field types and configuration schemas match expected data structures.

7. Quick Reference: Common Tasks

8. Revision History