This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Operations
- :
- FlexNet Operations Forum
- :
- Variable versions
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 27, 2009
09:42 AM
Variable versions
When configuring a new feature, you are of course given the choice of entering a 'fixed' version or a date-based version. The date-based version can be configured at entitlement time, while the 'fixed' version cannot.
Can operations be configured so that the numeric version can be used and configured at entilement time? If not through the Flex-Ops user interface, is this possible using the Web Service interface?
Can operations be configured so that the numeric version can be used and configured at entilement time? If not through the Flex-Ops user interface, is this possible using the Web Service interface?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 29, 2009
05:05 PM
I gather that once a feature is in the Deployed state, you can't change its fixed version number. I imagine you could dynamically create features with specific fixed versions using the publisher web services, but then you'd presumably need to create a product that includes the new features (a Deployed product can't change its included features), and so forth.
There might be some FLEXnet Operations trick that I'm not aware of; but one option that comes to mind is to put the custom entitlement-time or fulfillment-time version in VENDOR_STRING or SN, and then have a little checkout filter in the FLEXenabled application code to test that value...
There might be some FLEXnet Operations trick that I'm not aware of; but one option that comes to mind is to put the custom entitlement-time or fulfillment-time version in VENDOR_STRING or SN, and then have a little checkout filter in the FLEXenabled application code to test that value...