| com.microstrategy.web.objects.EnumWebSubscriptionDeviceSubtype |
| Constants | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| int | SUBSCRIPTION_DEVICE_SUBTYPE_ABSOLUTE | This type of device requires that the actual physical location be completely specified by the user in order to properly define an address | |||||||||
| int | SUBSCRIPTION_DEVICE_SUBTYPE_FIXED | This type of device completely defines the path within its definition In other words, all users using this device will end up using the same location | |||||||||
| int | SUBSCRIPTION_DEVICE_SUBTYPE_OTHER | This value indicates that the device is not a file/print/ftp location | |||||||||
| int | SUBSCRIPTION_DEVICE_SUBTYPE_RELATIVE | When an address corresponding to this type of device is created, the user would need to type in only a path relative to the fixed portion that is specified in the device definition For instance, the device definition could be something like \\network-server\directory1\%%PHYSICAL_ADDRESS%% So the path typed in by the user replaces only the %%PHYSICAL_ADDRESS%% macro | |||||||||
| int | SUBSCRIPTION_DEVICE_SUBTYPE_RELATIVE_MACRO | ||||||||||
This type of device requires that the actual physical location be completely specified by the user in order to properly define an address
This type of device completely defines the path within its definition In other words, all users using this device will end up using the same location
This value indicates that the device is not a file/print/ftp location
When an address corresponding to this type of device is created, the user would need to type in only a path relative to the fixed portion that is specified in the device definition For instance, the device definition could be something like \\network-server\directory1\%%PHYSICAL_ADDRESS%% So the path typed in by the user replaces only the %%PHYSICAL_ADDRESS%% macro