Abstract: A method and system for providing real-time display of data collected and submitted via mobile devices. An example method includes collecting data in a data record by the mobile device. The collected data record is submitted to a remote server. At least some of the data in the collected data record is displayed in real-time relative to the submission of the collected data record via an interface.

Abstract: A method and system for providing real-time display of data collected and submitted via mobile devices. An example method includes collecting data in a data record by the mobile device. The collected data record is submitted to a remote server. At least some of the data in the collected data record is displayed in real-time relative to the submission of the collected data record via an interface.

Abstract: The present invention relates to a method and a data structure for defining a resource of a desired type within a resource management application. The method for creating a resource comprising steps for: selecting a catalog based on the desired type; identifying a template associated with the catalog; creating an initial instance of the resource; creating attributes associated with the resource based on definitions specified by the catalog and applying primary validations specified by the catalog; establishing relationships with the resource by applying constraints associated with the template and the catalog; and applying secondary validations associated with the catalog and the template. The data structure lends itself to being changed or augmented. This permits the modification or addition of resource type definitions without necessitating changes to computer program code in the resource management application.

Abstract: The present invention provides an interface in a first computer application system that can be utilized by other computer application systems to invoke the execution of an action (e.g. a functional process) on the first system. The first system can support multiple different actions each with distinct functionality. A single entry point in an externally accessible interface is used regardless of which action is invoked. Each invocation of the entry point includes two parameters. The first to designate which of the actions is to be invoked. The second provides for the referencing of data elements that can supply input arguments used during execution of the action. The single entry point is not exposed to the semantic of the supplied arguments. Therefore the action execution interface does not need to change when the semantic specific to any of the actions is changed or when a new action is added.