Rule Operation Functions

These are Operational Functions that determine which process or processes apply to the selected Module Filtration Rule you have defined. For example, you want your filter of Opportunities that have a status of "won" to only update devices that already have that Opportunity (UpdateExistingOnly). The following are the options currently available:

• Nil
  • If choosing Nil as an option when creating download rules, child records associated to the new record are not downloaded to a device.
• PassToOwners
  • The PassToOwners option allows administrators to only pass updates to owners or if using Oracle CRM on Demand, owner teams or books. iEnterprise Mobile™ does not know by default how to determine what the owner field is or the value that should be contained in it, so this feature will only work if those parameters are defined. (A field of type OWNER should be defined in the module.)
  • The PassToOwners option will search for one of the following values in the rule formula:
    • takeinputfromuser – this identifies that the name entered into the Field Value for each user will be used to determine the owner.
    • takeinputfromteam/takeinputfromuserbook – Oracle CRM on Demand only. This informs iEnterprise Mobile™ that if the user is part of the team /book assigned to this record, the update should be delivered to them.

• PassToAllUsers
  • This will send the updated records (including new records if not previously downloaded) to all users regardless of record ownership. e.g. A contact is updated in the Data Source. Users that have already downloaded that contact will get the updated information. Users that have not already downloaded that contact will get the record in its entirety.
• DeleteAndPassToAllUsers
  • Deleteandpasstoallusers would generally be used if you need one version of a record for a module on all user devices. An example would be if your company had only one version of a disclaimer record and it needed to be on all devices. Then that disclaimer is later updated. So in this case it would be picked up by getupdates, the existing one is deleted on all devices and replaced with the new one. It is a way to ensure consistency of a unique record across all devices.
• SkipGetUpdates
  • If the filter conditions are met, the matching records will not be included in the GetUpdates operation.
• UpdateExistingOnly
  • Devices will only get an update to a record if that record were previously downloaded to that device, either by a Lookup or Initload. Normal operation would create the updated record on any device that did not already have it, but still followed the other filter rules.
• SkipTrickleLoad
  • Updates will only reach a device when manually polled.
• SkipTrickleLoad with Parent
  • If a parent module has been selected, you can prevent a download of all children associated to that parent by selecting the parent and the SkipTrickleLoad.
  • If a new Activity was delivered to a device and Account was selected as a parent, the Account would be checked to see if it had any other children and they would also be downloaded. If an account had 10 activities that the user had previously removed on a device, they would all be re-downloaded as part of the update as all child records of the parent are retrieved. Selecting the parent and SkipTrickleLoad will prevent this from occurring.