During the activation process, a Trigger Code is sent to your application to perform a specific action. View the Trigger Code overview topic for more information on how trigger codes work.
When using SOLO Server, you will set a Trigger Code for each of your product options. When activating a customer manually with Instant Protection PLUS 3, you will choose the Trigger Code for each activation.
Trigger Code 1 is used for perpetual licenses where the Expire Type is set to 'N' for non-expiring. Trigger Codes 10 and 11 are used for expiring (time-limited) licenses where the Expire Type is set to 'P' for periodic. Trigger Codes 2 through 5 will activate and set the Expire Type to 'N' for a non-expiring license if the application is in trial mode. These Trigger Codes will leave the previous Expire Type if it is set to 'P' for periodic. After activating a periodic license, you must activate with Trigger Code 1 to set a non-expiring license.
If you are using SOLO Server, the "data value" mentioned below can come from one of four fields: Quantity, TC Fixed Value, Days to D/L, or License Counter Value. The Option Type field would need to be set as follows to pass down the correct data field during activation:
| Trigger Code Number | Title | Full Description |
|---|---|---|
| 1 | Activate | This will generate a code to activate the product allowing unlimited use (non-expiring) |
| 2 | Activate and store data | This will generate a code to activate the product. In addition the data value will be stored in the license file data field. You may retrieve this data value from within your application by using the WR_LFGetNum function of the Instant Protection PLUS 3 API. The data is stored in field 23. |
| 3 | Activate and set modules | This will activate the product and store the data value in the license file data field. The data value is used as a bit field to specify which modules are enabled. You may retrieve this data value from within your application by using the WR_LFGetNum function of the Instant Protection PLUS 3 API. This data is stored in field 22. |
| 4 | Activate and OR modules | This will activate the product and OR the data value with the value in the license file data field allowing you to activate additional modules. The data value is used as a bit field to specify which additional modules are enabled. You may retrieve this data value from within your application by using the WR_LFGetNum function of the Instant Protection PLUS 3 API. This data is stored in field 22. |
| 5 | Activate and add data value to License File data field | This will activate the product and add the data value to the value stored in the license file data field. You may retrieve this data value from within your application by using the WR_LFGetNum function of the Instant Protection PLUS 3 API. This data is stored in field 23. |
| 10 | Activate for X days | Sets the product in Periodic mode to run the number of days specified in the data value. If the product is being activated a second time but the periodic time has not expired, the days to run are added to the actual expiration date of the license. For example, if there are 10 days left in the periodic license, and the user activates again with a new license for 90 days then the application will run for 10 + 90 = 100 days. Otherwise, if the periodic license has expired and there are no days left, the days to run are added to the current system date. |
| 11 | Activate for X days from current date | Sets the product in Periodic mode to run the number of days specified in the data value. This code differs from Trigger Code 10 in that the days to run is always added to the current system date. |
| 12 | Store data | This will generate a code to where the data value will be stored in the license file data field. You may retrieve this data value from within your application by using the WR_LFGetNum function of the Instant Protection PLUS 3 API. The data is stored in field 23. |
| 13 | Set modules | This will store the data value in the license file data field. The data value is used as a bit field to specify which modules are enabled. You may retrieve this data value from within your application by using the WR_LFGetNum function of the Instant Protection PLUS 3 API. This data is stored in field 22. |
| 14 | OR modules | This will OR the data value with the value in the license file data field allowing you to enable additional modules. The data value is used as a bit field to specify which additional modules are enabled. You may retrieve this data value from within your application by using the WR_LFGetNum function of the Instant Protection PLUS 3 API. This data is stored in field 22. |
| 15 | Add data value to License File data field | This will add the data value to the value stored in the license file data field. You may retrieve this data value from within your application by using the WR_LFGetNum function of the Instant Protection PLUS 3 API. This data is stored in field 23. |
| 20 | Extend a trial by X days from current date | Extend a trial version of your application to expire after the number of days entered into the data field from the current date. |
| 21 | Extend a trial by X number of runs | Extend a trial by the number of executions entered in the data field. |
| 48 | Force License Synchronization | If the user has, for whatever reason, tampered with the system clock, the licenses could become out-of-synchronization and not allow any more activations. Use this Trigger Code to re-synchronize the licenses on the user's system. |
| 49 | Reset license file and aliases | This Trigger Code will reset a user's machine to a state as if the application was just installed. |
| 50 | Deactivate license | Deactivates the license and sets it to expired if it was a trial. A unique deactivation code is generated on the user's PC and in Instant Protection PLUS 3 below the Activation Code 1 field. You may use this number to verify your user has deactivated. |