Abstract: Certain aspects of the present disclosure provide techniques for defining a completeness of input, including receiving a first input, comprising: a set of fields associated with an operation; a set of indicators, wherein at least one indicator in the set of indicators is associated with a field in the set of fields; and a set of modifiers, wherein each modifier is associated with at least one indicator in the set of indicators, wherein a combination of the set of indicators and the set of modifiers indicates fields of the set of fields that require input to execute the operation; receiving a second input associated with the set of indicators and the set of modifiers; receiving, from the knowledge engine, a result based on the second input; and determining whether the second input contains required input to the fields that require input based on the result.

Abstract: Certain aspects of the present disclosure provide techniques for encoding rules defining a completeness of input, including receiving a first input comprising one or more tuples, wherein a tuple of the one or more tuples comprises one or more fields associated with an operation, one or more indicators, and one or more modifiers; receiving a second input associated with the one or more tuples; providing, to a knowledge engine, the first input and the second input; receiving, from the knowledge engine, a result based on the first input and the second input; determining, based on the result, a first symbol associated with a first tuple of the one or more tuples; and displaying the first symbol, wherein the first symbol indicates whether the first tuple is complete.

Abstract: Certain aspects of the present disclosure provide techniques for generating a user experience for a software program product based on a knowledge engine. Techniques for generating the user experience include a UI builder tool providing a set of tabular UI views and receiving in each tabular UI view corresponding input data for generating a calculation graph, a completeness graph, a client UI view, and a constants table. Based on the input data, the UI builder tool and knowledge engine can generate a set of artifact files. The knowledge engine can generate and/or execute the calculation graph(s), completeness graph(s), and constants table(s) as defined in the corresponding artifact files. The UI builder tool can generate an instance of the client UI view. With the generated calculation graph(s), completeness graph(s), constants table(s), and an instance of the client UI view, the user experience can be provided to a computing device.

Abstract: Certain aspects of the present disclosure provide techniques for generating a user experience for a software program product based on a knowledge engine. Techniques for generating the user experience include a UI builder tool providing a set of tabular UI views and receiving in each tabular UI view corresponding input data for generating a calculation graph, a completeness graph, a client UI view, and a constants table. Based on the input data, the UI builder tool and knowledge engine can generate a set of artifact files. The knowledge engine can generate and/or execute the calculation graph(s), completeness graph(s), and constants table(s) as defined in the corresponding artifact files. The UI builder tool can generate an instance of the client UI view. With the generated calculation graph(s), completeness graph(s), constants table(s), and an instance of the client UI view, the user experience can be provided to a computing device.