Thousands of days of cultivation to return to the original heart, and thousands of hammers to make a tool . After five iterations and three months of fine-tuning, Feida 2.3.0RELEASE has finally been officially released!
Flying Overview
FeiDa, which is based on Hande's digital platform HZERO, is an integrated aPaaS low-code platform built on the basis of advanced low-code concepts.
As an important part of the HZERO ecosystem, FeiDa fully integrates the rich and powerful platform capabilities of the HZERO platform (flexible permissions configuration, support for internationalization, support for SaaS, front-end and back-end personalization and expansion, high security, high performance, etc.), Component capabilities (process platform, integration platform, data platform, etc.)
At the same time, with business-oriented data model, visual interactive components, comprehensive logic events and flexible script & transaction processing flow back-end logic programming capabilities, it empowers enterprises to build B-side applications flexibly online, and supports enterprise generalization. Huihua (low threshold, high collaboration), agility (high efficiency) and low cost respond quickly to market changes, and accelerate the implementation of complex business scenarios.
▲The overall architecture of the aPaaS platform
▲aPaaS platform system features
current pain points
Some low-code products on the market currently focus on OA document scenarios with short business process links and less control, or focus on specific industries/businesses/functions. While ensuring flexible business configuration, Support more core and complex enterprise business processes.
In response to this pain point, Feida 2.3 supports online configuration of complex front-end pages, back-end control or processing logic, and can be used as a general base to support enterprises to realize the construction of complex business scenarios.
In-page field/component linkage
01. Control the available value range of other fields according to the value of a field
02. When a field is maintained, it is linked to assign values to other fields
03. When a field is maintained, the linkage makes other fields read-only/required
04. The linkage between different values of fields and roles makes the button read-only/invisible (state transfer can be realized): Combined with the operation buttons that can be used by roles, different roles can perform different processing on documents, change the status of documents, and realize the status transfer of documents
05. The linkage of different values of object header fields makes the row TAB page invisible
Role linkage control page field/component property
06. Some fields are invisible/read-only when controlling different roles using the page
object data linkage
07. The object field association applies other object non-primary key fields (such as code fields): for example, the "purchase type code" field of the purchase order header object is associated with the "type code" field of the purchase type object
08. Application of slave-master relationship linkage to save lines and headers: Multi-layer slave-master relationship objects can be saved at the same time, such as purchase order header forms, line lists, and dispatch run lists.
09. Corresponding additional data is created when the list is saved in multiple lines: the multi-line in-line editing of the list is saved together, and related records are created when the master record is generated. For example, when the purchase order header list is edited and saved in-line, the purchase order history record is created and generated synchronously
10. The summary query line data can be displayed when querying the header: for example, the summary of the number of lines corresponding to all purchase order lines (that is, the sum of the number of lines) can be found on the purchase order header information.
Object data verification and masking
11. Multi-field combination control data uniqueness: When the object is saved, it can judge whether the data is unique according to multiple fields and report an error, for example, the purchase order line is unique according to the purchase order header ID + line number control
12. Judging data validity through formula verification: When objects are saved, they can judge whether the records are valid according to the maintenance formula verification rules. For example, when maintaining order lines, the line unit price * line quantity cannot be greater than 10000
13. Queryable data range of shielded roles: For example, role A can check order status = data to be submitted, role B can check order status = data to be approved, and data shielding can be performed according to roles
Capability Convergence - Process Application
14. Submit workflow for document processing
Some scene examples
01 Control the range of available values for other fields based on the value of a field
Flyover supports controlling the range of options in the B field through the A field value.
For example, on the edit page of the request form, you need to control the [Acceptable Mode] according to the [Classification] field of the [Request Form Line] list.
When the [Category] field of the request single line list is selected as [Material], the [Processable Mode] field cascades and displays three options of [Available], [Cancellable], and [Can be Shipped]; and when the [Category] field is selected When [Manual] is selected, the [Acceptable Mode] field can only display two options [Available] and [Cancel] in cascade.
02 When a field is maintained, it is linked to assign values to other fields
Flyover supports the assignment of data selected by A (LOV) to the B (LOV) field in the page.
For example: [Service Station] After LOV selects "Guangxi Service Station", it will automatically assign [Office] to the "Guangxi Office" it belongs to.
Recommended in the past
1. The HZERO 1.9.0 version of Hande's enterprise-level digital PaaS platform was officially released!
For more exciting content, scan the code to follow the public account of "Sihai Hande"