Offline Sync Add-On purchase options and licensing examples according to the end-user license agreement.
Purchase Options
Offline Sync licenses are sold under the “Offline Sync Add-On” name.
The number of licensed users specifies the number of application users that will work in the offline/disconnected mode. Packs of 10 and 3 users are available for purchase. Make sure to purchase the required number of packs to match the maximum number of the expected offline users.
The following options are available for purchase:
Pack 1
"Perpetual / 10 users / 2 domains" - $995 USD.
Includes twelve months of maintenance updates.
Pack 2
"Perpetual / 3 users / 2 domains" - $375 USD
Includes twelve months of maintenance updates.
The license is perpetual.
The custom domain names are specified when the Offline Sync activation code is registered.
The “localhost” domain is included with each license.
The licensed number of users and custom domain names cannot be changed after the Offline Sync license has been issued.
Offline Sync license can be purchased on behalf of another entity.
The owner of the license must register the product activation code at https://my.codeontime.com to claim ownership.
Licensing Example
The following examples are provided to explain the licensing terms and integration process.
Example 1
Organization Acme performs on-site food safety inspections. Acme employs twenty auditors. Acme purchased Code On Time app generator for their IT department to create an online application supporting the data collection by auditors.
Five auditors work in remote locations without Internet access. They used to take notes on paper and enter collected data when online connection was available.
Acme purchased a perpetual Offline Sync license for 6 users (two packs of “"Perpetual / 3 users / 2 domains").
Developers have configured an application page to list data that needs to be available in offline/disconnected mode. The page is marked as “offline”. Offline Sync Add-On is enabled in the application. All application users have access to the “offline” page. The “Offline” membership role was assigned to five users.
Five auditors with the “Offline” role have their account data and the front-end code installed on the device as soon as they sign in. Subsequent navigation requests to the application always work with the offline data and code. Auditors periodically synchronize to submit the audit data to the headquarters when they have a reliable internet connection.
Other auditors work with the online data and front-end at all times. The audit data is immediately available to the headquarters.
The audit application was deployed to the server with app1.food-audit-gurus.com address. The IT department has specified the domains app1.food-audit-gurues.com and app2.food-audit-gurus.com when claiming their Offline Sync license. They are planning to use the second domain name to build the offline time tracking application for the auditors. Developers can test the app in the offline mode since the localhost domain is included in the license.
Application administrators easily manage the offline capability of users by adding and removing the “Offline” role.
Example 2
City manager has hired an independent developer to create an application automating the handling of repair orders by municipal workers. Workers require offline access to job orders and ability to take notes and pictures at the job sites.
Developer has created an online version of the application with Code On Time app builder. City manager has purchased the Offline Sync Add-On for 40 users (four packs of “Perpetual / 10 users / 2 domains”) to cover the 34 city workers performing their duties in the field. The page of the app with the list of scheduled jobs was marked as “offline”.
City has more than 100 end users (employees and subcontractors) working with the app. Field workers periodically sync the repair job orders while the other users always access the online version of data at all times.
The app is deployed to two domains that are specified in the Offline Sync license: orders.smart-city.gov and orders-staing.smart-city.gov. The first domain is the production application site. The second domain allows testing the app iterations by the city employees in the staging mode. Developer can test the offline mode of the app on her laptop since the Offline Sync license also includes the localhost domain.
Developer transformed the online app into an offline-capable app without writing a single line of code.
Example 3
The niche market CRM provider used Code On Time to create their online multi-tenant application. Customers are signing into their account through the custom domains. The provider has installed the wildcard SSL certificate on their web server, which makes it possible to secure the traffic from domains such as customer-abc.niche-crm.com and customer-xyz.niche-crm.com.
The provider has acquired the Offline Sync license for 100 users (ten packs of “Perpetual / 10 users / 2 domains”). The licensed domain names include *.niche-crm.com and staging.niche-crm.com. The first domain name allows sharing the offline capabilities with up to 100 users that are spread across multiple customer accounts. The second domain makes it possible for the staging testing of the CRM iterations. The distributed development team can work on the CRM code running in the offline mode thanks to the localhost domain included in the license.
Wildcard domain licensing allows sharing the offline capabilities across multiple application tenants.