access:internet_key_stories
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
access:internet_key_stories [2012/10/10 16:19] 127.0.0.1 external edit |
access:internet_key_stories [2017/10/31 16:47] (current) mikeclapp [Story 4 Site License Capability] |
||
|---|---|---|---|
| Line 55: | Line 55: | ||
| * Deployment Plan to server. | * Deployment Plan to server. | ||
| * Roll smartdirt and windows products to access.agtek.com | * Roll smartdirt and windows products to access.agtek.com | ||
| + | |||
| + | ===== Story 4 Site License Capability ====== | ||
| + | |||
| + | A site license is designed to propagate mobile apps further into companies by removing the barriers to anybody who needs the products in that company. The customer buys a site license rather than individual apps and in return has that products for his site (office) with the only limits being total users per company. There are likely two parts to this, an update to mobile products and a server update with provisioning software changes. | ||
| + | |||
| + | ==== Implementation Thoughts ==== | ||
| + | None of this set in stone because decisions on how to best implement on the server are to be determined. The provisioning method also factors in. | ||
| + | |||
| + | === Provisioning Ideas === | ||
| + | |||
| + | First thought is to have a flag on the company similar to AGTEK Access & Tracking that enables a SmartPlan, SmartTrack, or SmartDirt license ( I don't see us doing RTK under Site license at this point). The mobile apps would likely need to be updated to understand this change and bypass the key selection page entirely when the flag is encountered. One small downside to this approach is future site license types would have to be added as they occur however I don't anticipate many others. | ||
| + | |||
| + | Second though is to create a site license product code that when placed on a key essentially creates a site license for those key codes. The benefit would be that essentially any software that had been enabled to support site licenses could be used. The downside would be inadvertent provisioning with the key code (don't know if it's ever happened) has far more cost. | ||
| + | |||
| + | |||
| + | === App Behavior === | ||
| + | |||
| + | I'm imagining that any app that sees a matching site license indication bypasses the key selection screen entirely and goes directly to files or tracks. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| ===== Future Story ===== | ===== Future Story ===== | ||
access/internet_key_stories.1349885991.txt.gz · Last modified: 2012/10/10 16:19 by 127.0.0.1
Page Tools
