The Enables.ini file contains one section for each module defined within the application. Each section lists all actions, pushes, detail screen fields, and list screen columns that are defined within the module. The value of each item is either true or false. It is likely that most of the values are set to true, unless the definition is disabled in the application.
The override file created from this base file can contain items with a value of false to disable the corresponding definition, or true to enable it. The effect of disabling a definition depends on the definition type. Disabled fields and columns do not appear on the client. Users cannot execute disabled actions. A disabled push results in all behaviors related to that push being disabled. If there are no enabled pushes, and background sending is not enabled, users do not remain logged in to the server, regardless of the transmit configuration definition.
This is an example of the contents of the Enables- and EnablesBase.ini files:
The contents of this file are application-specific. The above is an example for a mobile application built for the Northwind demonstration database in SQL Server.
This override file contains one section name, [<ModuleName>], for each module defined within the application.
screencolumn.ShowCustomers.ShowCustomers_List_PPC.CustomerID=truerepresents the screen column (screencolumn) CustomerID in the ShowCustomers_List_PPC list screen, which is a child definition to the ShowCustomers screen set. Each override item’s key follows a defined format:
- defType – definition type being
overridden by the item. Examples include:
- ModuleLevelParent – name of the module-level parent definition, of the definition whose enabled state is being overridden.
- Parent.Parent – name of each subsequent ancestor definition, of the definition being overridden is a part of the key.
- definitionName – name of the definition being overridden.