Kk wks 38 updates#11410
Conversation
| {{< 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**. |
There was a problem hiding this comment.
Test type workspaces have developer mode for stations turned on by default
| {{< 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**. |
There was a problem hiding this comment.
Changing the type from test to anything else won't change the developer mode setting. (Won't deactivate it.) And vice versa.
|
|
||
| #### Device Settings | ||
|
|
||
| ##### Configuration in Management UI |
There was a problem hiding this comment.
Explain each field separately - for Maia.
|
Have a section "Accessing Workstation Management" for the benefit of AI agents. |
|
|
||
| Refer to [Message Syntax - Card Readers](/mendix-workstation/device-syntax/#card-readers) for a more in-depth explaination how to communicate with card readers. | ||
|
|
||
| ### Serial Port Devices |
There was a problem hiding this comment.
Static vs dynamic port assignment, different methods depending on use case. Cf demo. Static using com ports, dynamic - pnp id or manufacturer.
|
Station Details - toggles removed/replaced (UI changed). Search for Toggles and replace. |
|
Review Settings page. |
|
Developer mode - no Ctrl+I, delete line. Plus cf. environment type |
|
Unlink client > Deregister client |
| 4. Optional: Select or create a class to help you manage your devices, for example, *Building A Printers*. | ||
| 5. Specify the information required to connect to the device. | ||
|
|
||
| The required information depends on the type of the device. For some devices, like printers, you must only specify the device name. For others, like Serial Port devices, you can use a variety of identifiers such as serial numbers, manufacturer names, and others. |
There was a problem hiding this comment.
"For others, like Serial Port devices, you can use a variety of identifiers such as serial numbers, manufacturer names, and others." Add a dedicated section for serial devices. Printers cannot be added that way.
Just document here that the "printer name" must be filled with the exact name as in the OS printer settings
|
|
||
| ##### Card Readers | ||
|
|
||
| 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. |
There was a problem hiding this comment.
as discussed, pls. update this section "Auto detecting card readers is enabled by default. This setting can be configured on a Station page by toggling Detect Card Readers."
- is disabled by default
- Go to station detail page --> 3-dot menu --> edit station --> set checkbox and save
And all other places where this "toggl" is mentioned
Same for debugger mode toggl
|
|
||
| ### Message | ||
|
|
||
| A print command, for example, `P#TESTHELLO#RAW#aGVsbG8=`. |
There was a problem hiding this comment.
TWS-919 contains further explanations of the message format that should be added here:
Message format:
P#PrintJobDocName#Format#DataPayloadInBase64: Submit a print job.S: Get printer status and queued jobs.C#JobId: Cancel print job.
Response format:P#DocName#JobId: Print job accepted by OS print interface.S#State#StateReason1,...#NumJobs#JobId1:JobName1:JobState1,...: Printer state and job list summary.E#ErrorMessage: Error.
Example: P#TESTHELLO#RAW#aGVsbG8=
Breaking down the print command
- P (command prefix): tells the Workstation Client that the incoming instruction is a Print command
-
separator
- TESTHELLOFILE (filename): name assigned to the print job. The client uses this to create the temporary file (e.g., TESTHELLOFILE.prn) before sending it to the printer spooler
-
separator
- RAW (The Format Type): Tells the Workstation Client that the data following it is Raw Printer Commands (such as ZPL for Zebra printers, EPL, or PCL) rather than a standard document like a PDF or a Word file. By printing in "RAW," bypasses the standard printer drivers' formatting. It sends the exact code the printer needs to generate labels, barcodes, or specific layouts.
- aGVsbG8= (The Payload): Data string encoded to Base64. Base64 decoded, it translates to the text: 'hello'. If you are testing this and the printer isn't reacting, double-check that the string you are encoding in Base64 matches the specific language your printer speaks (e.g., a Zebra printer won't know what to do with plain text "hello" unless it's wrapped in ZPL commands like ^XA^FO50,50^A0N,50,50^FDhello^FS^XZ).
|
|
||
| Mendix Workstation provides detailed usage reports that show how stations are being used across your different workspaces and company. This helps you understand and optimize your Workstation deployment. | ||
|
|
||
| Workstation Clients automatically report their daily active usage to the server, tracking which stations were used and on which days. This data powers the usage reports, giving you valuable insights without extra effort. |
There was a problem hiding this comment.
Note: currently, the report is indeed tracking "active stations". Will change to "active Workstation Clients" as next release i.e. 4.0 GA.
| ## Accessing the Usage Reports | ||
|
|
||
| You can access the Usage Reports by performing the following steps: | ||
|
|
There was a problem hiding this comment.
Add:
3. To view a report of all workspaces that are owned by your company, you must have the Mendix admin role assigned in ControlCenter. TO view the report, go to Workstation Management and click the Company Usage Report tab.
Screenshot can be created from test environment.
2 participants
No description provided.