A Module is the generic term for a development file that's under Devin's control.
To Add a Module to a Project, open the Project Workspace, go to Modules and click +. Then:
Choose a file from your development server
Specify an initial version number
Choose the file type
Enter Full Access credentials for the file (FileMaker user account)
Optionally, provide an EAR encryption key.
When the file has been added as a Module in Devin, you will see that a copy of the file now exists on the project's default main branch, called <filename>_main.fmp12. The original file, <filename>.fmp12, will no longer be used by Devin and can be removed manually from your server.
To start development on the file, the main file should be branched to another branch (see Branch a Module).
Devin lets you choose between three file types. If you practice the Data Separation Model architecture where you split up your fmp12 files into UI and Data files choose App for UI files and DB for Data files. If your file has combined UI and Data, choose All-In-One.
To learn more about the Data Separation Model, search "FileMaker Data Separation Model" in your favorite search engine and discover many community and blog posts about this choice of this popular architecture.
Devin needs access to development files via the FileMaker Data API. Therefore, the specified account must have the fmrest extended privilege enabled. Other features, like 回帰テスト, requires communication via the FileMaker OData API, and thus, the fmodata extended privilege enabled. To enable these extended privileges, go to Security -> Advanced Settings -> Extended Privileges.
Devin has not been tested with files that use external OAuth for authentication.
To learn more about branches and version control, see .
