Oracle International Corporation

Pravas Sudhakar Naik Bhagat

Tarun Kumar

Gustavo Takano

Lourdes Hernández Fernández Del Castillo

Manuel Humberto Noriega Soto

Krishna Kumar Viswanathan Nair

Sankaranarayanan Nurani Raman

Vishwanagendran Venkatasubramanian

Jeevan Selvan Job John

Prasun Mukherjee

Russell Broom

Walter Duell

Ricarda Heuss

Srilakshmi Ramachandra

Routines are used to connect bot queries entered via a bot interface and database queries executed on a database. Each routine is associated with routine configurations, including (a) query attributes associated with bot queries that trigger the routine, (2) a database query executed or to be executed for the routine, and/or (3) display settings for displaying information returned from the database query in a bot response. Each routine is configured to generate an output structured data object (SDO) indicating information returned from the database query and the display settings applicable to the information. The output SDOs from the various routines are transmitted to the bot application via a single API endpoint. The routine configurations are entered by a design user through one or more design user interfaces rendered by an integrative configuration application module.

Integrative configuration for bot behavior and database behavior

Techniques for visualizing data elements are disclosed. A system presents a first data element profile comprising: a first data element; a second data element; and a first formula used to calculate a value of the first data element using a value of the second data element. The system detects user input selecting the second data element. Based on detecting the user input, the system presents a second data element profile comprising: the second data element; a third data element; and a second formula used to calculate a value of the second data element using a value of the third data element. The system detects user input selecting the third data element. Based on detecting the user input, the system presents a third data element profile comprising the third data element.

Data element visualization interface

Methods and systems are disclosed for defining deployment data that identify a manner in which to divide a software package of source code deliverables into smaller discrete software package. A triggering event occurring in response to a modification of one or more source code deliverables causes a set of source code deliverables to be identified. One or more particular metadata identifiers associated with the modified one or more source code deliverables may be used to define a group of source code deliverables. The group of source code deliverables includes a subset of the set of source code deliverables that may also be associated with the one or more particular metadata identifiers. One or more packaging rules may facilitate defining deployment data identifying package transmissions for the group of source code deliverables. The deployment data may then be output to one or more devices.

Automated identification of deployment data for distributing discrete software deliverables

Growing community of inventors

Bengaluru, India

Pravas Sudhakar Naik Bhagat