Defining Mobile Workflow Load Parameters From Mapped Transient personalization Keys

Map load parameters to transient personalization keys. Specify values for those personalization keys when you invoke an operation or object query from the mobile workflow form.

1. Create a mobile business object that has load parameters. For example, the Customer MBO could have this definition:

   SELECT   id,
     fname,
     lname,
     address,
     city,
     state,
     zip,
     phone,
     company_name FROM sampledb.dba.customer
   where state = :state_load_param
   

2. Create a corresponding personalization key for each load parameter where the Storage type is Transient.
3. Map each load parameter to the corresponding personalization key. Set the load parameters in the MBO Properties view, from the Load Parameters tab.
   
   
   
4. (Optional – specify the cache group policy that meets the Workflow client's needs. The policy defined here, results in a immediate data refresh for every client request). Set the On demand cache group policy for the MBO with a Cache interval of zero.
   1. Add the MBO to a Cache Group that uses the On demand cache group policy. For example, create a new cache group named CacheGroupOnDemand and set the policy to On demand and the Cache interval to zero.
      
      
      
   2. Drag and drop the MBO to the CacheGroupOnDemand cache group.
   At runtime, when the client passes in their transient personalization key values (user name and password for example), the entire cache for the MBO refreshes prior to synchronization. While this ensures the device receives up-to-date EIS data, it is more costly in terms of resources compared to a cache policy with a longer cache interval.
5. Deploy the project that contains the MBO to Unwired WorkSpace. Select Message-based in the deployment wizard.