Migrating Applications From Asynchronous to Synchronous Programming Model

Siebel Mobile disconnected uses a synchronous programming model where $.callback and $.setReturnValue are not required. Previous releases of Siebel Mobile, prior to Siebel Innovation Pack 2016, used an asynchronous programming model where business services used a $.callback and $.setReturnValu for every method.

Note: Customers who have written their own JavaScripts for Siebel Mobile disconnected must complete this task. This task is not required for customers planning to use Siebel Mobile disconnected for the first time with latest Siebel Innovation Pack.

Migrating Siebel Mobile disconnected from an asynchronous to a synchronous programming model involves the following

• Removing $.callback for all calling and called functions in the core framework (buscomp.js, applet.js, appmgr.js, browsercachemgr.js, model.js, and view.js).

  Note that metadata discovery is retained as an asynchronous call.

• Removing $.callback from all Siebel Mobile disconnected applications.

• Removing $.setReturnValue.

• Returning a value instead of $.setReturnValue in all functions.

To assist you in migrating Siebel Mobile disconnected JavaScript code from an asynchronous to a synchronous programming model, a migration tool (async2sync.pyc) is provided. For more information about the JavaScript migration tool, see About the JavaScript Migration Tool.