--- title: "ePO - On-prem command framework: best practice" slug: "epo-on-prem-command-framework-best-practice" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T17:47:05Z published: 2026-09-07T17:47:05Z canonical: "docs.trellix.com/epo-on-prem-command-framework-best-practice" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # ePO - On-prem command framework: best practice The structure of the ePO - On-prem framework allows you to access all ePO - On-prem command objects and their parameters using the API or the user interface. To understand the ePO - On-prem framework, you can compare how the `AppliedTag` command is accessed from multiple places in the ePO - On-prem user interface and the web URL. The `AppliedTag` command is accessed from the **System Tree** page in the ePO - On-prem user interface. You can find valid `AppliedTag` command parameters using this core.listTables web URL command: `https://<localHost>:8443/remote/core.listTables` The following Web URL command structure, and its parts, are used to find the `AppliedTags` command. `https://<localHost:8443/remote/core.listDatatypes?type=applied_tags` Following are the parts of the web URL command. - **Basic URL** — Your remote console connection URL. The default port number is 8443. - **Command name** — Appears before the `?` and is listed in the web API Help. - **Command argument** — Appears after the `?` and is separated by `&` (ampersands). You can also add S-Expressions to your commands.