Abstract: Simplifying understanding of procedure dependencies in a form definition used in user interfaces. In an embodiment, a form definition including a set of procedures (identified by a corresponding identifier) are examined to determine pairs of procedures such that a caller procedure of a pair invokes/refers a called procedure in the pair. For each of pair of procedures determined, a link associated with an identifier identifying the called procedure is included in the caller procedure. The link is designed to display the called procedure in response to a user action associated with the identifier in a display of the caller procedure.

Abstract: Embodiments of the invention provide systems and methods for logging of messages in a development environment. More specifically, embodiments of the present invention provide dynamically adaptive logging of runtime messages generated by an application. These embodiments provide a way to handle the volume of information stored in the logs by dynamically changing the severity associated with generated messages based on previous code path execution. Embodiments can use a set of metrics to replace the usual static log level associated with the code by the developer. For example, such metrics can include but are not limited to a cost-based (storage volume on disk), an exception-based (weight increase in catch block), and/or a crowd-based (community can vote down noise). As a result, embodiments can provide more detailed information when the error is recurring for a particular user but without generating so much information as to make the log difficult to use.

Abstract: A method of tracking dependencies in an application file, including analyzing the application file to identify at least one dependency in the application file, extracting information from the application file related to the dependency to allow identification of an entity to which the application file has a dependency from the information, and storing the dependency for the application file in the application tier data dictionary. A system has a memory, at a first tier, to store an application tier data dictionary and at least one application file, and a processor at the first tier to determine dependencies in the application file, store the dependencies in the application tier data dictionary, communicate with a second tier, separate from the first tier, as needed to access information with regard to the dependencies, and store the information in the application tier data dictionary.

Abstract: Embodiments of the invention provide systems and methods for logging of messages in a development environment. More specifically, embodiments of the present invention provide dynamically adaptive logging of runtime messages generated by an application. These embodiments provide a way to handle the volume of information stored in the logs by dynamically changing the severity associated with generated messages based on previous code path execution. Embodiments can use a set of metrics to replace the usual static log level associated with the code by the developer. For example, such metrics can include but are not limited to a cost-based (storage volume on disk), an exception-based (weight increase in catch block), and/or a crowd-based (community can vote down noise). As a result, embodiments can provide more detailed information when the error is recurring for a particular user but without generating so much information as to make the log difficult to use.

Abstract: Methods and systems for supporting multiple deployment models for enterprise business applications, are described. In one embodiment, the method may include designating pillars associated with an enterprise business application. Each pillar may include application units which comprise logical groupings for application units used in the enterprise business application. The method may further include determining which of the application units are dependent to more than one of the pillars. Furthermore, based on the determination of the dependent application units, the method may generate deployment code associated with the dependent application units which is configured to be deployment model independent. The method may then receive, at deployment time, a deployment model designation indicating a type of deployment model selected to be used for the enterprise business application. Then, the enterprise business application may be deployed according to the deployment model designation.

Abstract: This disclosure describes, generally, methods and systems for supporting multiple deployment models for enterprise business applications. In one embodiment, the method may include designating pillars associated with an enterprise business application. Each pillar may include application units which comprise logical groupings for application units used in the enterprise business application. The method may further include determining which of the application units are dependent to more than one of the pillars. Furthermore, based on the determination of the dependent application units, the method may generate deployment code associated with the dependent application units which is configured to be deployment model independent. The method may then receive, at deployment time, a deployment model designation indicating a type of deployment model selected to be used for the enterprise business application. Then, the enterprise business application may be deployed according to the deployment model designation.

Abstract: A method of tracking dependencies in an application file, including analyzing the application file to identify at least one dependency in the application file, extracting information from the application file related to the dependency to allow identification of an entity to which the application file has a dependency from the information, and storing the dependency for the application file in the application tier data dictionary. A system has a memory, at a first tier, to store an application tier data dictionary and at least one application file, and a processor at the first tier to determine dependencies in the application file, store the dependencies in the application tier data dictionary, communicate with a second tier, separate from the first tier, as needed to access information with regard to the dependencies, and store the information in the application tier data dictionary.

Abstract: Simplifying understanding of procedure dependencies in a form definition used in user interfaces. In an embodiment, a form definition including a set of procedures (identified by a corresponding identifier) are examined to determine pairs of procedures such that a caller procedure of a pair invokes/refers a called procedure in the pair. For each of pair of procedures determined, a link associated with an identifier identifying the called procedure is included in the caller procedure. The link is designed to display the called procedure in response to a user action associated with the identifier in a display of the caller procedure.