Browse Source

Merge pull request #26338 from abpframework/salihozkara/new-session-9ed7f5

Remove preview notices from Low-Code documentation
pull/26346/head
Enis Necipoglu 3 weeks ago
committed by GitHub
parent
commit
2c41dc31af
No known key found for this signature in database GPG Key ID: B5690EEEBB952194
  1. 2
      docs/en/low-code/add-to-existing-solution.md
  2. 2
      docs/en/low-code/code-integration.md
  3. 2
      docs/en/low-code/custom-endpoints.md
  4. 2
      docs/en/low-code/designer.md
  5. 2
      docs/en/low-code/expression-language.md
  6. 2
      docs/en/low-code/fluent-api.md
  7. 2
      docs/en/low-code/foreign-access.md
  8. 2
      docs/en/low-code/formula-properties.md
  9. 2
      docs/en/low-code/index.md
  10. 2
      docs/en/low-code/interceptors.md
  11. 2
      docs/en/low-code/mcp.md
  12. 2
      docs/en/low-code/model-json.md
  13. 2
      docs/en/low-code/react-runtime.md
  14. 2
      docs/en/low-code/reference-entities.md
  15. 2
      docs/en/low-code/script-actions.md
  16. 2
      docs/en/low-code/scripting-api.md

2
docs/en/low-code/add-to-existing-solution.md

@ -7,8 +7,6 @@
# Add Low-Code to an Existing Solution
> **Preview:** The Low-Code System is currently in preview. APIs, generated files, designer behavior, and React runtime details may change before general availability.
This guide explains how to add the ABP Low-Code System to an existing solution instead of generating a new solution with Low-Code enabled from the beginning.
Keep every ABP and Low-Code package aligned with the ABP version used by the existing solution. When an example contains a version placeholder, replace it with that version instead of copying a version from another solution.

2
docs/en/low-code/code-integration.md

@ -7,8 +7,6 @@
# Code Integration
> **Preview:** Low-Code integration APIs are part of the preview Low-Code System. Registration details, repository behavior, and page service contracts may change before general availability.
Use the [Low-Code Designer](designer.md) and [React Runtime](react-runtime.md) for standard CRUD screens. This page covers the integration points for the cases where low-code models and regular application code need to reach each other directly.
## Choose the Right Integration Path

2
docs/en/low-code/custom-endpoints.md

@ -7,8 +7,6 @@
# Custom Endpoints
> **Preview:** Custom endpoint descriptors and scripting helpers are part of the preview Low-Code System. Names, validation rules, and runtime behavior may change before general availability.
Use generated page CRUD APIs for normal dynamic entity pages. Custom endpoints are an advanced option for exposing small model-owned REST APIs that do not map to standard list, get, create, update, delete, export, file, or attachment operations.
Custom endpoints are defined in JSON descriptor files or through the Low-Code Designer. Each endpoint executes server-side JavaScript and is registered as an ASP.NET Core route.

2
docs/en/low-code/designer.md

@ -7,8 +7,6 @@
# Low-Code Designer
> **Preview:** The Low-Code Designer is part of the preview Low-Code System. Designer screens, metadata fields, and validation rules may change before general availability.
The Low-Code Designer is available in ABP Admin Console. It is the main UI for building and maintaining low-code descriptor metadata.
```text

2
docs/en/low-code/expression-language.md

@ -13,8 +13,6 @@ Expressions are not JavaScript. They cannot contain arbitrary code, SQL, network
An expression can contain up to 4096 characters.
> **Preview:** The language profile is preview functionality. The supported syntax and function set may change before general availability.
## Values and field references
Use invariant numeric literals, quoted strings, Boolean values, and date constructors. Reference a property by name:

2
docs/en/low-code/fluent-api.md

@ -7,8 +7,6 @@
# Attributes & Fluent API
> **Preview:** Attributes and Fluent API configuration for the Low-Code System are preview APIs. Prefer the designer for day-to-day modeling work, and review release notes before relying on these APIs in long-lived integrations.
Use the [Low-Code Designer](designer.md) for runtime pages, forms, filters, dashboards, menus, and page groups. The code-first surface documented here is for source-controlled model metadata: entity definitions, property metadata, enums, validation, attachments, relationships, and runtime overrides.
## What This Surface Configures

2
docs/en/low-code/foreign-access.md

@ -7,8 +7,6 @@
# Foreign Access
> **Preview:** Foreign access metadata is part of the preview Low-Code System. Relation behavior and designer options may change before general availability.
Use the [Low-Code Designer](designer.md) to review relation metadata visually. This page explains the advanced configuration values that control how related dynamic entities can be reached from runtime pages.
Foreign Access controls how related **dynamic entities** can be accessed through foreign key relationships. It determines whether users can view or manage related data directly from the **target entity's** UI.

2
docs/en/low-code/formula-properties.md

@ -16,8 +16,6 @@ The Designer supports two kinds of calculated property:
Both kinds can participate in filtering, sorting, paging, count, projection, grouping, and supported aggregates while the work remains in the database provider. The complete entity set is not loaded into application memory to calculate the values.
> **Preview:** Calculated properties, rollups, and the expression profile are preview features. Supported operations and provider translation may change before general availability.
## Availability
Calculated and rollup properties can be authored in a writable Runtime JSON-backed layer that supports direct model changes. The corresponding commands are disabled when the selected Designer layer does not support them.

2
docs/en/low-code/index.md

@ -9,8 +9,6 @@
> You must have an ABP Team or a higher license to use this module.
> **Preview:** The Low-Code System is currently in preview. APIs, designer behavior, generated metadata, and React runtime details may change before general availability. Use it for evaluation and controlled projects, and review release notes before upgrading.
The ABP Low-Code System lets you build data-driven admin screens from metadata. The primary workflow is the **Low-Code Designer** in ABP Admin Console, backed by the **React runtime** in your application.
Use the designer to model entities, enums, properties, relations, pages, forms, filters, permissions, actions, and health checks. The runtime uses the same metadata to provide:

2
docs/en/low-code/interceptors.md

@ -7,8 +7,6 @@
# Interceptors
> **Preview:** Interceptors and their JavaScript context are preview extension points. Script context members, validation behavior, and lifecycle hooks may change before general availability.
Use designer actions and descriptor metadata for standard low-code behavior first. Interceptors are an advanced extension point for adding JavaScript lifecycle logic when the generated CRUD flow needs validation, transformation, or replacement behavior.
Interceptors allow you to run custom JavaScript code before, after, or instead of Create, Update, and Delete operations on dynamic entities.

2
docs/en/low-code/mcp.md

@ -7,8 +7,6 @@
# MCP Integration
> **Preview:** The low-code MCP surface is part of the preview Low-Code System. Endpoint behavior, authorization requirements, and mutation metadata may change before general availability.
The Low-Code Designer exposes a **remote Model Context Protocol (MCP) server** from the running ABP HTTP API host. It is not a local `stdio` tool package. MCP clients connect to your application over HTTP, authenticate with an OpenIddict access token, and work against the same **runtime database-backed** model that the Designer edits in the **Runtime JSON** layer.
Use [Model Descriptor Files](model-json.md) when you need source-controlled `_Dynamic/model/**/*.json` files. Use MCP when an agent or automation needs authenticated, structured runtime access that the Designer can immediately show.

2
docs/en/low-code/model-json.md

@ -7,8 +7,6 @@
# Model Descriptor Files
> **Preview:** The Low-Code System is currently in preview. The descriptor format is stable enough for evaluation and source control, but fields may change before general availability.
Low-code metadata is source-controlled as JSON descriptor files used by the Low-Code Designer and React runtime. Current generated projects keep descriptors as split files under `_Dynamic/model`; older projects may still contain an aggregate `_Dynamic/model.json` document. Use the [Low-Code Designer](designer.md) for normal editing. Use this page when you need to review, generate, merge, or source-control the JSON metadata directly.
## File Location

2
docs/en/low-code/react-runtime.md

@ -7,8 +7,6 @@
# React Runtime
> **Preview:** The React low-code runtime is part of the preview Low-Code System. Runtime APIs, generated routes, metadata contracts, and UI behavior may change before general availability.
The React runtime renders low-code pages from backend metadata. Generated low-code React applications include the required package and wiring.
```json

2
docs/en/low-code/reference-entities.md

@ -7,8 +7,6 @@
# Reference Entities
> **Preview:** Reference entity metadata is part of the preview Low-Code System. Registration APIs, relation options, and designer behavior may change before general availability.
Use the [Low-Code Designer](designer.md) to select reference entities after they are registered in application startup. This page explains the registration and metadata details behind that designer experience.
Reference Entities allow you to create foreign key relationships from **dynamic entities** to **existing C# entities** that live outside the Low-Code System.

2
docs/en/low-code/script-actions.md

@ -7,8 +7,6 @@
# Script Actions
> **Preview:** Script actions are part of the preview Low-Code System. Descriptor fields, designer screens, and script context members may change before general availability.
Use **Actions** in the Low-Code Designer when descriptor metadata and generated CRUD behavior are not enough. Actions can add JavaScript-backed HTTP endpoints, distributed event handlers, background jobs, and scheduled background workers.
Custom HTTP endpoints are documented separately in [Custom Endpoints](custom-endpoints.md). This page focuses on the shared action designer experience and the event handler, background job, and background worker action types.

2
docs/en/low-code/scripting-api.md

@ -7,8 +7,6 @@
# Scripting API
> **Preview:** The Low-Code scripting API is a preview server-side JavaScript surface. Available globals, helper methods, limits, and sandbox behavior may change before general availability.
The designer and React runtime cover the standard CRUD, form, filter, and export workflows. Use the scripting API when an interceptor, action, or custom endpoint needs server-side JavaScript.
The Low-Code System provides a server-side JavaScript scripting engine for executing custom business logic within [interceptors](interceptors.md), [custom endpoints](custom-endpoints.md), event handlers, background jobs, and background workers. Scripts run in a sandboxed environment with access to a database API backed by EF Core.

Loading…
Cancel
Save