FM Registrations creates licensing codes for your FileMaker projects.

Example: If FM Registrations is integrated into your solutions, then you can create unlock codes for your customers, which they can use to unlock a trial version to a full version, for example.

Licensing codes carry certain information, such as expiration date, number of users, version number, etc. All this information can be freely defined in FM Registrations.

After you have used the sample file to apply the decryption in your own software, the customer can now enter the registration codes and they will be decrypted again in your software. As a result of the decryption the following information is available afterwards:

• Total result of decryption (valid/invalid)
• All information (number of users, expiration date, etc.)

You yourself must now evaluate this information in your software.

FM Registrations consists of 2 parts:

1. FM Registrations, the coding software
2. Sample file for integration into your solutions

You need a full version of FileMaker Pro Advanced to add this registration solution to your own FileMaker solutions. Please note the minimum requirements for the current version of FM Registrations.

The minimum requirements are as follows:

1. The developer minimally needs FileMaker Pro Advanced 15
2. The solution itself can be integrated in all FileMaker versions from version 12.

Yes. You can list any number of your own solutions, register any number of customers and generate any number of codes. There are no limitations.

No. FM Registrations – the program itself – cannot be customized. The file has no developer access. On the other hand, the example file is completely accessible and well documented, so you can easily integrate the registration into your solutions.

The sample file was built according to the structure of a FileMaker module. A module distinguishes by functionality and parameterization. A module folder has different subordination, for example for settings, for test scripts, for the main script. Adjustments should be needed only in the settings scripts. These are queried by the main script during execution. A module makes it easier to incorporate solutions from other developers into your own development because you only have to worry about the settings, so to speak, and not the functionality.

The registration module of the sample file has its own table, layouts and scripts and also uses some own functions. There are instructions on how to import these parts in order. The description can be found in the manual as well as in the ReadMe script of the module.

Importing all components takes maybe a quarter of an hour. Afterwards, the integrated test function can be used to check whether everything is working correctly. Afterwards, the secret keys can be integrated for your own software solution – and you can start assigning your own license codes.

Yes, any number of codes can be generated as a batch.

• Codes are always created for an address. This also applies to a batch with codes. This can be, for example, a partner who receives multiple codes
• Codes can later be “reversed” to a new address, e.g. of the licensee.
• Lists with codes can be printed or output as an Excel file.

FM Registrations does two things: encrypt parameters (code generator) and decrypt parameters (sample implementation file). The first step is to integrate the information in the sample file into your own solution. After that, unlock codes are decrypted and the parameters for the unlock code are available again. How now these parameters are interpreted, you must define yourself.

Example: You have set up an expiration date. This information is available after decryption. Now you have to write a script which checks the date and take this script into account when starting the file (or include it in a startup script).

The check should have a certain logic: Option A) The expiration date has not yet been reached, the license is valid. > continue to home page, or option B) The expiration date has been reached and the license is no longer valid > further to a page where either a new license can be requested (e.g. link to website) or where the data of the application can be exported if the customer does not need another license.