47 docs tagged with "LOC"

The administration panel has a series functions for management roles.

In future releases the administration panel will only be accessed by authorised LOC Owners.

Data Context is an object injected into logic functions at runtime, which containes some key components:

- To create a microservice consisted of two data processes.

- To create a schedule trigger for executing a data process at a specific interval.

See Introduction and Setup first if you haven't gone through the steps above.

- To create an API route (a HTTP endpoint) for a deployed data process.

API Route

Execution

Data Process

Connecting external databases with built-in drivers. Currently the following databases are supported:

For executing a select/action query given by another logic and write the query result (if any) to session storage.

- To understand what are events in LOC.

Emit and query LOC data events.

- To query events emitted from another data process.

Accessing and writing files. Supports the following storages:

CLI commands for

For sending HTTP requests to specific hosts.

We will follow the steps of this article to create, implement and test all assets of the Lakeside Oasis Café use case.

- LOC v0.10 Release Note

LOC SDK is a downloadable NPM package that defines the interfaces of data context as well as agents - a series of features provided by LOC's logic runtime that can read and/or write internal and external storages.

LOC Studio is the web-based graphical user interface for LOC Core. Thanks to its highly-interactive Reack framework and UI/UX-driven design, Studio is intuitive to use and doesn't need a lot of walkthrough to learn. You've probably already used most of it in Quick Start and Tutorials.

To create a comprehensive project consist of

Developing with CLI

- To understand features in LOC and their hierarchy.

For sharing data between tasks of one data process, which can stay persistent for a period of time.

Log (debugging) messages to LOC.

- To understand how logic are executed in a data process.

Read a local environment variable (not to be confused with local storage data or secrets in agent configurations). These variable can be set via Studio or CLI, which are useful for configuring a data process' behavior without modifying the logic code.

Sending emails with a SMTP server.

Payload is a lazy-loaded object which contains metadata and payload data (if any) from a trigger as the initial input of the data process and for determining how the data process is triggered.

Parse trigger payload to JSON and write to the session storage.

CLI commands for managing assets in LOC:

Parse QueryString from the HTTP request into an object.

- To create your first data process in LOC.

LOC v0.10 is a minor update that focus on various improvements in LOC Studio.

Finalise a JSON object as the task result data. If the trigger is synchronized API route or message queue, it will be returned to the trigger, otherwise stored in LOC to be retrieved later.

Parse trigger payload to JSON and write to the session storage.

- To create a HTTP configuration.

For sharing data between logic during a task (execution) of a data process.

Synchronising Local and Remote Project

In order to implement the order tracking feature for Lakeside Oasis Café, here's a simplified system design process.

- To understand how LOC handles logic errors by default.

CLI commands for managing assets in LOC:

For managing triggers which can invoke data processes. Currently the following trigger features are available in Studio:

This feature is only accessed by authorised LOC Owners.

CLI commands for managing assets in LOC: