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 Connect
- :
- FlexNet Connect Forum
- :
- Profile info by version
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
Apr 19, 2005
07:19 AM
Profile info by version
I'm suggesting this blindly, having not checked if this is possible now.
When viewing "default profile" data collected from the Update Service node in InstallShield 10.5, I'd like to be able to view by product and version. For example, I may collect info on version 1 and you may have Windows 98. Then when I release version 2 X years later, you may then have Windows XP, etc. I need to keep a tab on the profile data to target my resources by ensuring the profile data is updated/recorded with each version.
When viewing "default profile" data collected from the Update Service node in InstallShield 10.5, I'd like to be able to view by product and version. For example, I may collect info on version 1 and you may have Windows 98. Then when I release version 2 X years later, you may then have Windows XP, etc. I need to keep a tab on the profile data to target my resources by ensuring the profile data is updated/recorded with each version.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 19, 2005
07:45 AM
The profiles are per product, though you can create your own profiles to manage instead. Two ways come to mind... note: these haven't been completely thought through yet. 🙂
1. The way it is now, no, the change in version would write a new value to the server. However, you could very well write your own profile item, the item name being say "Version1/Win98" and the value being "updated". Your next version could then create a "Version2/WinXP" key with value "updated".
2. Think classic INI files, you could create your own [Version1] section with key OS and "Win98" value. With version 2, you would then create a new [Version2] section with "WinXP" as the value. [Version1] and [Version2] would each be profiles attached to your product.
Without pausing to think it over, I'd go for #2 honestly. At first blush, it makes the most sense and works the way the profiles were designed.
KellyF
1. The way it is now, no, the change in version would write a new value to the server. However, you could very well write your own profile item, the item name being say "Version1/Win98" and the value being "updated". Your next version could then create a "Version2/WinXP" key with value "updated".
2. Think classic INI files, you could create your own [Version1] section with key OS and "Win98" value. With version 2, you would then create a new [Version2] section with "WinXP" as the value. [Version1] and [Version2] would each be profiles attached to your product.
Without pausing to think it over, I'd go for #2 honestly. At first blush, it makes the most sense and works the way the profiles were designed.
KellyF