diff --git a/content/en/docs/releasenotes/workstation/_index.md b/content/en/docs/releasenotes/workstation/_index.md index c660c0a9ce1..ede9b9f279f 100644 --- a/content/en/docs/releasenotes/workstation/_index.md +++ b/content/en/docs/releasenotes/workstation/_index.md @@ -236,7 +236,7 @@ For more information, see [Nanoflows](/mendix-workstation/connector/#javascript- * Automatic suffixing for duplicate workstations – To make managing your workstations even smoother, we have implemented automatic suffixing for imported workstations that have duplicate names. This helps prevent naming conflicts and keeps your environment tidy. * Feedback module replaced by the new Forum Space – We have removed the Feedback function in the Workstation Management. Don't worry, your voice is still incredibly important to us! Please share your questions, ideas, and feedback in the new dedicated [Mendix Forum Space for Mendix Workstation](https://community.mendix.com/link/spaces/mendix-workstation-client). This change will help us centralize discussions and provide better support. -* Special characters in Workspace names – You can now use special characters in your Workspace names, giving you more flexibility and personalization. +* Special characters in workspace names – You can now use special characters in your workspace names, giving you more flexibility and personalization. * Unique auto-accepted computer names – We have added a uniqueness validation to the **Auto-Accepted Computer Name** field used for bulk registration. This ensures that each computer name is distinct, preventing potential conflicts during the registration process. #### Fixes @@ -362,7 +362,7 @@ Mendix Workstation is [Limited Availability](/releasenotes/release-status/#limit #### Logging Is Configurable in Workspace Settings -The level of logs written to log files and visible in the client is configurable in Workspace Settings. You can configure the following: +The level of logs written to log files and visible in the client is configurable in workspace Settings. You can configure the following: * Log level: Info, Warn, Error, Debug. * Log retention policy: Maximum log folder size (in MB) and maximum number of stored days. @@ -611,7 +611,7 @@ The second pre-release of Mendix Workstation is available under the conditions o #### Breaking Changes * The new connector is incompatible with the previous releases. Your Mendix app must be refactored to adopt the new pattern. -* Due to the introduction of the Workspace, existing station configurations are deleted. Stations must be reconfigured. +* Due to the introduction of the workspace, existing station configurations are deleted. Stations must be reconfigured. * The Workstation Management is no longer compatible with the Workstation Client version 2.0. Clients must be updated to version 2.1. #### App Upgrade diff --git a/content/en/docs/workstation/management/wks-management-admin.md b/content/en/docs/workstation/management/wks-management-admin.md index e9c7512dcdc..8b1c9540702 100644 --- a/content/en/docs/workstation/management/wks-management-admin.md +++ b/content/en/docs/workstation/management/wks-management-admin.md @@ -99,15 +99,16 @@ Auto detecting card readers is enabled by default. You can toggle the **Detect C ### Developer Mode {#developer-mode} -Developer mode can be configured on the **Station** page by toggling **Enable Developer Mode**. +Developer mode can be configured on the **Station** page by selecting **Enable Developer Mode**. -When Developer Mode is enabled, users of the Workstation Client have access to: +Environments created with the Test environment type have developer mode enabled by default for easier testing. Changing the environment type after creation does not enable or disable developer mode. For more information about creating environments, see [Configuring Mendix Workstation Management](/mendix-workstation/management-config/). -* Quit the program from the start menu. -* Unlink the Workstation Client, allowing it to be registered to another station. +When developer mode is enabled, users of the Workstation Client can perform the following actions: + +* Quit the program from the Start menu. +* Deregister the Workstation Client, allowing it to be registered to another station. * Debug level live logs displayed in the Logs pane of the Workstation Client, even if the workspace's log level is set to a different level. -* Developer tools (accessible by pressing *Ctrl + Shift + I*). {{% alert color="info" %}} -For production environments, it is strongly recommended to disable Developer Mode. This prevents Workstation operators from accidentally quitting or unlinking the Workstation Client and restricts access to debugging tools that are not needed in a live operational setting. +For production environments, it is strongly recommended to disable Developer Mode. This prevents Workstation operators from accidentally quitting or deregistering the Workstation Client, and restricts access to debugging tools that are not needed in a live operational setting. {{% /alert %}} \ No newline at end of file diff --git a/content/en/docs/workstation/management/wks-management-devices.md b/content/en/docs/workstation/management/wks-management-devices.md index e4762c3c21e..ea44bd171f3 100644 --- a/content/en/docs/workstation/management/wks-management-devices.md +++ b/content/en/docs/workstation/management/wks-management-devices.md @@ -8,7 +8,7 @@ weight: 60 ## Introduction -This section details how to configure various device types for the current station. For each device type, you will find instructions on how to set it up in the Management UI, along with the specific message syntax required for Mendix applications to communicate with it through the Workstation Client. +This section details how to configure various device types in Workstation Management, along with the specific message syntax required for Mendix applications to communicate with the device through the Workstation Client. ## Device Connectivity @@ -30,7 +30,7 @@ Before connecting devices with Mendix Workstation, perform the following steps: Card reader devices cannot be configured as separate devices in the **Devices** overview of a **Station** page. Instead, they are automatically detected by the Workstation Client and added to the device list of the Client. -Auto detecting card readers is enabled by default. This setting can be configured on a **Station** page by unselecting **Detect Card Readers**. +Auto detecting card readers is disabled by default. You can enable this setting on a **Station** page by selecting **Detect Card Readers**. ### Message Syntax {#card-readers} @@ -47,21 +47,115 @@ Send instruction in hexadecimal as a string, for example, *FFCA000000* to read t * `2# Response` - Response from device as raw hexadecimal. * `3# Error` - Error message from device. +## Serial Port + +Serial Port devices allow you to connect to a device with a serial port. + +### Configuring Serial Port Devices + +To add a serial port device, perform the following steps: + +1. In Workstation Management, navigate to the **Devices** section on the **Station Detail** page. +2. Click **Add Device** and, and then click **Serial Port**. +3. Click **Next**. +4. Enter a meaningful name for the device. +5. Optional: Select or create a class to help you manage your devices. +6. Click **Next**. +7. In the **Detect Serial Device By** section, select one of the following values, depending on whether the serial port device uses static or dynamic port assignment: + + * For static port assignment, select **Port**. + * For dynamic port assignment, select **Identifiers**. + +8. For static port assignment, configure the following connection parameters: + + * **Port** - Required; the identifier of the serial port + * **Baudrate** - Required; the Bits per Second rate + * **Data Bits** - Required; the number of bits per data frame + * **Parity** - Optional; the parity mechanism used, that is, the way in which an extra bit is added to each data byte in order to help detect transmission errors + * **Flowcontrol** - Optional; the handshake mechanism between the server and receiver, used to prevent data overflow + * **Stop Bits** - Required; the bits when data transmission ends. + +9. For dynamic port assignment, configure the following connection parameters: + + * At least one of the following required identifiers: + + * **Serial Number** - The serial number of the device + * **Friendly Name** - Only available on Windows systems; the device name from Device Manager + * **Manufacturer** - The manufacturer of the device + * **Plug and Play ID** - The PnPId of the device. + + * **Baudrate** - Required; the Bits per Second rate + * **Data Bits** - Required; the number of bits per data frame + * **Parity** - Optional; the parity mechanism used, that is, the way in which an extra bit is added to each data byte in order to help detect transmission errors + * **Flowcontrol** - Optional; the handshake mechanism between the server and receiver, used to prevent data overflow + * **Stop Bits** - Required; the bits when data transmission ends. + +10. Click **Next**. +11. In the **Split Incoming Message By** section, select one of the following options: + + * **Delimiter** - Messages received from the device are split by the specified character or characters marking the end of the message, for example, `\r\n`. + * **Time and Size** - Messages received from the device are split by time interval in milliseconds and maximum message size in bytes. + * **Do Not Split** - Messages received from the device are not automatically split. + +12. In the **Characters Added to Message** field, specify the character or characters marking the end of the message sent to the device, for example, `\r\n`. +13. In the **Encoding** field, select the message encoding. +14. Click **Add Device**. + +## Bluetooth + +Add Bluetooth LE (BLE) devices that use the ATT protocol by entering the exact device name as displayed in your operating system's Device Manager. + +### Configuring Bluetooth Devices + +To add a Bluetooth device, perform the following steps: + +1. In Workstation Management, navigate to the **Devices** section on the **Station Detail** page. +2. Click **Add Device** and, and then click **Bluetooth**. +3. Click **Next**. +4. Enter the exact device name as it is displayed in your operating system's Device Manager. +5. Optional: Select or create a class to help you manage your devices. +6. Click **Add Device**. + +### Message Syntax + +This device type requires the following message and response: + +#### Message + +* `0#ServiceUUID#CharacteristicUUID` - Subscribe to characteristic `CharacteristicUUID` from service `ServiceUUID`. +* `1#ServiceUUID#CharacteristicUUID` - Unsubscribe from characteristic `CharacteristicUUID` from service `ServiceUUID`. +* `2#ServiceUUID#CharacteristicUUID` - Read characteristic `CharacteristicUUID` from service `ServiceUUID`. +* `3#ServiceUUID#CharacteristicUUID` - Write to characteristic `CharacteristicUUID` from service `ServiceUUID`. + +### Response + +* `CharacteristicUUID#Response` + ## File Device -The File Device allows Mendix applications to interact with the local file system of the computer running the Workstation Client. +The file device allows Mendix applications to interact with the local file system of the computer running the Workstation Client. -### Configuration in Management UI +### Configuring File Devices -To add a File Device, perform the following steps: +To add a file device, perform the following steps: -1. Navigate to the **Devices** section on the **Station Detail** page. -2. Click **Add Device** and select **File Device**. -3. Provide a **Device Name** (for example, *Write files to test folder*). +1. In Workstation Management, navigate to the **Devices** section on the **Station Detail** page. +2. Click **Add Device**, and then select **File Device**. +3. In the **Device Name** field, enter an identifying name for the device. +4. Optional: Select or create a class to help you manage your devices. +5. Click **Next**. +6. Configure the following connection parameters: -### Allowed Folder Configuration + * **Allowed Folder** - The folder in which the Workstation Client can perform actions. The allowed folder supports flexible path configuration through environment variables, providing cross-platform compatibility for both Windows and Unix-based systems. For more information, see [Allowed Folder Configuration](#allowed-folder). + * **Allow subscribing to change events** - Allows the Workstation Connector to monitor the allowed folder for changes. + * **Allow reading files** - Enables Mendix applications to read the content of files within the allowed folder. + * **Allow writing files** - Enables Mendix applications to write content to files within the allowed folder. -The *Allowed Folder* feature supports flexible path configuration through environment variables, providing cross-platform compatibility for both Windows and Unix-based systems. This functionality allows administrators to define the allowed folder where the Workstation Client can perform actions. +7. Click **Add Device**. + +### Allowed Folder Configuration {#allowed-folder} + +For more information about supported environment variables and path formats for the allowed folder, refer to the sections below. #### Environment Variable Support @@ -76,17 +170,9 @@ Windows and Unix-style paths can be used independently of the operating system t * Unix-style with backslash: `$EnvVar\test` * Unix-style with forward slash: `$EnvVar/test` -### Allowed Actions - -You can grant one or more of the following permissions for the File Device: - -* Subscribe to change events - Allow the Workstation Client to monitor the configured folder for changes. -* Read files - Allow Mendix applications to read the content of files within the allowed folder. -* Write files - Allow Mendix applications to write content to files within the allowed folder. - ### Message Syntax {#file-device} -Before sending messages to the File Device, review the following points: +Before sending messages to the file device, review the following points: * Path handling - You can provide the paths either as absolute (for example, `/var/log/app.log` or `C:\Data\report.txt`), or as relative paths. Relative paths are always interpreted relative to the allowed folder configured in Workstation Management. * Delimiter - The `#` character is used as a delimiter within messages. Paths and data may not contain the `#` character. @@ -109,18 +195,18 @@ Before sending messages to the File Device, review the following points: ### Example Test: Verifying File Device Configuration -Follow these steps to verify that your File Device configuration is working correctly: +Follow these steps to verify that your file device configuration is working correctly: 1. Create a new Workspace in the Workstation Management. -2. Create a new Station. -3. Add a `File Device` with the following configuration to this Station: +2. Create a new station. +3. Add a file device with the following configuration to this station: * **Device Name** - A meaningful name, for example, *Write files to test folder*. * **Allowed Folder** - For example, on a Windows computer you can use a path like `C:\MyTestFolder`. Ensure this folder exists on the computer where the Workstation Client will run. * **Allow writing files** - Select **Yes**. * Use the default values for everything else. -4. Register the Station to your computer (assuming the Workstation Client is installed there). +4. Register the station to your computer (assuming the Workstation Client is installed there). 5. In your Workspace, navigate to **Test Your Station** and click **Test** by the configured file device. 6. Enter `3#test.txt#Hello from Mendix` in the **Send Message** field, and then press **Send Message**. @@ -129,44 +215,78 @@ Follow these steps to verify that your File Device configuration is working corr 7. Go to *C:\MyTestFolder* and verify that it contains the text file. 8. Open the test file and verify that it contains the text *Hello from Mendix*. -## Bluetooth Devices +## TCP/IP Client -Bluetooth Low Energy (BLE) devices using the ATT protocol can be integrated with Mendix Workstation. +TCP/IP clients allow you to connect to remote devices over the network. -### Configuration in Management UI +### Configuring TCP/IP Clients -To add a Bluetooth Device, perform the following steps: +To add a TCP/IP client, perform the following steps: -1. Navigate to the **Devices** section on the **Station Detail** page. -2. Click **Add Device** and select **Bluetooth Device**. -3. Enter the exact device name as it is displayed in your operating system's device manager. +1. In Workstation Management, navigate to the **Devices** section on the **Station Detail** page. +2. Click **Add Device**, and then select **TCP/IP Client**. +3. In the **Device Name** field, enter an identifying name for the device. +4. Optional: Select or create a class to help you manage your devices. +5. Click **Next**. +6. Configure the following connection parameters: -### Message Syntax + * **Host** - The host to which the TCP/IP Client connects. For test scenarios, you can use `localhost` to connect to a TCP/IP server on the same machine. For production scenarios, it is usually a local IP address. + * **Port** - The port to which the TCP/IP Client connects. The value must be in the range of `0-65535`. -This device type requires the following message and response: +7. Click **Next**. +8. In the **Split Incoming Message By** section, select one of the following options: -#### Message + * **Delimiter** - Messages received from the device are split by the specified character or characters marking the end of the message, for example, `\r\n`. + * **Time and Size** - Messages received from the device are split by time interval in milliseconds and maximum message size in bytes. + * **Do Not Split** - Messages received from the device are not automatically split. -* `0#ServiceUUID#CharacteristicUUID` - Subscribe to characteristic `CharacteristicUUID` from service `ServiceUUID`. -* `1#ServiceUUID#CharacteristicUUID` - Unsubscribe from characteristic `CharacteristicUUID` from service `ServiceUUID`. -* `2#ServiceUUID#CharacteristicUUID` - Read characteristic `CharacteristicUUID` from service `ServiceUUID`. -* `3#ServiceUUID#CharacteristicUUID` - Write to characteristic `CharacteristicUUID` from service `ServiceUUID`. +9. In the **Characters Added to Message** field, specify the character or characters marking the end of the message sent to the device, for example, `\r\n`. +10. In the **Encoding** field, select the message encoding. +11. Click **Add Device**. -### Response +## TCP/IP Server -* `CharacteristicUUID#Response` +TCP/IP clients allow you to host connections over the network. + +### Configuring TCP/IP Servers + +To add a TCP/IP server, perform the following steps: + +1. In Workstation Management, navigate to the **Devices** section on the **Station Detail** page. +2. Click **Add Device**, and then select **TCP/IP Server**. +3. In the **Device Name** field, enter an identifying name for the device. +4. Optional: Select or create a class to help you manage your devices. +5. Click **Next**. +6. Configure the following connection parameters: + + * **Port** - The port on which the TCP/IP Server is initalized. The value must be in the range of `0-65535`. + +7. Click **Next**. +8. In the **Split Incoming Message By** section, select one of the following options: + + * **Delimiter** - Messages received from the device are split by the specified character or characters marking the end of the message, for example, `\r\n`. + * **Time and Size** - Messages received from the device are split by time interval in milliseconds and maximum message size in bytes. + * **Do Not Split** - Messages received from the device are not automatically split. + +9. In the **Characters Added to Message** field, specify the character or characters marking the end of the message sent to the device, for example, `\r\n`. +10. In the **Encoding** field, select the message encoding. +11. Click **Add Device**. ## Printers You can integrate your Workstations with printer devices. -### Configuration in Management UI +### Configuring Printers To add a printer device, perform the following steps: -1. Navigate to the **Devices** section on the **Station Detail** page. -2. Click **Add Device** and select **Printer**. -3. Enter the exact device name as it is displayed in your operating system's device manager. +1. In Workstation Management, navigate to the **Devices** section on the **Station Detail** page. +2. Click **Add Device**, and then select **Printer**. +3. In the **Device Name** field, enter an identifying name for the device. +4. Optional: Select or create a class to help you manage your devices. +5. Click **Next**. +6. Enter the exact device name as it is displayed in your operating system's device manager. +7. Click **Add Device**. ### Message Syntax @@ -193,4 +313,4 @@ The sample print command `P#TESTHELLO#RAW#aGVsbG8=` contains the following eleme 3. `TESTHELLOFILE` (file name) - Name assigned to the print job. The client uses this to create the temporary file (for example, `TESTHELLOFILE.prn`) before sending it to the printer spooler. 4. Separator 5. `RAW` (format type) - Tells the Workstation Client that the following data is a Raw Printer Command (such as ZPL for Zebra printers, EPL, or PCL) rather than a standard document like a PDF or a Word file. Printing in RAW bypasses the standard printer drivers' formatting. It sends the exact code the printer needs to generate labels, barcodes, or specific layouts. -6. `aGVsbG8=` (payload) - A data string encoded to Base64. Base64 decoded, it translates to the text `hello`. If you are testing this and the printer is not reacting, verify that the string you are encoding in Base64 matches the specific language your printer speaks. For example, a Zebra printer cannot process a plain text `hello` unless it is wrapped in ZPL commands like `^XA^FO50,50^A0N,50,50^FDhello^FS^XZ`). +6. `aGVsbG8=` (payload) - A data string encoded to Base64. Base64 decoded, it translates to the text `hello`. If you are testing this and the printer is not reacting, verify that the string you are encoding in Base64 matches the specific language your printer speaks. For example, a Zebra printer cannot process a plain text `hello` unless it is wrapped in ZPL commands like `^XA^FO50,50^A0N,50,50^FDhello^FS^XZ`. diff --git a/content/en/docs/workstation/management/wks-management-settings.md b/content/en/docs/workstation/management/wks-management-settings.md index 28ed38e854a..f297c3d3e39 100644 --- a/content/en/docs/workstation/management/wks-management-settings.md +++ b/content/en/docs/workstation/management/wks-management-settings.md @@ -12,22 +12,18 @@ Navigate to the **Settings** page in a workspace to configure settings that are ## Log Settings -Log settings are available in Workstation Management at **Settings > Log Settings**. - The Workstation Client always stores logs to the file system it is installed on (for more information, see [Troubleshooting the Workstation Client](/mendix-workstation/troubleshooting-workstation-client/)). No logs are send to the Workstation Management. However, you can configure the log level and retention policy of all the Workstation Clients that are registered to stations in the workspace. -{{< figure src="/attachments/workstation/wks-settings1.png" class="no-border" >}} - ### Log Level -Configure the log level of the logs stored by the Workstation Client(s). +Configure the log level of the logs stored by the Workstation Clients. -* Info (default) - Logs normal operation and key application events. For example, the time when the Client was launched or terminated. -* Warn - Info logs and potential issues or suboptimal conditions. For example, if a request to refresh the Client's configuration timed out. -* Error - Warning logs and visible problem, something is not working as expected. For example, if a port to connect to a device is already in use. -* Debug - Error logs and detailed internal state for developer diagnostics. For example, requests to the Workstation Management, communication with devices. +* **Info** - This is the default log level. Logs normal operations and key application events. For example, the time when the Client was launched or terminated. +* **Warn** - Logs potential issues, suboptimal conditions, and other situations that require attention, for example, if a request to refresh the Client's configuration timed out. +* **Error** - Logs visible problems where something is not working as expected, for example, device failures. +* **Debug** - Logs detailed internal states for developer diagnostics, for example, requests made to the Workstation Management, or communication with devices. -By default, the unregistered Workstation Client is set to the **Debug** log level. After the client is registered, the log level as configured in the Workspace settings is applied. +By default, unregistered Workstation Clients are set to the **Debug** log level. After a Client is registered, the log level as configured in the Workspace settings is applied. ## Retention Policy @@ -37,10 +33,6 @@ Modify these settings to the needs of your logging policy, especially if you req ## Client's Auto-Refresh {#auto-refresh} -Auto-refresh settings are available in Workstation Management at **Settings > Client's Auto-Refresh**. - -{{< figure src="/attachments/workstation/wks-settings2.png" class="no-border" >}} - By default, the Workstation Client operates in auto-refresh mode. That is, any changes made to the configuration in Workstation Management are immediately reflected in the Client. To change this behavior, change the **Auto-Refresh Mode** setting to **Off**. You can then force the configuration to refresh by clicking **Refresh on Computer** in Workstation Management, or by clicking **Refresh** in the Workstation Client. @@ -49,8 +41,12 @@ The **Check Interval** setting is only available when the auto-refresh mode is e ## Local Device Testing -Local device testing settings are available in Workstation Management at **Settings > Local Device Testing**. +When enabled, this allows local device communication between the Workstation Client and Workstation Management App to use the **Test Your Station** feature of Studio Pro. You can use this option to test your devices. + +## Delete Workspace -{{< figure src="/attachments/workstation/wks-settings3.png" class="no-border" >}} +The option to delete a workspace is available only to the workspace [Owner](/mendix-workstation/management-team/#user-roles). -By default, the Workstation Management is pre-configured as an allowed app to connect to the Workstation Client on the **Test your Station** page in a workspace. To disable this setting, toggle it off. \ No newline at end of file +{{% alert color="warning" %}} +Deleting a workspace cannot be reverted. The entire repository and all associated cloud environments are deleted permanently. Selecting this option makes the project inaccessible to all team members, including the workspace Owner. +{{% /alert %}} \ No newline at end of file diff --git a/content/en/docs/workstation/management/wks-management.md b/content/en/docs/workstation/management/wks-management.md index 8a854da6e3b..fc774e3a023 100644 --- a/content/en/docs/workstation/management/wks-management.md +++ b/content/en/docs/workstation/management/wks-management.md @@ -15,10 +15,12 @@ To start using Mendix Workstation, you must first create a workspace and a stati {{< figure src="/attachments/workstation/wks-install1.png" class="no-border" >}} -3. Enter a name for your new workspace, and then click **Create Workspace**. +3. Enter a name for your new workspace, specify the environment type (**Test**, **Acceptance** or **Production**), and then click **Create Workspace**. {{< figure src="/attachments/workstation/wks-install2.png" class="no-border" >}} + Environments created with the Test environment type have [developer mode](/mendix-workstation/management-stations/#developer-mode) enabled by default for easier testing. Changing the environment type after creation does not enable or disable developer mode. + 4. After the workspace is created, in the **Stations** page, click **Create a New Station**. {{< figure src="/attachments/workstation/wks-install3.png" class="no-border" >}} diff --git a/content/en/docs/workstation/troubleshooting/wks-troubleshooting-mgmt.md b/content/en/docs/workstation/troubleshooting/wks-troubleshooting-mgmt.md index dd2a21b3982..a2fa9650517 100644 --- a/content/en/docs/workstation/troubleshooting/wks-troubleshooting-mgmt.md +++ b/content/en/docs/workstation/troubleshooting/wks-troubleshooting-mgmt.md @@ -10,13 +10,13 @@ weight: 30 This document provides troubleshooting instructions for some potential issues related to Workstation Management. -## Station Status of Unlinked Workstation Client Is Still "Computer Registered" +## Station Status of Deregistered Workstation Client Is Still "Computer Registered" This issue might occur if your Workstation Client could not establish a connection to the Workstation Management, for example, because the computer was not connected to a network. ### Solution -Manually unregister the station in Workstation Management. +Manually deregister the station in Workstation Management. ## Workspace Owner Account Deactivated diff --git a/content/en/docs/workstation/wks-connector.md b/content/en/docs/workstation/wks-connector.md index ae9d0ae644f..a31c0f86916 100644 --- a/content/en/docs/workstation/wks-connector.md +++ b/content/en/docs/workstation/wks-connector.md @@ -84,7 +84,7 @@ You can invite other Workstation Management users to your workspace to share con To invite a user, click **Team** in the left navigation menu, then click **Invite Team Member**. Enter the user's email address and select a role. For more information about the available roles, see [Managing the Team](/mendix-workstation/management-team/). -To change a user's role or remove them from the workspace, click the three-dot icon in the right column of the user list. This action requires the Owner or Workspace Admin role. +To change a user's role or remove them from the workspace, click the three-dot icon in the right column of the user list. This action requires the Owner or workspace Admin role. ## Getting Started with Custom Logic for Device Interaction diff --git a/content/en/docs/workstation/wks-quickstart.md b/content/en/docs/workstation/wks-quickstart.md index aa3c41f4f28..894da83f14e 100644 --- a/content/en/docs/workstation/wks-quickstart.md +++ b/content/en/docs/workstation/wks-quickstart.md @@ -36,10 +36,12 @@ A *station* represents a workstation on the shop floor. It can connect to one or {{< figure src="/attachments/workstation/wks-install1.png" class="no-border" >}} -3. Enter a name for your new workspace, and then click **Create Workspace**. +3. Enter a name for your new workspace, select **Test** as the environment type, and then click **Create Workspace**. {{< figure src="/attachments/workstation/wks-install2.png" class="no-border" >}} + Environments created with the Test environment type have [developer mode](/mendix-workstation/management-stations/#developer-mode) enabled by default for easier testing. Changing the environment type after creation does not enable or disable developer mode. + 4. After the workspace is created, in the **Stations** page, click **Create a New Station**. {{< figure src="/attachments/workstation/wks-install3.png" class="no-border" >}} @@ -145,7 +147,7 @@ The device, which will be used to connect to the TCP/IP server running in Workst After configuring the server and client pair, test their connectivity by performing the following steps: -1. In the left navigation menu of the current workspace, click **Settings**, and ensure that the **Enable Local Device Testing** toggle is set to **On**. +1. In the left navigation menu of the current workspace, click **Settings**, and ensure that the **Enable Local Device Testing** setting is enabled. 2. In the left navigation menu, click **Test Your Station**. The page refreshes and displays a list of all your devices. This includes detected smart card readers available on your computer if you did not [disable detecting card readers](#create-workspace). diff --git a/static/attachments/workstation/wks-install2.png b/static/attachments/workstation/wks-install2.png index 96c9b73d60b..78cecaa869f 100644 Binary files a/static/attachments/workstation/wks-install2.png and b/static/attachments/workstation/wks-install2.png differ