Skip to content

Commit 572faf5

Browse files
Updates to Workstation docs
1 parent 3fda663 commit 572faf5

3 files changed

Lines changed: 17 additions & 3 deletions

File tree

content/en/docs/workstation/wks-batch-registration.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,10 @@ The registration process is a necessary first step when enabling this crucial fu
1313

1414
Mendix Workstation supports both individual registration of local Workstation clients, and bulk rollouts for large production environments.
1515

16+
{{% alert color="info" %}}
17+
After a Workstation Client is registered, any changes that you make in Workstation Management (such as adding new devices, or setting the **Detect Card Readers** toggle to **Off**) will be immediately displayed in the Client. To change this behavior, see [Client's Auto-Refresh](/mendix-workstation/installation/#auto-refresh).
18+
{{% /alert %}}
19+
1620
## Registering a Single Workstation Client
1721

1822
If you are developing or testing Workstation configurations, you can register a single Workstation Client for your local computer by performing the following steps:

content/en/docs/workstation/wks-installation.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -96,14 +96,16 @@ The **Stations** page now shows your station's status as **Computer Registered**
9696

9797
{{< figure src="/attachments/workstation/wks-install10.png" class="no-border" >}}
9898

99+
Any changes that you make in Workstation Management (such as adding new devices, or setting the **Detect Card Readers** toggle to **Off**) will be immediately displayed in the Workstation Client. To change this behavior, see [Client's Auto-Refresh](#auto-refresh).
100+
99101
### Configuring and Testing Virtual Devices
100102

101103
After registering your computer, test your connectivity by creating a pair of virtual devices: a TCP/IP server that will emulate a device, and a TCP/IP client that will connect to the emulated device.
102104

103105
#### Creating a TCP/IP Server
104106

105107
1. Go to [Mendix Workstation Management](https://workstation.home.mendix.com/).
106-
2. In the **Station** page, click **Add Device**.
108+
2. In the **Station Details** page, click **Add Device**.
107109
3. Select **TCP/IP Server** as the **Device Type**, and then click **Next**.
108110
4. In the **Device Name** field, enter **Test Server**
109111
5. In the **Device Class** field, select or create a class (for example, *Virtual*), and then click **Next**.
@@ -119,7 +121,7 @@ The emulated device, a local TCP/IP server listening on port 1705, is added to t
119121
#### Creating a TCP/IP Client
120122

121123
1. Go to [Mendix Workstation Management](https://workstation.home.mendix.com/).
122-
2. In the **Station** page, click **Add Device**.
124+
2. In the **Station Details** page, click **Add Device**.
123125
3. Select **TCP/IP Client** as the **Device Type**, and then click **Next**.
124126
4. In the **Device Name** field, enter **Test Client**, and then click **Next**.
125127
5. In the **Device Class** field, select or create a class (for example, *Virtual*), and then click **Next**.
@@ -153,7 +155,7 @@ Different device types have different requirements for the message syntax. For m
153155

154156
### Quitting the Workstation Client
155157

156-
The **Close** button closes the Client window but does not terminate the application; it continues to run in the background. To completely quit the Client, right-click its icon in the Windows systray and select **Quit**. This action is only available if [Developer Mode](#developer-mode) is enabled. Alternatively, the Workstation Client process can always be stopped via Windows Task Manager.
158+
The Workstation Client runs automatically at system startup. The **Close** button closes the Client window but does not terminate the application; it continues to run in the background. To completely quit the Client, right-click its icon in the Windows systray and select **Quit**. This action is only available if [Developer Mode](#developer-mode) is enabled. Alternatively, the Workstation Client process can always be stopped via Windows Task Manager.
157159

158160
## Advanced Configurations
159161

@@ -186,6 +188,14 @@ Verbosity and thus log file size increases with each log level. To constrain thi
186188

187189
Modify these settings to the needs of your logging policy, especially if you require to keep debug level logs in production for retrospective troubleshooting.
188190

191+
#### Client's Auto-Refresh {#auto-refresh}
192+
193+
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.
194+
195+
To change this behavior, set the **Auto-Refresh Mode** toggle to **Off**, and then force the configuration to refresh by clicking **Refresh on Computer** in Workstation Management.
196+
197+
You can also **Adjust the Check Interval** to specify how often a disconnected Workstation Client should automatically refresh its configuration by polling Workstation Management. By default, this happens every 60 minutes.
198+
189199
#### Local Device Testing
190200

191201
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, navigate to the tab "Local Device Testing" on the **Settings** page and toggle it off.
203 KB
Loading

0 commit comments

Comments
 (0)