Method, system, and program for automatic generation of screens for mobile apps based on back-end services

Abstract

The present invention enables development of a mobile app screen based on a back-end service, deploy the screen into a mobile app, and develop integration components to connect to the back-end service. The present invention enables automatic creation of a user interface based on a back-end service and offers sufficient flexibility in screen layout modification. The present invention facilitates seamless addition of that screen into a mobile app, submission of data from the screen into the back-end service, and rendering of data received from the back-end service onto the screen.

What is claimed is: 
     
         1 . A method for enabling screen development based on a back-end service, the method comprising the steps of:
 importing a message format definition associated with the back-end service;   creating a business model;   creating a presentation model;   modifying the business model if changes are required;   modifying the presentation model if changes are required;   storing the business model and the presentation model in XML format as a source file; and   generating, using the business model and the presentation model, a HTML page, JSON file, and a JS file.   
     
     
         2 . The method of  claim 1 , wherein the message format definition is one of WSDL, XSD, and JSON. 
     
     
         3 . The method of  claim 1 , wherein the step of creating the business model comprises:
 creating a block for every node in the message format definition; and   creating a field for every element in the message format definition.   
     
     
         4 . The method of  claim 1 , wherein the step of creating the presentation model comprises:
 creating a default window for displaying all nodes and elements;   creating a field group for each node;   in a case in which a node can have only one record, defining a view property of the corresponding field group as form to show all elements in a single record format; and   in a case in which a node can have multiple records, define the view property of the corresponding field group as a grid to show records in multi-record tabular form.   
     
     
         5 . The method of  claim 1 , wherein:
 the HTML page contains presentation-related attributes of the screen;   the JSON file includes a hierarchy definition of various nodes for use in retrieving data from the screen and rendering data received from the back-end service; and   the JS file provides a developer with an option to include functions that can be invoked when a specific action is performed on the screen.   
     
     
         6 . The method of  claim 1 , further comprising the step of checking whether there is an additional service, and, if so:
 importing a format definition associated with the additional service;   adding to the business model by (1) creating a block for every node in the message format definition associated with the additional service and associating the block with the additional service, and (2) creating a field for every element in the message format definition associated with the additional service; and   adding to the presentation model by creating a field group for each node in the message format definition associated with the additional service, and in a case in which a node can have only one record, defining a view property of the corresponding field group as form to show all elements in a single record format, and in a case in which a node can have multiple records, defining the view property of the corresponding field group as a grid to show records in multi-record tabular form.   
     
     
         7 . A non-transitory computer-readable medium storing a program, which, when executed by at least one processor, causes the at least one processor to perform the method for enabling screen development based on a back-end service according to  claim 1 . 
     
     
         8 . A method for providing a development environment to automatically upgrade a screen whenever an underlying service is modified, the method comprising the steps of:
 importing a latest message format definition associated with a back-end service;   updating an existing business model;   updating an existing presentation model;   repeating the importing and updating steps for each service associated with the screen;   modifying the business model if changes are required;   modifying the presentation model if changes are required;   storing the business model and the presentation model in XML format as a source file; and   generating, using the business model and the presentation model, a HTML page, JSON file, and a JS file.   
     
     
         9 . The method of  claim 8 , wherein the message format definition is one of WSDL, XSD, and JSON. 
     
     
         10 . The method of  claim 8 , wherein the step of updating the existing business model includes:
 verifying, for every node in the message format definition, whether the node is already present in the current data model under the same service;   if the node is not present, creating a block for that node, associating the block with the service, and creating a field for every element in the message format definition;   if the node is already present, (1) verifying whether there is any change required in the master-detail relation for the node, and if so updating the existing master-details relation, (2) checking for every element under the node whether the element is already present in the data model, (3) creating a field for each element not present, and (4) checking whether any elements currently present in the data model are not available in the latest format and removing all such fields in both the business model and the presentation model.   
     
     
         11 . The method of  claim 8 , wherein the step of updating the existing presentation model includes:
 creating a field group for each new node comprising all elements under the node, and in a case in which a node can have only one record, defining a view property of the corresponding field group as form to show all elements in a single record format, and in a case in which a node can have multiple records, defining the view property of the corresponding field group as a grid to show records in multi-record tabular form, and   including newly added fields in existing nodes if there is only one field group for the node.   
     
     
         12 . The method of  claim 8 , wherein:
 the HTML page contains presentation-related attributes of the screen;   the JSON file includes a hierarchy definition of various nodes for use in retrieving data from the screen and rendering data received from the back-end service; and   the JS file provides a developer with an option to include functions that can be invoked when a specific action is performed on the screen.   
     
     
         13 . A non-transitory computer-readable medium storing a program, which, when executed by at least one processor, causes the at least one processor to perform the method for providing a development environment to automatically upgrade a screen whenever an underlying service is modified according to  claim 8 . 
     
     
         14 . A method for facilitating addition of new screens into a mobile app and providing data exchange between a screen and a back-end service, the method comprising the steps of:
 launching a HTML screen and loading HTML, JSON, and JS files associated with a chosen function;   initiating a request submission to the back-end;   if indirect back-end integration, building a data JSON request invoking a RESTFul web service deployed in the application server, and invoking the back-end service;   if direct back-end integration, converting JSON to XML if the message format of the back-end service is XML, and invoking the back-end service;   validating the status as successful if a response from the application server component is received, storing the response in an object variable, and populating relevant fields in the HTML file by reading the object variable, and   retrieving error messages and displaying the error messages to the user if the status is not successful.   
     
     
         15 . The method of  claim 14 , further comprising the step in indirect back-end integration of including a function in the screen-specific JS file such that a developer can modify the JSON file being submitted to the back-end. 
     
     
         16 . A non-transitory computer-readable medium storing a program, which, when executed by at least one processor, causes the at least one processor to perform the method for facilitating addition of new screens into a mobile app and providing data exchange between a screen and a back-end service according to  claim 14 . 
     
     
         17 . A method for receiving a request from a mobile tier and sending a response to the mobile tier, the method comprising the steps of:
 receiving a JSON object via a HTTP POST method call from a mobile channel;   performing the following actions on the JSON object:   validating session authenticity using a token generated in an earlier HTTP call;   logging the JSON object;   validating user entitlements;   invoking a generic integration adapter to route the request to an appropriate processing system;   logging a response received from the appropriate processing system;   further updating the transaction audit trail; and   forwarding the response to the mobile tier.   
     
     
         18 . A non-transitory computer-readable medium storing a program, which, when executed by at least one processor, causes the at least one processor to perform the method for receiving a request from a mobile tier and sending a response to the mobile tier according to  claim 17 . 
     
     
         19 . A system implemented on a computer having a processor and a memory coupled to said processor for automatic generation of screens for mobile apps based on back-end services, comprising:
 a Development Tool Module for enabling screen development based on the back-end service;   a Mash-Up Module for adding an additional service;   an Automatic Screen Upgrade Module for providing a development environment to automatically upgrade a screen whenever an underlying service is modified;   a Container App Module for facilitating addition of new screens into a mobile app and providing data exchange between the screen and the back-end service; and   an App Server Module for receiving a request from a mobile tier and sending a response to the mobile tier.   
     
     
         20 . A system for enabling screen development based on a back-end service, the system comprising:
 a development tool, adapted to:   import a message format definition associated with the back-end service;   create a business model;   create a presentation model;   modify the business model if changes are required;   modify the presentation model if changes are required;   store the business model and the presentation model in XML format as a source file; and   generate, using the business model and the presentation model, a HTML page, JSON file, and a JS file.   
     
     
         21 . A system for providing a development environment to automatically upgrade a screen whenever an underlying service is modified, the system comprising:
 an automatic upgrade tool, adapted to:   import a latest message format definition associated with a back-end service;   update an existing business model;   update an existing presentation model;   repeat the importing and updating steps for each service associated with the screen;   modify the business model if changes are required;   modify the presentation model if changes are required;   store the business model and the presentation model in XML format as a source file; and   generate, using the business model and the presentation model, a HTML page, JSON file, and a JS file.   
     
     
         22 . A system for facilitating addition of new screens into a mobile app and providing data exchange between a screen and a back-end service, the system comprising:
 a Container App, adapted to:   launch a HTML screen and loading HTML, JSON, and JS files associated with a chosen function;   initiate a request submission to the back-end;   if indirect back-end integration, build a data JSON request invoking a RESTFul web service deployed in the application server, and invoking the back-end service;   if direct back-end integration, convert JSON to XML if the message format of the back-end service is XML, and invoking the back-end service;   validate the status as successful if a response from the application server component is received, store the response in an object variable, and populate relevant fields in the HTML file by reading the object variable, and   retrieve error messages and display the error messages to the user if the status is not successful.   
     
     
         23 . A system for receiving a request from a mobile tier and sending a response to the mobile tier, the system comprising:
 an App Server, adapted to:   receive a JSON object via a HTTP POST method call from a mobile channel;   perform the following actions on the JSON object:   validate session authenticity using a token generated in an earlier HTTP call;   log the JSON object;   validate user entitlements;   invoke a generic integration adapter to route the request to an appropriate processing system;   log a response received from the appropriate processing system;   further update the transaction audit trail; and   forward the response to the mobile tier.