Browser Access to Simple Search
 
 
Browser Access to Routing Guides
 
 
Browser Access to PropertySets
 
 
Browser Access to Rating
 

 
 

InfoShare
Browser Access to PropertySets

PropertySets are in-memory databases that reside locally InfoShip workstations that allow the data business rules operate on to change dynamically.  Because PropertySets are self-describing, they can be rendered just as well in a browser as they can inside InfoShip.  The behavior of a system can be modified simply by modifying the data in a PropertySet.

One example might be a business rule used for "self-insurance" purposes.  Self-insurance is the concept where a company decides that it will replace the shipped goods up to a certain dollar amount (the self-insurance threshold), but the company charges its customer the same amount the carrier would otherwise charge; beyond the threshold amount, the company opts to insure the goods through the carrier directly.  It is desirable to have the self-insurance threshold maintainable through a means other than modifying the business rule itself (which may be written in VB Script or a Behavior).  The solution would be to store the self-insurance threshold in a PropertySet.  Then, whenever the company needs to modify this threshold amount, the Self-Insurance PropertySet can be opened and the value modified.

Another example would be displaying messages to operators and optionally stopping shipments.  If an order needs to be stopped (for instance, if the customer cancelled the order), the ERP or WMS system is usually the first place to go.  However, often times, such a system is only capable of stopping an order if it hasn't already reached a particular point in the packaging process (such as packed confirm).  Once the order has been completed from an ERP or WMS perspective, the only available option a company might have is to actually call down to the warehouse and have the operator watch for the order and physically pull it from the conveyor.  This is a tedious, error-prone, and time-consuming process.  A much better approach would be to setup an Operator Messages PropertySet that contains order numbers, a message to display to the operator (such as "This order has been held.") and an optional flag indicating whether or not to allow the order to ship.  A screen showing such a PropertySet is shown below.