Hi @pavol_holes ,
As noted in my other reply 16.01.3 will not be interpreted as 16.1.3, the zero is significant in our versioning system. Any 2020 R2.1 release will be 16.10.0 or similar, Any 2020 R2 release will be 16.00.0 or similar.
Regards,
Peter...
Hi @pavol_holes ,
The compressed (three part) version number always includes the two digits in the second part so it does actually end up as 16.01.3. Your example is correct, that will end up as 6.13.0 (although build numbers always start at 1).
The ...
Hello Pavol,
Versioning of FlexNet Manager Suite binaries utilizes a four part numbering scheme:
Major.Minor.Release.Build
So that will give 16.0.1.3 for your example. The final part is the build number which is for internal use only, for customers a...
Hello Jim,
Recommendations for purchases can always be re-calculated via selecting them in the Unprocessed Purchases grid and selecting the Recalculate button.
The specific scenario you call out is interesting. I'm not aware of SKUs rolling forward w...
Hello Jim,
The recommended license calculation for unprocessed purchases does indeed have many variables involved. As you not the SKU is indeed heavily involved in this. When a purchase has a known SKU from our Content libraries it will consider lice...
