<menu path> <link to F1 content>
<intro text>Business Objects allow third-party developers and DATASCOPE Solution Providers (DSPs) to build external applications and enable third-party applications to interact with the DATASCOPE WMS application.
Business Objects can be used from within a Plugin architecture or external applications. For more information, refer to Custom Plugins Module.
An additional module must be purchased to use Business Objects from an external application, but the module is NOT required when using it within Plugins.
| Info |
|---|
Note: this is not standard with your FASTTRACK WMS purchase and must be requested as an additional module with DATASCOPE WMS Premium. |
| Info |
|---|
If you don’t like reading, you can watch the video. |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
<link to YouTube video> <link to PDF doc on my OneDrive> |
Try it!
<content>What are Business Objects?
Encapsulation describes the binding and the hiding of the underlying implementation of an object’s data and operations. The data is wrapped in a particular type of protocol header. The set of operations that is accessible is the object’s interface.
Business Objects are the encapsulation of a system (or business logic) within our DATASCOPE WMS software.
On a transaction level, a particular object can be called to do a particular task within the system Our Business Objects have also been built as backward compatible, as this is a key requirement for using Business Objects in warehouse environments. When newer software versions are released, existing custom software can still operate on the newer versions using our Business Objects.
Our Business Objects follow a structured and transactional approach since they are aligned with the business logic within our core system. These Business Objects are extensively utilized in our core services within our core software.
Module Licensing
Business Objects are a separate Module within the product. It must be licensed separately when purchasing the product. However, one exception is when you call Business Objects from within our Plugins framework.
When calling a Business Object from within our Plugin architecture, you do not require it to be licensed – it is free to call from that architecture. For more information on Custom Plugins, refer to the Custom Plugins Series.
Licensing is then based on our Named User module. Therefore, if you purchased 50 Named User licenses, you will be getting a 50-user Business Objects Module.
To confirm your licensing is correct:
On the DATASCOPE WMS Server, browse to the Licensing folder in your File Explorer.
It will typically be located under C: / DatascopeLicense / License.xml.
Open the License.xml file and search for WMS_ENET_OBJECTS.
If you do not have WMS_ENET_OBJECTS within your license file, then you are not licensed to use this. Contact your local DSP (DATASCOPE Solution Provider) to obtain the Business Objects License.
User Licensing
The user licensing and permissions to use the WMS E.Net Objects module must also be activated.
Open DATASCOPE WMS
On the Ribbon Bar, browse to Settings / User Licensing
In the data grid, you will see a list of all the named users that are licensed with two additional columns called Licensed and E.Net Object Licensed.
The Licenced column is for your standard DATASCOPE WMS license.
The E.Net Object Licensed column is for E.Net Object users. This column will be greyed out if you are not licensed for the Business Object module.
Select the check box per user to activate the E.Net user license per user level.
| Info |
|---|
Note: A user can either be a WMS user, just an E.NET user, or both. |
At the bottom of the User License screen, you will see a summary of the number of Named Users you are licensed for, as well as how many are in use.
Tools required
The following prerequisites exist to start work with Business Objects.
Visual Studio 2022 IDE
.NET Framework
Module license for E.Net Business Objects
SDK.dll located within our DATASCOPE WMS SDK
A WMS Test Environment
Design Model
Our Business Object framework is built into our Software Developer Kit using Object Oriented programming. If you instantiate a business object, and enter a dot, you will see what properties are available directly within the Visual Studio designer.
The Software Developer Kit has several Class Libraries broken up into various functional areas. Basically, they are broken down into different classes within the SDK, and each class represents a particular functional area, and within the functional areas you have several business objects.
A lot of our Business Objects have types, so there are various types of Business Objects.
For more information on all the different types, refer to the DATASCOPE Business Objects Reference Library