Conversation
| * **AppKeyPair** - A persistent entity to store the app's key pair. The public key needs to be entered in the corresponding app in the Workstation Management. | ||
|
|
||
| ### Using the Nanoflows and Actions | ||
| ### Using the Nanoflows and Actions {#java-actions} |
There was a problem hiding this comment.
Actions are JavaScript Actions, not Java
| Call `Unsubscribe` to end a subscription. | ||
|
|
||
| #### UnsubscribeByContext | ||
| #### SetupDevice |
There was a problem hiding this comment.
After discussion today, we renamed this to GetCreateDevice. Same behavior, hopefully easier to understand.
|
|
||
| Call this action to unsubscribe and completely disconnect from a specific device. | ||
|
|
||
| #### Initialize |
There was a problem hiding this comment.
Initialize needs to be called by something in order to set up communication with the Workstation Client.
Users shouldn't ever need to call this directly. It should be automatically called from within GetStation or GetCreateDevice. Users will need to pass it to GetCreateDevice as initialize for it to be called. This should be well documented in the action parameter description.
|
|
||
| #### GetStation | ||
|
|
||
| Call `GetStation` to retrieve configuration of the current Client computer by using the Workstation Client. `GetStation` can be used multiple times, but it queries the Workstation Client only the first time. The following calls return the current object loaded in the session. If connection with Workstation Client does not work, `GetStation` returns an empty object. |
There was a problem hiding this comment.
Call `GetStation` to retrieve the current Workstation Client configuration and devices. Creates and returns a station object with a linked device object per peripheral.
|
|
||
| Call `GetStation` to retrieve configuration of the current Client computer by using the Workstation Client. `GetStation` can be used multiple times, but it queries the Workstation Client only the first time. The following calls return the current object loaded in the session. If connection with Workstation Client does not work, `GetStation` returns an empty object. | ||
|
|
||
| If your microflow references a peripheral module (that is, a reusable module which supports a specific peripheral device), you do not need to call `GetStation` to reference it. Instead, you can initialize the peripheral module by calling `Initialize`. |
There was a problem hiding this comment.
If you need to interact with a specific device, prefer getting it via `GetCreateDevice` instead. It has a more convenient API, allows specialization and avoids creation of station and device objects that may not be needed.
|
|
||
| Call this action to unsubscribe and completely disconnect from a specific device. |
There was a problem hiding this comment.
Call this action to disconnect from a specific device.
Does not unsubscribe anything.
| @@ -86,46 +75,104 @@ The domain model contains the following entities: | |||
| * **Device** - A list of devices associated with the station; includes device names and properties required to achieve a connection (non-persistent entities). | |||
There was a problem hiding this comment.
* **Station** - A non-persistent entity representing the Workstation Client configuration.
* **Device** - A non-persistent entity representing a connectable peripheral device. Includes name, class and available/connected/error states. Specialize this to maintain your device specific state.
| * `timeout` | ||
|
|
||
| The callback nanoflow must have the following parameters: | ||
| #### SubscribeToObjectChanges |
There was a problem hiding this comment.
SubscribeToXxx might be better to come near the end. I see these as low-level APIs. Most users shouldn't need these. GetCreateDevice should be enough.
No description provided.