Stories of digital innovation by no-code
Learn about channel program opportunities
Join the Network
Leverage the resources of Jamio designers
We collaborate with universities
Jamio openwork world news
Keep up on the world of no-code and digitization
The periodical on no-code and BPM
Check out our guides full of clarification for digitization
Jamio has tools for modeling a generic business entity so that it can represent any real-world object, e.g., a product sheet, a quote card, a service request, a customer master, etc....
The purpose of the card is to collect a set of information and documents that can be imputed by a person. either directly or during the execution of a process, or by an external system or automatically precompiled based on context and/or conditional information (e.g., date, author, author role, etc.).
To model an information sheet ( form ) with jamio composer, you start with a basic model and enrich it with additional fields for collecting metadata: all those needed to manage in the most appropriate way your business case (text, dates, images, files, lists, links to other objects, etc). In design time, the designer, in addition to being able to represent the information to be managed, can also define the way in which the user must interact with it ( layout) and the behavior of each field by setting business rules that can be assertive, assignment or validation ( e.g.: the field "author" is disabled, the field "amount" is visible only to the head of the person who entered it", the field "date" must contain a value equal to today plus 10 days.........). In addition, for each card the lifecycle (create, read, save, edit, delete, lock) is natively managed and Access Control Lists (ACLs ) are attributable. These, together with many other Data Management features, make it possible to manage a multiplicity of business cases always using a no- code Human Resource Oriented language
By performing one-click publishing of the solution to a Jamio workspace, the form modeled in design time is immediately usable from the front-end. Different forms compiled from the same template, based on an authorization profile, can be navigable and explorable through catalogs, i.e., lists of forms of the same type, possibly filtered against a selection rule.