Administrative services.
Custom change column query.
Custom create table query.
Dialect used. Tested: mssql and sqlite.
Allows filtering on SQL generated before send to the database.
Data access layer instance.
SQL: let sql = '' + 'ALTER TABLE [UserGroup]' + ' ADD CONSTRAINT [invalid1] FOREIGN KEY ([userId1], [userId2], [userId3]) REFERENCES [User] ([userId1], [userId2], [userId3]) ON DELETE NO ACTION,' + ' CONSTRAINT [invalid2] FOREIGN KEY ([groupId1], [groupId2]) REFERENCES [Group] ([groupId1], [groupId2]) ON DELETE NO ACTION, ' + ' CONSTRAINT [invalid3] FOREIGN KEY ([instanceId1]) REFERENCES [Instance] ([instanceId1]) ON DELETE NO ACTION'
Checks wheather storage is acessible or not and opens firewall in case of any connection block.
Creates the first bot instance (boot instance) used to "boot" the server. At least one bot is required to perform conversational administrative tasks. So a base main bot is always deployed and will act as root bot for configuration tree with three levels: .env > root bot > all other bots.
SQL:
// let sql: string = '' + // 'IF OBJECT_ID('[UserGroup]', 'U') IS NULL' + // 'CREATE TABLE [UserGroup] (' + // ' [id] INTEGER NOT NULL IDENTITY(1,1),' + // ' [userId] INTEGER NULL,' + // ' [groupId] INTEGER NULL,' + // ' [instanceId] INTEGER NULL,' + // ' PRIMARY KEY ([id1], [id2]),' + // ' FOREIGN KEY ([userId1], [userId2], [userId3]) REFERENCES [User] ([userId1], [userId2], [userId3]) ON DELETE NO ACTION,' + // ' FOREIGN KEY ([groupId1], [groupId2]) REFERENCES [Group] ([groupId1], [groupId1]) ON DELETE NO ACTION,' + // ' FOREIGN KEY ([instanceId]) REFERENCES [Instance] ([instanceId]) ON DELETE NO ACTION)'
Removes a bot instance from storage.
Verifies that an complex global password has been specified before starting the server.
Certifies that network servers will reach back the development machine when calling back from web services. This ensures that reverse proxy is established.
Get a dynamic param from instance. Dynamic params are defined in Config.xlsx and loaded into the work folder from /publish command.
Name of param to get from instance.
Value returned when no param is defined in Config.xlsx.
Gets database config and connect to storage. Currently two databases are available: SQL Server and SQLite.
Setup generic web hooks so .gbapps can expose application logic and get called on demand.
Loads all bot instances from object storage, if it's formatted.
Loads just one Bot instance.
Loads just one Bot instance.
Loads just one Bot instance by its internal Id.
Loads all items to start several listeners.
Load all cached schedule from BASIC SET SCHEDULE keyword.
Loads all system packages from 'packages' folder.
Helper to get the web browser onpened in UI interfaces.
Opens storage firewall used by the server when starting to get root bot instance.
Saves a bot instance object to the storage handling multi-column JSON based store 'params' field.
Defines the entry point dialog to be called whenever a user starts talking to the bot.
Replaces the default web application root path used to start the GB with a custom home page.
Syncronizes structure between model and tables in storage.
Writes .env required to start the full server. Used during first startup, when user is asked some questions to create the full base environment.
Generated using TypeDoc
GBCoreService contains main logic for handling storage services related to instance handling. When the server starts a instance is needed and if no instance is found a boot instance is created. After that high-level instance management methods can be created. Core scheduling, base network services are also handled in this service.