Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

There are a number of module settings that can be configured by the Admin to tailor Swift MEAP™ iEnterprise Mobile™ to your company's requirements. For information on how to make changes, see Modifying a Mapped Module.

Select Map Settings -> Module Settings to see the list of modules already mapped to the Server.  To the right of each entry will be a list of icons.  Choose the 'Edit' icon to make modifications to that module.  Once you do, a configuration window will appear and display the following options:

  • Server Module Name: Displays the table name of the current Swift MEAP™ iEnterprise Mobile™ module selected. This is a read only field.
  • Module Name: The name of the module currently being edited, as read from the Data Source. This is a read only field.
  • Top Level: Indicates whether an object has been defined as a Top Level Object. Top Level Objects are displayed in the Navigation Bar within the Swift MEAP™ iEnterprise Mobile™ client. If a module is not defined as a Top Level Object, it will only be displayed as a related (child) object in Swift MEAP™iEnterprise Mobile™. For an overview of the layout used in the Swift MEAP iEnterprise Mobile client, see Mapping Overview.
  • High Priority - GetUpdates: Sets this module in the GetUpdates routine as a High Priority item. Items marked as such get processed before items without this indication.
  • Group: Objects can be grouped into a special "Activities" object. It can be used to group similar tasks such as emails, appointments and phone calls together. When viewing records within the "Activities" group, all items are displayed in a single list. In the example given above, a user would see a list of emails, appointments and phone calls together. When a user adds a new Activity, a pop up is displayed asking which of the grouped items they wish to add. Objects can only be grouped this way into the Activities group. The Activities object cannot be renamed.
  • Read Only: The Read Only setting only applies to the creation of new records, users may still be able to edit records, if editing has been configured using the Allow Edit function. NOTE: This setting will only apply if your Data Source allows editing. There are four options available:
    • NIL - no Value Set.  This is the default setting.
    • ReadOnly: Users will not be able to create new records for this module.
    • ReadOnlyTopLevel: Users will not be able to create records for this module when viewing this module from the top level. They will be able to create related records when viewing this module from a parent object. For example, if Contacts were set with this parameter, users would not be able to create contacts when viewing the Contacts object. They would be able to create a contact when viewing Accounts and clicking on the blue plus sign next to Contacts in the Related List. This prevents unassociated records from being created.
    • ReadOnlyNotParentOwner: Users will not be able to create related records unless they are defined as the owner of the parent. If Contacts were set up with this setting, users would only be able to create contact records related to an account if they were defined as the owner in the account record.
  • Skip in Cad: The Skip In Cad feature allows administrators to prevent a module from being sent to a client device. If a module is not included in the CAD file, it will not be displayed on the client device but will still exist within the Admin application. This feature can be used to disable preconfigured modules if they are not needed, without having to remove them completely. If mapping new modules, it is recommended that you enable the Skip in Cad option until the module has been fully configured.
  • Allowed to delete in Data Source: Indicates whether records within this module be removed from the data source server. NOTE: Some data sources will not allow removal of records through web services, regardless of the option specified here.
  • Allow to remove from Device: Indicates whether records may be removed from the device by server update or command.
  • Allow Edit: This allows administrators to choose who and if records can be edited on a device. If a module has editing enabled, administrators can also configure which fields are editable when configuring field settings. For more information, see Field Details. There are three options available:
    • Nil: No editing is allowed
    • Allow Edit (All): All users are allowed to edit records in this module
    • Allow Edit (Owners): Users are only allowed to edit records if they are defined as the owner

...

Info
This setting will only apply if your data source allows editing.

 

  • Display As Table: This allows the fields within the module to be displayed in a table format on the mobile device (currently iPad only). For more information, see Displaying Tables in Swift MEAPiEnterprise Mobile.
  • Conflict Resolution: Select whether data from a mobile device or the Swift MEAP™ iEnterprise Mobile™ server should be processed in the event of a conflict within the current module.
  • Device Type to Display On: Specifies whether the module should be displayed on phones, tablets, or both.
  • Module Type: The module type field should not be changed. It is reserved for use by iEnterprises for a customized installation.
  • Display as HTML: Allows a record to render in an HTML format. Not all devices can support this feature.
  • Show Custom DB Fields: Occasionally it is necessary for iEnterprises to insert custom code to alter fields within the Swift MEAP™ iEnterprise Mobile™ application. Any custom code is displayed here. Note: This should only be amended by iEnterprises, do not enter or alter any code entered here.
  • WebService Configurations: This field is used for custom code that is required to manage data from custom Web Service code. Note: This should only be amended by iEnterprises, do not enter or alter any code entered here.

...