Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

System Setup / Plugin Customization / Plugin Configuration [SET062] .

This plugin is used for importing Tracking ID allocation data from within the LCT Receipt Application in DATASCOPE WMS. Typically for LCT Shipments the Tracking ID allocation information is available in an electronic format.

Typically, this process of allocating tracking IDs is very time-consuming due to the volume of stock. This plugin allows for the injection of logic in a plugin to run a program or some process to perform the Tracking ID allocation.

A simple example, included as a sample below is to allow the operator to import an Excel sheet, containing the Tracking ID allocation information. This is then imported into the system using a Business Object call to WMS within the plugin. Once imported the screen is refreshed and the allocations are visible to the operator to review and finalize the LCT

The popup window is shown below where the operator can perform the import.

image-20240308-090402.pngImage Addedimage-20240202-140907.png
Info

If you don’t like reading, you can watch the video.

Panel
panelIconId1f3a5
panelIcon:movie_camera:
panelIconText🎥
bgColor#DEEBFF

None

None

Try it!

Plugin details

Type

Plugin Name

Interface

Location

Method Name

Location

Method Name

Module

Linked Action

Receiving

LCT Tracking ID Allocation Import

ILCTAllocationImport

DATASCOPE.SDK.PluginInterfaces

DATASCOPE.SDK.PluginInterfaces

Receipt LCT

Import LCT

To develop your own plugin:

Info

Strong development skills are required in order to develop your own plugins.

For more information, refer to What is needed to work with Plugins?

  • Open a Class Library Project within Visual Studio

  • Insert the DATASCOPE SDK

  • Insert the inheritance from the DATASCOPE SDK

  • Select the required Interface.

  • Write your code as per your own requirement.

  • Build it into a single .dll file and save it in the C:/ Program Files / DATASCOPE / DATASCOPE WMS WebAPI / Plugins folder on the server.

  • Test it in the module.

To configure this plugin:

  • From the Main Menu, browse to System Setup / Plugin Customization / Plugin Configuration

  • Select LCT Tracking ID Allocation Import from the Plugin Name drop-down.

  • Select ADDfrom the Action drop-down

  • Enter a Display Name (i.e. LCT Import)

  • Add the applicable DLL - in this case it will be LCTImport.dllcompiled DLL file name, developed by a developer, in the Dll FileName field - for example LCTImport.dll

Info

The DLL file name added into the Dll FileName field must be exactly the same as the .DLL file saved in the C: / Program Files (x86) / DATASCOPE / DATASCOPE WMS WebAPI / Plugins folder.

Info

All the Plugin .DLL files are located on the DATASCOPE WMS server under C: / Program Files (x86) / DATASCOPE / DATASCOPE WMS WebAPI / Plugins. . Refer to https://datascopewms.atlassian.net/wiki/spaces/TG/pages/109051919/What+is+needed+to+work+with+Plugins#Location-of-plugin-files .

  • Select Save to save the configuration.

  • This plugin will now be configured for the Import LCT button on the Receipt LCT screen.

For more information on configuring a plugin, refer to Create a Custom Plugin and link it to a Module or System Setting (configuring plugins) or https://datascopewms.atlassian.net/wiki/spaces/TG/pages/109707274/Developing+your+own+plugins#Configuring-the-plugin-in-the-software

image-20240308-090402.pngImage Removed

To develop your own plugin:

Info

Strong development skills are required in order to develop your own plugins.

For more information, refer to What is needed to work with Plugins?

  • Open a Class Library Project within Visual Studio

  • Insert the DATASCOPE SDK

  • Insert the inheritance from the DATASCOPE SDK

  • Select the required Interface.

  • Write your code as per your own requirement.

  • We build it into a single .dll file and save it in the C:/ Program Files / DATASCOPE / DATASCOPE WMS WebAPI / Plugins folder on the server.

  • Configure and saved the plugin in the system Plugin Configuration screen.

  • Lastly, we tested it in the module.image-20240610-094408.pngImage Added