Terminal Setup
First thing to do for setup the terminal account
Receive from package
Here you will get a few things from the box:
HKM.ServeBox - the inworld serve box to contain all the packages from your business. We will find other similar names from that aka Release Server, HKM.Warehouse ....
LICENSE - put this into each package, that will be delivered to each customers. Make sure they are set to (no transfer)(copy) or (no transfer)(no copy) as they are finalized.
LICENSEWORKER - optional helper script from the LICENSE
VendCore - vending machine core engine. You will need to use that for each vending machine that made by your own.
VendExt - the extension scripts that provide more functionality for gift cards and membership related features for the vending machine.
Keep in mind that you have to keep your package box after you have unloaded the content. First is to rez the start up box and your account register. If you are upgrading from the free version to the paid version, you will be notified with in your instant messages.
Business Membership Registeration
Use HKM Inworld Terminal to register and say “loss pass” when you loss your password.
STEP I
Issuance of a new product
Issuing a new product MUST login to the system and choose the tab NEW LINE. All brand new products must start from there.
Product code is a secret that people should not able to guess right and it is not the same from the package name. Product code cannot contain “;”, “‘”, “`”, or “%”.
Package name is the object name that will be constantly be delivered from the system and its naming method must be complied with the following rules. ( Capital letters, uncap letters, numbers, and dot. DO NOT USE “;”, “‘”, “`”, or “%”.)
Naming package name with your version number must be careful. Once you add the version into the package name the package name will be kept for the system to deliver this package item from the server box. So you should not add version name on it unless you want to create a specific series of the product in a whole version. The one constant number such as 1 , II, III ,VI can be used for 15-100 times because you have developments during these versions.
VERSION is the field you will put in the very beginning number. I could be “1.00”, “0.01” or “0.1”. Try not to put the number to be too big otherwise it will be hard to renew the version later. The initial version number is best to be as low as possible.
STEP II
How to make a BOXED item?
Since you have already finished the procedure above now its time to create your first boxed item inworld. You will find LICENSE in the retail box where you need to add this script into any package once. Then you must check on the permission of LICENSE.
MUST set LICENSE to NO TRANSFER to make it effective
Another part of the LICENSEWORKER is a helper tool to identify all the internal items and show them on the screen for further editings in anyways. Finally create an empty script as the installation script under your title inworld. We can name it whatever we can but its better to mark it relatively for easy management then copy and paste the installation code from the platform.
The install script have recorded the basic version and naming key information so that SHOULD NOT SHARE TO others in anyways. Now drop the script inside the package other than LICENSE or LICNENSEWORKER will be removed.
Now fill out the information from what you have issued from the new product. These information MUST match exactly from what you have previously added that new item. Then you can save it and drop this installation script into the package box.
It will responded accordingly if you have added the information correctly to the script. Now you can add whatever products or creations into this package. After you have done it then you are finished and pick up to your inventory.
From the inventory you can now drag and drop this package into the server box. Touch the server box and the indication light will change to yellow and it shows you that package is successfully verified on the system and this package is ready to be sent out anytime to the customers.
STEP III
How to make an update or issuing a new update from the existing product?
Open from the previous Boxed object and replace the newer items with proper permissions make sure that they are all ready. We suggest the proper permission as the following:
For resellers package AKA [PRO]:
LICENSE (notransfer)(copy)
Other items (nomod)(transfer)(copy)
For retailers package:
LICENSE (notransfer)(copy)
Other items (nomod)(notransfer)(copy)
From the installation script with the same information about the product and the version. Change the version with a bigger number.
The version MUST be a bigger one then add this script into the package that you are about to update.
Now pick up the package and rez the package on the ground to have the script runs. Wait until the appropriate responding information shows on the screen then you can add the package into the terminal.
Before adding the new package into the terminal please remove the old package with the same name manually. Otherwise there will be a duplication from the inworld serve box.
Drag and drop the package into the serve box and touch the box again to finalize it.
Things to do Right After Issuing the New Product
Go into the system and see RELEASE. Find the product code which is just updated on the system and click DEPLOY. The inworld serve box will deliver the new package to the existing customers.
System migration
Adding each customer uuid and using semi colons to separate them. It allows to import customers in one take. It will able to filter the duplicated customer registrations for the same product.
Definitions:
Terminal - the online console for to work on each package.
Serve Box - the inworld box that placed in a secured place without auto return.
Last updated