# US 2025/0094142 A1 · Model describing configuration field dependencies to drive user experience > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2025/0094142 A1 - Document ID: US20250094142A1 - Status: Published application - Kind: A1 - Application number: 18/368,708 - Filed: 2023-09-15 - Published: 2025-03-20 - Earliest claimed: 2023-09-15 - Assignees: Oracle International Corporation - Applicants: Oracle International Corporation - Inventors: Tuck Chang; Tian Ma; Zhengming Zhang - Web page: https://patentgrep.com/patent/US20250094142A1 ## CPC - G06F 8/38: for implementing user interfaces - G06F 9/451: Execution arrangements for user interfaces - G06F 9/541: {via adapters, e.g. between incompatible applications} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract The present disclosure relates to a “no code” framework for creating adapters to integrate a cloud service or other platform with a third-party service. User interface component metadata representing a user interface may be generated based at least in part on a metadata document. The metadata document may comprise metadata specifying a plurality of fields and one or more dependencies of one or more of the plurality of fields on one or more other of the plurality of fields. The user interface component metadata may comprise metadata representing a first field of the plurality of fields. An interaction with the first field in the user interface may be detected, and a second field of the plurality of fields having a dependency on the first field may be identified based at least in part on the metadata document. The user interface component metadata may be updated to comprise data representing the second field. ## Claims ### Claim 1 A method comprising: generating user interface component metadata representing a user interface based at least in part on a metadata document, the metadata document comprising metadata specifying a plurality of fields and one or more dependencies of one or more of the plurality of fields on one or more other of the plurality of fields, and the user interface component metadata comprising metadata representing a first field of the plurality of fields; detecting an interaction with the first field in the user interface; identifying a second field of the plurality of fields having a dependency on the first field based at least in part on the metadata document; and updating the user interface component metadata to comprise data representing the second field, wherein the method is performed by one or more computing devices. ### Claim 2 (depends on 1) The method of claim 1, wherein the interaction with the first field of the user interface is a first interaction and the dependency is a first dependency, the method further comprising: detecting a second interaction with the second field, the second interaction indicating a particular value for the second field; identifying a third field of the plurality of fields having a second dependency on the second field based at least in part on the metadata document, the second dependency specifying the particular value; and updating the user interface to comprise the third field and data corresponding to the third field. ### Claim 3 (depends on 2) The method of claim 2, further comprising determining that the second dependency specifies the particular value based at least in part on a query to a third-party service. ### Claim 4 (depends on 2) The method of claim 2, further comprising: requesting the data corresponding to the third field from a third-party service; and receiving the data corresponding to the third field from the third-party service. ### Claim 5 (depends on 2) The method of claim 2, wherein encoding for rendering the user interface based at least in part on the metadata document further comprises determining to refrain from encoding for rendering the second field in the user interface based at least in part on the first dependency on the first field. ### Claim 6 (depends on 1) The method of claim 1, wherein the user interface is a first user interface, further comprising encoding for rendering a second user interface comprising an editable representation of the metadata document. ### Claim 7 (depends on 6) The method of claim 6, further comprising updating the second user interface to comprise an indication of one or more errors within the metadata document based at least in part on one or more rules. ### Claim 8 (depends on 7) The method of claim 7, wherein the user interface is encoded for rendering in response to determining that the metadata document satisfies the one or more rules. ### Claim 9 (depends on 7) The method of claim 7, wherein the one or more rules comprise at least one of: one or more syntactic rules, one or more semantic rules, or one or more dependency rules. ### Claim 10 (depends on 6) The method of claim 6, further comprising updating the second user interface to comprise a representation of at least a portion of the first user interface. ### Claim 11 One or more non-transitory, computer-readable media storing instructions which, when executed by one or more computing devices, cause: generating user interface component metadata representing a user interface based at least in part on a metadata document, the metadata document comprising metadata specifying a plurality of fields and one or more dependencies of one or more of the plurality of fields on one or more other of the plurality of fields, and the user interface component metadata comprising metadata representing a first field of the plurality of fields; detecting an interaction with the first field in the user interface; identifying a second field of the plurality of fields having a dependency on the first field based at least in part on the metadata document; and updating the user interface component metadata to comprise data representing the second field. ### Claim 12 (depends on 11) The one or more non-transitory, computer-readable media of claim 11, wherein the interaction with the first field of the user interface is a first interaction and the dependency is a first dependency, and the instructions, when executed by the one or more computing devices, further cause: detecting a second interaction with the second field, the second interaction indicating a particular value for the second field; identifying a third field of the plurality of fields having a second dependency on the second field based at least in part on the metadata document, the second dependency specifying the particular value; and updating the user interface to comprise the third field and data corresponding to the third field. ### Claim 13 (depends on 12) The one or more non-transitory, computer-readable media of claim 12, wherein the instructions, when executed by the one or more computing devices, further cause determining that the second dependency specifies the particular value based at least in part on a query to a third-party service. ### Claim 14 (depends on 12) The one or more non-transitory, computer-readable media of claim 12, wherein the instructions, when executed by the one or more computing devices, further cause: requesting the data corresponding to the third field from a third-party service; and receiving the data corresponding to the third field from the third-party service. ### Claim 15 (depends on 12) The one or more non-transitory, computer-readable media of claim 12, wherein the instructions causing encoding for rendering the user interface based at least in part on the metadata document, when executed by the one or more computing devices, further cause determining to refrain from encoding for rendering the second field in the user interface based at least in part on the first dependency on the first field. ### Claim 16 (depends on 11) The one or more non-transitory, computer-readable media of claim 11, wherein the user interface is a first user interface, further comprising encoding for rendering a second user interface comprising an editable representation of the metadata document. ### Claim 17 (depends on 16) The one or more non-transitory, computer-readable media of claim 16, wherein the instructions, when executed by the one or more computing devices, further cause updating the second user interface to comprise an indication of one or more errors within the metadata document based at least in part on one or more rules. ### Claim 18 (depends on 17) The one or more non-transitory, computer-readable media of claim 17, wherein the user interface is encoded for rendering in response to determining that the metadata document satisfies the one or more rules. ### Claim 19 (depends on 17) The one or more non-transitory, computer-readable media of claim 17, wherein the one or more rules comprise at least one of: one or more syntactic rules, one or more semantic rules, or one or more dependency rules. ### Claim 20 (depends on 16) The one or more non-transitory, computer-readable media of claim 16, wherein the instructions, when executed by the one or more computing devices, further cause updating the second user interface to comprise a representation of at least a portion of the first user interface.