I noticed that the activation functions flxActAppActivationSend, flxActAppActivationReqCreate etc. all accept the expiration date as an argument
I tried changing this date making it lesser/greater than the expiry date for the corresponding activation ID that's been set on the operations server but it doesn't seem to have any effect on the license that gets loaded on TS. The expiration date on the fulfillment and the individual feature lines is always what's been set in operations
what is this date argument meant for in that case? I thought it was meant for specifying an earlier expiration than the date set on operations. or maybe there's something I'm missing/doing wrong?
I believe FLEXnet Operations ignores that field; it is used (required, actually) when using the manual response generator, and required when detaching an activatable license from a license server.
