1. Micro Applications

Menu path: Resource Management → Micro App

Micro applications host static site files—such as HTML, JavaScript, CSS, and images—inside ThinkLink. You can preview an application from the platform or publish it to organization members through a Dynamic Menu.

1.1. Purpose and Use Cases

Micro applications are suitable for browser-based pages that do not require their own application server, including:

• device-data views and lightweight dashboards;
• project information, operating procedures, and internal tools;
• built static files from a single-page application;
• external business frontends that need an entry in the ThinkLink menu.

Each micro application consists of an application record and a set of static files. The record defines its name and entry file; File Management stores the actual page content.

1.2. Prerequisites

• The current user has permission to access Micro App.
• A platform administrator has configured working object storage.
• The static site files can be opened directly by a browser.
• For a frontend project, upload its built output rather than only its source files.

If the page calls ThinkLink or a third-party service, make sure that service permits requests from the page origin. Do not store passwords, tokens, or other long-lived credentials in uploaded files.

1.3. Add an Application

1. Open Resource Management → Micro App.
2. Click Add.
3. Enter the application details:

Field	Description
Application Name	Identifies the application in the list and when configuring a dynamic menu.
Terminal Type	Select PC (pc), Mobile (mobile), or both. At least one is required. New applications default to PC; migration preserves existing terminal assignments.
Entry File	The relative path opened from the application root. The default is index.html.
Remark	Optional notes such as purpose, owner, or version.

4. Click OK to save.
5. Find the new row and open File Management to upload the page content.

Adding an application creates only its record. The application cannot be previewed successfully until a file exists at the configured entry path.

1.4. Upload Page Files

Open File Management and choose the upload method that matches the site structure.

Upload One or More Files

1. To place files below the application root, enter a relative path in Target sub-directory. Leave it empty for the root.
2. Click Upload Files.
3. Select one or more files.
4. After upload, check their paths and sizes in the file list.

Upload a Complete Directory

1. Click Upload Directory.
2. Select the local site directory.
3. The browser uploads all selected files while preserving their relative directory structure.

Confirm that the configured entry path exists after upload. For example, an entry of index.html requires index.html at the application root; an entry of pages/home.html requires that exact directory structure.

1.5. File Management and Online Editing

The file list shows each relative path, size, and available actions. The configured entry file is marked in the list.

Action	Description
New File	Create a text file at a relative path such as index.html or js/main.js.
Edit Online	View and change a supported text file. Binary files do not offer this action.
Copy URL	Copy the complete address for a file. Without sharing, this is a temporary address that expires automatically.
Download	Download one file.
Delete	Delete one file. Deleting the entry file prevents the application root from opening correctly.
Download All	Download the complete application as a ZIP for backup or migration.

After changing or deleting files, preview the application again and verify that its page, scripts, styles, and images still load.

1.6. Preview an Application

1. Return to the Micro App list.
2. Click Preview on the target application.
3. ThinkLink creates a time-limited access credential and opens the entry file in a new window.

You do not need to enable sharing before previewing, but the current user must be signed in and authorized. For a blank page or missing resource, check:

• whether the entry path exactly matches an uploaded file;
• whether scripts, styles, and images use correct relative paths;
• whether every required file was uploaded;
• whether the browser console reports a cross-origin, script, or resource error.

1.7. Copy an Address or Enable Sharing

From File Management, click Copy App URL, or click Copy URL for one file.

Sharing Disabled

ThinkLink creates a temporary address that expires automatically. Use it for short tests and reviews; do not save it as a permanent application entry.

Sharing Enabled

1. Turn on Share for the application in the list.
2. ThinkLink creates and copies a new sharing link.
3. Use Copy Link later to copy the current sharing address again.

Security: Anyone with a sharing link can open the application without signing in. Do not include credentials, personal information, or organization-only data in a shared application. Turning sharing off invalidates the current link. Turning it on again creates a new link; the previous link does not become valid again.

1.8. Download and Back Up

• Click Download in the application list or Download All in File Management to download the complete application as a ZIP.
• Click Download on a file row to download only that file.
• Before a large edit or deletion, download the complete application as a backup.

1.9. Delete an Application

1. Find the application in the list.
2. Click Delete.
3. Read the impact message and confirm.

Warning: Deleting an application removes its file records, dynamic menus that point to it, and the associated role permissions. The interface cannot undo this operation. Download a backup and confirm that its menu entries are no longer needed.

1.10. Quotas and Troubleshooting

Limit	Current maximum
Micro applications per organization	10
Size of one file	20 MiB
Total size of one application	20 MiB
Total size of one upload	20 MiB
Files in one upload	300

The application list and File Management show current usage. At the application-count limit, delete an unused application first. At the size limit, remove unused files or reduce assets such as images and scripts before uploading again.

Symptom	What to check
Preview reports that the page does not exist	Verify the entry path and confirm the matching file exists.
The page opens without styles or images	Check relative paths in the HTML and confirm the complete directory structure was uploaded.
Another user cannot see the menu	Enable and show the dynamic menu, then grant it to the user's role.
A copied address stops working later	With sharing disabled, the copied address is temporary. Enable sharing only after evaluating the security risk of permanent anonymous access.
More files cannot be uploaded	Check the per-file, per-upload, and total application limits.

1.11. Publish to the Sidebar

After the files are uploaded and preview works:

1. open Advanced Features → Dynamic Menu;
2. add a menu whose content source is Micro App, then select this application;
3. configure its mount position, open mode, sort order, visibility, and enabled state;
4. open System Management → Role Management and grant the dynamic menu to the target role;
5. sign in as a user with that role or re-enter the organization, then confirm the menu appears and opens.

See Dynamic Menus for the complete field reference.

1.12. Multiple Terminals and Filtering (Since 2.00.071)

One micro application can support both PC and Mobile without duplicate application records.

1. Add or edit an application in the list.
2. Select PC, Mobile, or both under Terminal Type. Keep at least one selected; new applications default to PC.
3. Save and check the displayed types. An application supporting both terminals can be found under either terminal filter.

type changes from a single value to an array, such as ["pc","mobile"]. Migration preserves existing terminal assignments, and the edit form can display historical single values. Update integration scripts to use arrays instead of treating the field as a single string.

Terminal selection does not automatically change preview dimensions, access permissions, or responsive layout. Adapt pages for mobile screens; existing menu authorization and sharing rules still apply.

1.13. Set the Main Application (Since 2.00.073)

1. Confirm that the application's Terminal Type includes Mobile. PC-only applications cannot become the main application.
2. Turn on Main Application in the application list.
3. Check the list: each tenant can have at most one main application. Selecting a new one automatically clears the previous selection.
4. To have no main application, turn off the current switch. All main-application switches may be off.

The setting is tenant-scoped. Backend transactions and a unique database index enforce uniqueness, and changes are recorded in history.

APP behavior has not been verified

Automatically opening the main application after APP login is a design goal. The related mobile repositories were outside this update, and actual APP behavior has not been verified. Enabling the switch is not evidence that automatic opening works.

See Scene Management for device bindings and 2.00.071–2.00.073 Upgrade Notes for migration impact.

2.00.083 management entry and resources

The management route is /tenant/resource-management/micro-app, with permission 1401 (verify migration from 805). Preserve existing application IDs, configuration, hosted addresses, routes, menus and business permissions; do not recreate applications for the menu move.

Each organization supports 10 applications. The application total, single file, upload file total and ZIP package limits are 20 MiB; each upload supports up to 300 files. Read /thinklink/micro-app/quota for actual limits. Multipart overhead counts toward the 20 MiB request limit, so leave headroom.

Use File Management for large models and textures; ordinary files have separate 50 MiB single-file and organization-total limits. Follow Data and Resources for scope, pagination, status and caching.