Documentation
Documentation
Main site
Academy
Community forum
Overview
Features
Getting started
Login and Signup
Profile settings
App management
Adding developers
Interface overview
Data
Data structures
Data types
System structures
Directual Query Language (DQL)
Import and export
❔File storage
Template system
Principles of templating
Formatting date/time data
Comparison component
Evaluating as a JS-expression
Tips for dealing with data
Scenarios
Principles of Directual scenarios
Directual event model
Event-driven triggers
Schedule triggers
Synchronic scenarios
Editing scenarios
System steps
Action steps
Integration steps
Condition steps
Using variables
Testing and debugging
System scenarios
API and integraions
API-endpoints (Security Layer)
❔Webhooks
Database listeners
Other integrations
Role-based access control
❔Configuring RBAC
❔Authentication options
Interface for your app
Options for building an app interface
Web-page builder
Components
Embedding pages
Directual 💙 React JS
React Boilerplate code
Reports
❔Configuring a report
❔Running a report
JavaScript SDK
Directual JavaScript SDK basics
Internal $D methods
Useful standard JS functions
JS SDK examples
Lifecycle management
❔App snapshots
Pricing and billing
Pricing plans
On-demand resource consumption
Using credits
Support
Contact Directual
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 - API and integraions
API-endpoints (Security Layer)
Last updated 6 days ago