Update old documentation terminology

DOCUMENTATION.md

@@ -1,12 +1,12 @@
-# Content CLI as a tool for managing content in the EMS
+# Content CLI as a tool for managing content in the Celonis Platform
 
 -   [Content CLI Core Features](#content-cli-core-features)
     -   [Using profiles](#using-profiles)
     -   [Pull command](#pull-command)
     -   [Push command](#push-command)
 -   [Using content-cli inside Studio](#using-content-cli-inside-studio)
     -   [Pull/Push packages from/to Studio](#pullpush-packages-fromto-studio)
-        -   [Pull package for EMS Store](#pull-package-for-ems-store)
+        -   [Pull package for Celonis Platform Store](#pull-package-for-celonis-platform-store)
     -   [Pull/Push individual assets from/to Studio](#pullpush-individual-assets-fromto-studio)
     -   [Overwrite Package In Studio](#overwrite-package-in-studio)
     -   [Batch Export packages from Studio](#export-multiple-packages-at-once-from-studio)
@@ -27,19 +27,19 @@
 
 Content CLI has three core functionalities:
 
-**Profile:** The CLI connects to the EMS environments through profiles. 
+**Profile:** The CLI connects to the Celonis Platform through profiles. 
 For each of the commands you can specify which profile you want to use. 
 This makes it powerful in the sense that you can pull something from 
-let's say team1.cluser1 and push it directly to team2.cluster2 easily. 
+let's say team1.cluster1 and push it directly to team2.cluster2 easily. 
 You can create a profile using the following command:
 
 ```
 content-cli profile create
 ```
 
-**Pull:** This feature allows you to download content from the EMS to 
-your local machine.Let's take Studio package as an example. These 
-can be exported in the EMS as ZIP files that contain all package assets. 
+**Pull:** This feature allows you to download content from the Celonis Platform to 
+your local machine.Let's take a Studio package as an example. These 
+can be exported in the Celonis Platform as ZIP files that contain all package assets. 
 By using the following command using the package key and profile you 
 have created, you will pull the ZIP file.
 
@@ -48,7 +48,7 @@ content-cli pull package -p team1.cluster1 --key my-package
 ```
 
 **Push:** This feature allows you to push a content file to a team 
-in the EMS. To continue the last example, you can use the following 
+in the Celonis Platform. To continue the last example, you can use the following 
 command to push he previously pulled package in another team.
 
 ```
@@ -67,7 +67,7 @@ content-cli pull package -h
 ### Using profiles
 
 As mentioned above, **Content CLI** allows creating profiles for
-different environments. A profile consists of a name, URL to your EMS
+different environments. A profile consists of a name, URL to your Celonis Platform
 team and an API token. Each of the above mentioned commands include
 a ***--profile*** flag which allows you selecting a profile by its name.
 
@@ -90,23 +90,25 @@ OAuth supports with two grant types: Device Code & Client Credentials.
 
 With Device Code, creating the profile will trigger an authorization flow 
 (using the OAuth 2.0 Device code). You will be prompted to follow an authorization 
-link where you must authorize the **Content CLI** to be able to access the EMS environment 
+link where you must authorize the **Content CLI** to be able to access the Celonis Platform environment 
 on your behalf. 
 
 With Client Credentials, you need to provide the credentials (Client ID, Client Secret) configured for your OAuth client. 
-You can create and configure an OAuth clients in the `Admin & Settings` section of your EMS account, under `Applications`. 
-The OAuth client needs to have the following scopes configured: studio, integration.data-pools, action-engine.projects. 
+You can create and configure an OAuth clients in the `Admin & Settings` section of your Celonis account, under `Applications`. 
+The OAuth client needs to have scopes configured based on the area of commands they're using, e.g.: 
+- For Studio commands: studio, 
+- Data Pipeline/Data Pool commands: integration.data-pools,
 After creating an OAuth client, you should assign it the permissions necessary for the respective commands. More 
 information on registering OAuth clients can be found [here](https://docs.celonis.com/en/registering-oauth-client.html).
 
 ##### API Token
 
 You can choose between two different options when asked for an API token. 
 The first option is to use an API key, which identifies the user that created 
-the key. You can generate an API key in the `Edit Profile` section of your EMS 
+the key. You can generate an API key in the `Edit Profile` section of your Celonis 
 user account, under `API-Keys`. The second options is to use an Application Key,
 which is treated as a new user with separate configurable permissions. You can 
-generate an Application key in the `Team Settings` section of your EMS account, 
+generate an Application key in the `Team Settings` section of your Celonis account, 
 under `Applications`. After creating an Application, you can assign it different
 permissions based on how much power you want to give to the key owner.
 
@@ -126,7 +128,7 @@ which of your commands is set to default.
 
 ### Pull command
 
-By using ***content-cli pull***, you can pull content from an EMS team.
+By using ***content-cli pull***, you can pull content from a Celonis Platform team.
 The CLI pulls that content to the current directory from where you are
 using the CLI.
 
@@ -155,19 +157,19 @@ to specify to which workspace it should be pushed and so on.
 ### Push command
 
 In the opposite to the pull command, with ***content-cli push*** you can
-push content to the EMS. Similarly to the pull command, with the
+push content to the Celonis Platform. Similarly to the pull command, with the
 ***--help*** functionality you can see all the possible entities which
 you can push.
 
 ```
 content-cli push --help
 ```
 
-#### Push .CTP files to the EMS
+#### Push .CTP files to the Celonis Platform
 
 _This functionality supports .CTP files generated on a cpm4 instance version 4.6+._ 
 
-By using ***content-cli push ctp***, you can push **.CTP** files from your local machine to the EMS, like the following examples:
+By using ***content-cli push ctp***, you can push **.CTP** files from your local machine to the Celonis Platform, like the following examples:
 
 ```
 // Push the analysis extracted from the .CTP file
@@ -220,10 +222,10 @@ of your package, like the following example:
 content-cli pull package -p my-profile-name --key ap-operational-app --draft
 ```
 
-#### Pull package for EMS Store
+#### Pull package for Celonis Platform Store
 
 You can use the ***--store*** option to pull the package including the
-store metadata you need to upload the package to the EMS Store, like the
+store metadata you need to upload the package to the Celonis Platform Store, like the
 following example:
 
 ```
@@ -237,7 +239,7 @@ content-cli pull package -p my-profile-name --key ap-operational-app --store
 ### Pull/Push individual assets from/to Studio
 
 The pull/push asset commands work the same way as for other content in
-the EMS. By using content-cli pull asset, you can pull individual assets
+the Celonis Platform. By using content-cli pull asset, you can pull individual assets
 from Studio to your local machine, and an example of it would be:
 
 ```

README.md

@@ -1,7 +1,7 @@
 # Content CLI
 
-Content CLI is a tool to help manage content in Celonis EMS. It provides various commands to help extract 
-content like analyses, packages, assets and others from your Celonis EMS team to your local machine, which 
+Content CLI is a tool to help manage content in Celonis Platform. It provides various commands to help extract 
+content like analyses, packages, assets and others from your Celonis Platform team to your local machine, which 
 you can then push to other teams. This process can be easily achieved by creating profiles for your different 
 teams and execute commands in a profile's context.
 
@@ -39,16 +39,16 @@ as part of our pycelonis examples library [here](https://github.com/celonis/pyce
 
 Content CLI has three core functionalities:
 
-**Profile:** The CLI connects to the EMS environments through profiles. For each of the commands you can specify 
+**Profile:** The CLI connects to the Celonis Platform environments through profiles. For each of the commands you can specify 
 which profile you want to use. This makes it powerful in the sense that you can pull something from let's say 
 team1.cluser1 and push it directly to team2.cluster2 easily. You can create a profile using the following command:
 
 ```
 content-cli profile create
 ```
 
-**Pull:** This feature allows you to download content from the EMS to your local machine. Let's take Studio package 
-as an example. These can be exported in the EMS as ZIP files that contain all package assets. By using the following 
+**Pull:** This feature allows you to download content from the Celonis Platform to your local machine. Let's take Studio package 
+as an example. These can be exported in the Celonis Platform as ZIP files that contain all package assets. By using the following 
 command using the package key and profile you have created, you will pull the ZIP file.
 
 ```
@@ -59,7 +59,7 @@ Example, if you want to pull a package with key "interesting-package" from your
 content-cli pull package -p my-dev-profile --key interesting-package
 ```
 
-**Push:** This feature allows you to push a content file to a team in the EMS. To continue the last example, 
+**Push:** This feature allows you to push a content file to a team in the Celonis Platform. To continue the last example, 
 you can use the following command to push he previously pulled package in another team.
 
 ```
@@ -84,7 +84,7 @@ content-cli pull package -h
 
 ## Building and Using the Project locally 
 
-This tool is tightly connected with the Celonis EMS and all capabilities require to have access to a Celonis EMS Team. 
+This tool is tightly connected with the Celonis Platform and all capabilities require to have access to a Celonis Platform Team. 
 After cloning the project, the next step is to install the project dependencies. We use `yarn` as our package manager, 
 so running `yarn install` on the project root folder should install all the necessary dependencies. After installing 
 the project dependencies, you can run `yarn build` to build the project artifact. To use the built artifact, you can 

docs/internal-architecture.md

@@ -2,7 +2,7 @@
 
 ## **Overview**
 
-The Content CLI is a TypeScript based CLI that allows interaction with the Celonis EMS. Its core functionality includes extracting, pushing, and managing EMS content.
+The Content CLI is a TypeScript based CLI that allows interaction with the Celonis Platform. Its core functionality includes extracting, pushing, and managing Celonis Platform content.
 
 **Key Dependencies**
 
@@ -36,7 +36,7 @@ The context object is passed to all commands and services. It includes:
 
 - **Profile**: The profile which is used for each command execution as authentication.
 - **Logger**: The global logger, with optional debug logging.
-- **HttpClient**: Authenticated EMS API client.
+- **HttpClient**: Authenticated Celonis Platform API client.
 
 This object is passed into command callbacks, ensuring that state and services are shared cleanly:
 ```
@@ -63,7 +63,7 @@ To manage profiles, use the content-cli profile command group. This allows you t
 
 ## **API communication**
 
-The **HttpClient** class is a centralized client for interacting with the EMS API. It handles:
+The **HttpClient** class is a centralized client for interacting with the Celonis Platform API. It handles:
 
 - **Auth**: Authenticates by sending the token in the provided profile.
 - **URL building**: Prefixing all API paths with the correct base (e.g. realm), inferred from the profile

package.json

@@ -1,7 +1,7 @@
 {
   "name": "@celonis/content-cli",
   "version": "1.0.0",
-  "description": "CLI Tool to help manage content in Celonis EMS",
+  "description": "CLI Tool to help manage content in Celonis Platform",
   "main": "content-cli.js",
   "bin": {
     "content-cli": "./dist/content-cli.js"