Special Notes

This section contains special information pertaining to FlexNet Operations.

Plug-in Upgrade Needed for High-Speed File Uploads

If you intend to use the high-speed upload option to upload files, upgrade the Aspera plug-in to Aspera Connect 3.10.0 or later.

Best Practice for Uploading New File Versions for Software Delivery

The following practice helps to prevent the delivery of “stale” file content to your customers.

When you upload a new version of a file (or package) whose previous version exists in the Software Delivery system, best practice is to give the new file version a unique name, different from the name of the existing file version. (For example, use a version number in the file name.) Try to avoid uploading a file using the same name as the existing file so that the existing file is overwritten.

If you must upload a new file using the same name as the existing file, delete the existing file and wait 10-15 minutes before uploading the new version. This process will reduce the probability of re-caching the old content.

Handling UI Conflicts When Using a Custom CSS for the End-User Portal

When you use your own CSS to customize the look of the End-User Portal, sometimes your custom CSS code conflicts with existing Revenera CSS code that is used to define certain buttons, pages, and other UI elements. When conflicts occur, handle each case individually, determining the basis of the conflict and adjusting the custom CSS as needed. If you require assistance, contact Revenera Technical Support (see Revenera Resources).