Esprida LiveControl offers to types of digital content packages: Standard and Generic. What’s the difference?

Generic Content Package
• Used exclusively for the distribution of files or folders to a device through the Esprida LiveControl Agent.

• Simpler to use: The user does not need to have any programing skills to create and distribute the content package. Esprida LiveControl will build the Install, Activate, Deactivate and Uninstall scripts required for the content package.

• Requires the user to enter the destination path for the file or folder when the content package is being uploaded.

• The distribution of the files or folders occurs immediately upon transfer of the files to the device. A generic content package does not run the Activation script and therefore the user will not be required to enter an activation time for the content package like occurs with a standard content package.

• The Deactivation script is never run.
• The Uninstall script will be executed when the content package is ‘Detached’ (Devices Module) or the device is removed from the content schedule (Digital Content module). The Uninstall script will not remove the files or folders that were distributed in the content package. The Uninstall script only removes the content package from the path were is was downloaded and sends a signal to the Esprida LiveControl Server that the package was removed.

Standard Content Package
• The most flexible method for delivering content to a device through the Esprida LiveControl Agent. If it can be done in a script it can be accomplished through a properly coded content package.

• Requires some experience with scripting languages such as VBS, Windows batch files, Linux shell scripting, Perl scripting etc. The user must create the 4 required scripts that will be run for the content package Install, Activate, Deactivate and Uninstall sequences.

• The user has completed control over what actions will occur on the device during Install, Activate, Deactivate and Uninstall sequences.

Can I use environment variables in the path for a Generic content package?
Yes. Environment variables are supported in the path for a generic content package. The path format is:

%Environment_Variable%/folder1/folder2