Nocode Usage and Flow

What is Nocode? For what purposes should it be used?

Nocode generates dynamic code generation between data layer and user interaction layers in model-widget-event layout, and generates operations in CRUD standards in nocode/lowcode standards. It is recommended to be used for rapid development in general modules that do not require complex, sequential and complex calculations on datasets. Since the Nocode platform is developed in nocode/lowcode standards, the codes produced can be edited manually when necessary.

Model Designing

A model is created on a Workcube Object page (which will be associated with this page) by accessing the "Model" menu on the left menu.

A new “Struct” is created with the “+” symbol in the upper right corner of the relevant screen. Struct encapsulates a dataset, allowing it to run in a scope. It is necessary to specify a name and type for the struct. Structs are formed in two forms main dataset and subdatasets.

A Struct with its Elements determines how a field in a dataset is presented to the user (eg creating a text field for the address field). In this way, the user interaction method of the dataset is determined. In addition, each element is matched to the field in a database object and determines where the incoming/outgoing data will be recorded.

Apart from these moments, if the data is to be associated with a function (provided that Workcube standard functions or specially developed functions are developed in system standards), it can also be specified in the detail of the element. Again, there are various functionality parameters in this area.

After the struct is created, it is saved and stored.

Widget Design

The list of widgets is accessed by the "Widget" option on the left menu of a Workcube Object detail. The widget list creates enhanced data interaction units depending on the relevant model. This allows a model to be presented in more than one shape and purpose.

After a widget data has been created, it drops into the widget list and enters the design screen with the design icon at the end of the list.

In the widget design screen, the structs created by the model are listed on the left and the elements in these lists are also visible. At this stage, the elements related to the “Add Row”, “Add Col” and “Add Grid” options are placed in the widget by drag and drop and a visual structure is created. In some cases, it may be desirable to prepare a storyboard before the model outline becomes clear. For this, by adding empty elements from the Elements section on the page without being connected to any model, structs can be created and the model can be formed according to this screen by following a dependent/independent way from the data.

After the design is completed, it is saved and the event is created.

An event characteristically represents one of the CRUD operations. Widgets can also represent these characteristics, but Widgets do not have to coexist characteristically (e.g., a subset of data can be appended to the record detail page, and that subset can carry the create character for the CRUD). The general characteristic visual sequence is provided with the event.

The event screen is like the widget screen, but instead of the elements on the event screen, the widgets in the library are placed on the screen based on rows and columns. We open an event in the Event menu (or after a new event is created with the "+" symbol) in design mode with the design symbol at the end of the list. On this screen, we add optional associated/unrelated widgets to the screen. An event can host a WO widget other than its own WO. In this case, the relation fields must be specified. This is best illustrated by placing a widget on the page that displays a list of orders for a customer record. Although it is not dependent on WO, which is ordered from widgets, it produces a meaningful result through the relationship. 

Publishing is done by selecting the "Publish" option on the event detail page. When the "Mode" option of the relevant WO is changed to "Holistic" after the publication process, the packages produced with the nocode interface are loaded and start working.