Development modes and project protection#

Sign-in and developer permissions#

Process creation and management use a unified web interface after authentication. The Account, Role and access folder determine available projects and blocks. Permissions are checked for reading, editing, publishing and execution, including API requests.

No-Code and Low-Code#

No-Code workflows use predefined components only. Users enter parameter values and select variables, but cannot write code or free-form program expressions. The restriction applies to editing, import, publication and execution. A predefined component’s internal implementation is not a user program.

Low-Code permits programming for Users whose Role grants that permission. The editor supports syntax highlighting, C# 9 or later, namespaces, classes and methods. Code is validated and compiled when its package is created. Repeated execution uses the compiled artifact.

Configuration follows these steps:

1. The administrator defines project access and the Role’s development mode.
2. The User creates a workflow from permitted blocks.
3. Workflow contents, program components and execution permissions are checked before publication.

Workflow and code protection#

Projects are stored and transferred in an encrypted protected format. Authorized platform tools open the contents, which are not accessible as an ordinary XML file. Viewing permission does not grant editing or export permission.

Program code is published as an independent reusable block. The package is signed at publication, and Runtime checks its signature and integrity before execution. Modified or untrusted packages do not run.

For server storage, the administrator can prohibit local project import and export. The policy covers the interface and API. Permission to run local Robots and permission to import are separate settings.