Documentation
Documentation
Main site
Overview
Platform Features
Getting started
Login and Signup
App management
Data
Data structures
Data types
Directual Query Language (DQL)
Import and export
File storage
Template system
Principles of templating
Evaluating as a JS-expression
Comparison component
Tips for dealing with data
Scenarios
Principles of Directual scenarios
Event-driven triggers
Schedule triggers
Synchronic scenarios
Editing scenarios
Using variables
Testing and debugging
System scenarios
Advanced scenario settings
API and integraions
API-endpoints (Security Layer)
Webhooks
Other integrations
Authentication API
Security features
App interface
Options for building an app interface
Web-page builder
Directual 💙 React JS
React Boilerplate code
Reports
Configuring a report
Running a report
JavaScript SDK
Directual JavaScript SDK basics
Internal $D methods
JS SDK examples
Lifecycle management
❔App snapshots
Pricing and billing
Pricing plans
On-demand resource consumption
Support
Contact Directual
Courses (coming soon)
Directual 101 (⏳coming soon)
Dealing with API (⏳coming soon)
Best practices (⏳coming soon)
Powered by GitBook

System scenarios

Sometimes you can face System scenarios (in a System scenarios folder). Such scenarios appeared automatically when you activate additional features like Telegram or some types of Components.

You can edit system scenarios, but be careful! If you edit scenario and something went wrong, restore the older version of a scenario.

Previous
Testing and debugging
Next
Advanced scenario settings
Last updated 5 months ago