Describes the manner in which an aseptic product is packed and shipped by the manufacturer:

Describes the manner in which an aseptic product is packed and shipped by the manufacturer:

Specify that all samples should be transferred into a specified container upon arrival:

Specify that some samples should be transferred into a specified container upon arrival:

CountSource automatically resolves to ExperimentallyMeasure for tablet model input and to None for all other samples. Count initializes to 0 for all of these cases:

If Mass is given and SolidUnitWeight is known, Count is calculated to resolve automatics:

Specify that the count of the sent samples should be found on the documentation that arrives with the sample:

Specify that the count of the sent samples should be measured upon arrival:

Specify the count of the samples that will be sent:

Update the count of objects in an existing transaction:

Specify a date shipped for each object when generating a transaction:

Specify a date shipped for each object when updating shipping information:

Specify a date shipped for some but not all of the models when generating a transaction.:

Specify a date shipped when generating a transaction:

Specify a date shipped when updating shipping information:

When updating shipping information, Automatic DateShipped will leave the existing date shipped in place, Null will clear the existing date shipped and revert the transaction status to Pending, and a new date shipped will overwrite the old date shipped:

Specify the destination where the samples will be sent:

Specify an expected delivery date for each object when generating a transaction:

Specify an expected delivery date for each object when updating shipping information:

Specify an expected delivery date for some but not all of the models when generating a transaction.:

Specify an expected delivery date for some but not all of the objects when updating shipping information:

Specify an expected delivery date when generating a transaction:

Specify an expected delivery date when updating shipping information:

When updating shipping information, Automatic ExpectedDeliveryDate will leave the existing date expected in place, None will clear the existing date expected, and a new date expected will overwrite the old date expected:

If Count is given and SolidUnitWeight is known, Mass is calculated to resolve automatics:

MassSource automatically resolves to ExperimentallyMeasure for solid model input and to None for all other samples. Mass initializes to 0 gram for all of these cases:

Specify different mass options for each input:

Specify that the mass of the sent samples should be found on the documentation that arrives with the sample:

Specify that the mass of the sent samples should be measured upon arrival:

Specify the mass of the samples that will be sent:

Update the mass of models in an existing transaction:

If multiple transactions are generated, an index is added to the name:

Specify a name for the transaction:

Update the name of existing transactions:

Provider must be specified for models. If provider is specified for products, it must match the supplier of the product:

If no quantities are specified, assumes one of each input:

Specify the quantity of the samples that will be sent:

Specify the allowable difference between received amount and expected amount for any ordered samples:

Indicates that samples will arrive in a sealed container:

Use the ShippedRack option to indicate that a rack will be shipped as part of the order. The compatibility of the rack will also be assessed:

Specify a shipper for each object when generating a transaction:

Specify a shipper for each object when updating shipping information:

Specify a shipper for some but not all of the models when generating a transaction.:

Specify a shipper for some but not all of the objects when updating shipping information:

Specify a shipper when generating a transaction:

Specify a shipper when updating shipping information:

When updating shipping information, Automatic Shipper will leave the existing Shipper in place, None will clear the existing Shipper, and a new Shipper will overwrite the old Shipper:

Specify that some samples are sterile:

Specify a tracking number for each model when generating a transaction:

Specify a tracking number for some but not all of the models when generating a transaction.:

Specify a tracking number when generating a transaction:

Specify a tracking number when updating shipping information:

Specify tracking numbers for each transaction when updating shipping information:

Specify tracking numbers for some but not all of the transactions when updating shipping information:

When updating shipping information, Automatic TrackingNumber will leave the existing tracking number in place, Null will clear the existing tracking number, and a new tracking number will overwrite the old tracking number:

Specify different volume options for each input:

Specify that the volume of the sent samples should be found on the documentation that arrives with the sample:

Specify that the volume of the sent samples should be measured upon arrival:

Specify the volume of the samples that will be sent:

Update the volume of models in an existing transaction:

VolumeSource automatically resolves to ExperimentallyMeasure for liquid model input and to None for all other samples. Volume initializes to 0 gram for all of these case:

Provider is required for model (i.e., non-product) inputs:

Provider must be a Service company for model (i.e., non-product) inputs:

If different ContainerOut is specified for the same model, give a message and fail:

Give a warning if it cannot be determined whether the specified container out is large enough to hold the sample:

If a count if provided that disagrees with the known count of the product, throws an error::

If Count is specified for a kit product, throws an error:

Specifying a count for items will throw a warning and not populate any count-related fields for those models when updating a transaction:

Specifying a count for non-tablets will throw an error when generating a transaction:

When the ShippedRack is not capable of supporting the container in which the product arrives (or if the ordered item is a container), an error is shown indicating incompatability:

If a listed option does not match the length of the transaction object inputs, give a message and return $Failed:

If DateShipped is after ExpectedDeliveryDate, give a message and return $Failed:

If Mass and Count are both given and disagree based on the SolidUnitWeight throw an error:

If a mass if provided that disagrees with the known mass of the product, throws an error::

If Mass is specified for a kit product, throws an error:

Specifying a mass for items will throw an error when generating a transaction:

Specifying a mass for items will throw a warning and not populate any mass-related fields for those models when updating a transaction:

When generating a transaction, if mass or volume is specified as ExperimentallyMeasure, throw a warning that the samples may be transferred to a different container:

When updating a transaction, if mass or volume is specified as ExperimentallyMeasure, throw a warning that the samples may be transferred to a different container:

When generating a transaction, if the same model is specified with differing count options, give a message and return $Failed:

When updating a transaction, if the same model within a transaction is specified with differing count options, give a message and return $Failed:

When generating a transaction, if the same model is specified with differing mass options, give a message and return $Failed:

When updating a transaction, if the same model within a transaction is specified with differing mass options, give a message and return $Failed:

When generating a transaction, if the same model is specified with differing amount options, give a message and return $Failed:

When updating a transaction, if the same model within a transaction is specified with differing amount options, give a message and return $Failed:

If the specified service provider is not recorded for the specified model, give a message that the model will be updated:

If there is no Model[Container, Rack] in the database that can hold the recieved container upright based on its Footprint and Dimensions, return an error:

If any listed options don't match the length of the inputs, give a message and return $Failed:

If a listed option does not match the length of the models in the transaction object inputs, give a message and return $Failed:

If a provider is provided that disagrees with the known supplier of the product, throws an error::

When generating a transaction, if volume is specified for a liquid model but the model does not have density, give a warning that the samples may still be transferred depending on the container it arrives in:

When updating a transaction, if volume is specified for a liquid model but the model does not have density, give a warning that the samples may still be transferred depending on the container it arrives in:

If ContainerOut is specified for a kit product, give a message and fail:

If ContainerOut is specified for an item, give a message and fail:

If a volume if provided that disagrees with the known volume of the product, throws an error::

If Volume is specified for a kit product, throws an error:

If ContainerOut is too small to hold the sample volume, give a message and fail:

Specifying a volume for items will throw an error when generating a transaction:

Specifying a volume for items will throw a warning and not populate any volume-related fields for those models when updating a transaction:

If the name is already in use, throws an error and fails:

If the name is already in use, throws an error and fails:

If the inputs don't match in length, give a message and return $Failed:

Update the quantity of objects in an existing transaction: