FLEXIBLE APPLICATION BUILDER

by AppliWare
At your applications' base
FlexAB is a tool for the non-programming application creation, with
object-oriented flexibility, and utilizing robust relational databases.
The developer interacts only with objects, the data and their relatio-
nal structure are transparent for the configurator, and there is no
time losing in relations, indexes, tables, etc. Thus, reducing the deve-
lopment time in the application creation. The Objects utilization
makes possible their reutilization in other applications, as well as
their link with other applications, sharing the information in all the
families of systems developed directly by FlexAB, without interme-
diate processes or interfaces.
FlexAB leans on a special, standardized, fixed, and optimized struc-
ture of tables on relational databases which makes possible the
objects storage in a transparent way. This structure of tables and
their associated functions for information handling is known as
ApliWare OrDBC (Object Relational Data Base Core).
FlexAB is developed from its bases oriented to Objects and to the
object application towards the information technology processes.
Due to this, it is a powerful tool when it comes to data processing.
FlexAB tool by AppliWare is a software which allows you to create
your own information system applications in a simple, dynamic, fast
and safe way without programming. FlexAB has embeded functionali-
ties for file management in a transparent way.
What is FlexAB's main idea:
to generate software appli-
cations capable of meeting
companies' needs without
having to develop a custom
software, and without the
constraints of having to
choose a shelf-ware or
"canned" software. The
best solution for any com-
pany lies halfway these
two ends. It is widely
known that custom solu-
tions end up being expensi-
ve to maintain, too depen-
dent on the implementa-
tion designer, and difficult
to enhance at an affor-
dably cost. On the other
hand, shelf-ware solutions
normally cover the compa-
nies' general solutions,
rather than the specific or
particular needs. It is here
where they fail, and the
company has to make an
effort, or even a change in
their usual procedures to
fit the software.
Custom or Shelf-
ware Solutions?
FlexAB
FlexAB is a combination of both
things: it is a tool which provides the
framework to develop a fully custom
application, but on a platform which
does not require programming so it
standardizes the software creation.
What does this mean? : The custom
software constraint elimination,
since the FlexAB-built applications
are not programmer-dependent, are
open, the application know how
remains with the end-client, are fle-
xible, and can be fully enhanced
with no surcharges.
Data process
Solutions
by utilizing
Custom
Software
Data process
Solutions
by utilizing
Shelfware
Expensive
Difficult
to maintain
Programmer
dependent
Difficult to adjust
Rigid
Non-integrable
Process-oriented

Combines
both
world's
benefits
Disadvantages Disadvantages

Why is FlexAB beneficial to Software developers?

For the application development it is necessary to have tools designed or oriented to the develop-
ment of applications capable of meeting the development needs at the lowest possible cost of
resources, both human and technical. Every professional needs its tools for the development of
his/her activities, and such tools are conceived from the beginning to meet the end-user's demands.
FlexAB is an environment that links databases for the object handling with the tools to provide
functionality to those objects and not only to store them.
Less Development Time: Because there exists a previously done base work, a Standard interfa-
ce ready to be used, there is no need to begin with the database structure development, it is
object-oriented.
Work Reutilization: All the applications have the same structure, and are object-oriented. The
classes defined in an application can be exported and used in other ones, taking with them their
definitions of attributes, methods, validations, etc.
Fully scalable applications: Since the applications are object-oriented created, in order to
modify or enhance the application it is only necessary to define the new classes and configure
how they interact with the others.
Standardized and integrable applications: The business rule is defined by the class structure to
be created and by the rules and validations to be placed in each object, this way of creating an
application is not dependent on the person which performs it, as it is the code creation. The
applications are "open"; any trained person can understand a palliation created directly by ano-
ther person.
Standardization in documentation: The same application generation, as it is standardized,
automatically generates the system documentation, both the internal one and that of the user's.
Faster staff training: Staff training is much faster and less expensive.
People with not a necessarily programming profile: It is not necessary to have highly trained
staff as regards programming languages, since there can be an application generation by trai-
ning staff with functional orientation.
Closer to trial and error. Quick going back: To modify an application does not generate a
waste of weeks and weeks of codes, it is just a redefinition of a class and the creation of the
new and necessary ones.
One hundred per cent Object-oriented: The applications are one hundred per cent object-
oriented, with a much faster transition from the real life to the definition of classes than having
to break the real life down into tables, keys, and relations.
High System Building Speed: All the aforementioned factors increase the speed for the appli-
cation creation.
FlexAB Components
The approach for the application creation by utilizing FlexAB is totally different; the main idea is
to orientate everything, not only programming and its routines, to objects. That is, to define which
are the objects related with the process we need to data process, and how these objects interact
with their environment (other objects). FlexAB allows us to create objects and handle them easily
and without having to worry about the way in which data is stored (in which tables, and with
which items). The application creator's only concern is what the objects have to do, and how they
have to relate among themselves. Another important factor is that there is no programming. This
means that the code generation for the objects handling is unnecessary. The question would be: If
there is no code, how do I generate the processes which obtain information from the data? The
answer is that each object is capable of defining how its own data interact, how it interacts with
the other objects. This functionality translates into FQL functions, that is, SQL functions oriented to
the objects information handling. All the application logic is done through FQLs. Besides, it is possi-
ble to define operations that take data from FQL results, and they operate it as indicated in the
class configuration. Also, each object's integrity validations are loaded similarly. On the other hand,
part of the configuration enables the handling of messages and the running of external programs,
which can interact with FlexAB objects by utilizing COM functions.
How does FlexAB work?
MOBILE
WEB
WAP
WIN
Interfaz Estndar
de Usuario
Funciones COM
FS SRV2
FS SRV1
File System
Server
OrDBC
Transacciones
de Objetos: Altas,
bajas, vnculos,
mtodos, etc. USUARIO
DB SRV2
DB SRV3
DB SRV1
Base de Datos
Relacional
Aplicaciones
de Usuario
Otras Aplicaciones
AutoCAD
Otras Aplicaciones
Excel - Word - Project
WIN
Editor de paquetes
DE UNIVERSOS
Interfaz Estndar
de Configuracin
OrdBC: Object-Relationship DB Core
COM: Communication Module
OED: Object Editor
XRPv: X Report Viewer
HLPV: Help Viewer
WSKc: WinSock Client
LNG: Language translator
MSS: Message send (SMTP client)
OPA: Object Packing Administrator (UpLoad & DownLoad)
VER: Object Version Administrator
AUD: Object Audit Viewer
FS SRV: File System Server
WSKs: WinSock Server
SCI: Standard Configuration Interface (for MS Windows)
HTM: HTML Editor
HTB: HTML Builder
FQL: FQL Builder (SQL + XQL)
XRPb: X Report Builder
XRV: X Report Viewer
HLPM: Help Maker
PRJ: Project Management
WSKc: WinSock Client
LNG: Language translator
AUA: Object Audit Administrator
UCI: Universe Configuration Interface (for MS Windows)
SUI: Standard User Interface (for MS Windows)
FlexAB.DLL (Communication module)
WUI: WEB User Interface (for Any WEB Browser)
FlexAB.DLL (Communication module)
AUI: WAP User Interface (for Palms)
FlexAB.DLL (Communication module)
MUI: Mobile User Interface (for Mobile Telephone)
FlexAB.DLL (Communication module)
POE: Packing Object Editor (for MS Windows)
eMail: eMail Client
SMTP: SMTP Client
POP3: POP3 Client
FLEXIBLE APPLICATION BUILDER
FlexAB manipulates any type of data
file as one more attribute of an
object managed in a private server
which communicates with the client
through Winsock interfaces. This
makes it possible to maintain files
completely organized in a personali-
zed and safe way, as would happen
in a conventional file system, ena-
bling to configure freely access to
them.
In order to define behavior and
nature of FlexAB objects, the confi-
guration tool (FlexAB SIC) is provi-
ded, which allows defining in a sim-
ple way all the necessary rules,
object structure and the way in
which these relate and/or interact.
As shown in the graphic, FlexAB
communicates with database engi-
nes through its set of low level func-
tions, which make OrDBC calls, thus
allowing access to the database
engine in a standard way. At the
same time, FlexAB communicates
with the environments or interfaces
which integrate it in a standard way
through its set of business functions,
also known as "public" functions
which are in charge of operating the
system objects. The interaction of
ALL FlexAB objects and the interfa-
ces is carried out by means of XML,
enabling in this way the unlimited
manipulation of their representa-
tion, in order to show them in a
Standard Interface provided by
Appliware (FlexAB SUI), or a fully
personalized interface, built in any
system with VBA support.
FlexAB Features
DataBase
Engine
FlexAB COM
XML
OrDBC
Any Application
with VBA
Word, Excel, Project
FlexAB
SUI
EGPCad
Running Over
AutoCad
Encapsulated
Interface
Dialogs
cFileClient
CLASS WinSock
Implementation
HTML
Event
CLASS
FlexAB SCI: Standard
Configuration Interface
Class Definitions
Object Interactions
Methods & Validations
Report, FQL and HTML
Edition
F R
A
M
E W
O R K C L A S S L O W L E V E L F U N C T I O
N
P
U
B
LIC
FRA
M
EW
ORKCLASSBUSSINESLEVEL
FU
N
C
T
IO
N
FlexAB
FS
FlexAB
HLP
FlexAB
XRP
SMTP Mail
Integrated segurity
& Audit Tools
FlexAB
LNG
FlexAB
FQL
XML formatted
Objects
Public Framework CLASS
Bussines Level Functions
Framework CLASS
Low Level Functions
File System
Documents
The Standard Configuration
Interface (SCI) is part of the FlexAB
Component Suite. The SCI allows the
configuration user to create new
FlexAB applications, classes, systems,
and application users.
When a FlexAB Class is created the
configuartion user has to define its
attributes, relationship with the
other classes on the same Universe,
methods, validation rules, and the
class front end Form which will be
use by the end user to load data or
objects into the application. These
forms are created with the FlexAB-
SCI using an HTML builder. The user
can change the FlexAB generic tem-
plate automatically created by the
SCI to meet specific application
needs.
Class
Attribute
Object
Explorer
Apart from this object handling,
which is based on a object-relational
database plus object access COM
functions (what we call OrDBC), the
FlexAB suite delivers a standard
interface in order to create applica-
tions as soon as possible. The confi-
gurator can or cannot use this inter-
face, according to how he wants to
solve the interaction with the user.
We understand that 90% of the
applications can be solved by using
this interface, thus reducing deve-
lopment time and costs.
The objects present the information to the user in mar-
ket applications such as MSWord, MSExcel, MSProject,
MSOutlook, AutoCAD, besides having the possibility for
generating online reports (presented on-screen). The
information to be extracted from the object database is
obtained by an FQL. Then such data is formatted by
means of style sheets or templates, and lastly, that
information is sent to the aforementioned applications
in order to enable the user to handle it freely (distribu-
te, print, sent, etc) as if the information had been gene-
rated in those applications.
Object visualization in market applications
All files are managed by the FlexAB File System, which
only makes it possible to work locally with them, and this
means that there is no (by default) access to the server's
File System. Therefore, it has functionalities in the
FlexAB's DDL which (by utilizing WinSock) is in charge of
storing them in the server and transferring them to the
local equipment (client workplace) in order to enable
user to handle it. File transference tasks between client
and server are managed by the FlexAB File System auto-
matically and by observing the rules configured for the
FileLink's of the particular class.
File managing
D
CLASE
TEMPLATES
(Formatos / Diseos)
CLASES
(Objetos)
VISUALIZACION
(Aplicaciones)
ALMACENAMIENTO
(Inaccesible al usuario)
C
CLASE
B
CLASE
A
CLASE
METODO
SQL+XQL
METODO
SQL+XQL
METODO
SQL+XQL
File Copy of Server
New Edit View
FlexAB
Data Base
FlexAB
File System
Server
FlexAB CLIENT
(user workspace)
SERVER
(Only Admin)
FlexAB DLL
File Link
OBJECT
FlexAB
File System
Client
Object and Its
structural
relationship
Object
Attributes
Function Bar
The following figure shows the network structure of the applications with FlexAB. This structure is flexible and the figu-
re shows the complete application.
Design architecture
FlexAB
FS Server
FlexAB
DB Server
FlexAB
WEB/WAP/Mobile
Server
Domain Controler
YOUR BIG APPLICATIONS SMALL APPLICATIONS SAN
Web Browser
Client+Com+STD Interface
Client+Com+STD Interface Client+Com+STD Interface
FlexAB FS Server
FlexAB DB Server
Optional=WWM Server
TCP/IP
TCP/IP
TCP/IP
VPN
HTTP/SSL
PALM MOVIL
TCP/IP
TCP/IP
1
2
9
S
E
C
U
R
I
T
Y
A
D
M
I
N
I
S
T
R
A
T
I
O
N

O
F

T
H
E

O
P
E
R
A
T
I
O
N
INTERFACES OF SERVICES OF USERS
USERS
C
O
M
M
U
N
I
C
A
T
I
O
N
FlexAB Standard
Configuration
Interface
FlexAB
Standard
User Interface
FlexAB
Object
Packing Editor
FlexAB Universe
Configuration
Interface
User
Applications
FlexAB
Web/Wap/Mobile
User Interface
FILELINK
Operation
Components
XML
Operation
Components
Translation
Components
Object
Method
Components
Logical Component
for Data Access
Logical Components
for File Access
with Winsock Client
3
7 8
4 5 6
Data Source File System
with Winsock SRV
The following picture
shows the FlexAB
Application three
layer model which is
the base for any
application created
with FlexAB.
FlexAB
Three layer
Model
Since all the Applications developed
with FlexAB are carried out on the
same base or platform, and with the
same data structure, ALL the objects to
be created can be used in any
Application. This is FlexAB capability: it
allows scalability and integration. I can
create independent applications and
then make them interact in a simple
way, without interface programs. In
addition, all applications developed by
means of FlexAB form a family of
applications which can be used in such
a way that they can empower the
companies' own developments, and
achieve complete solutions with less
development effort.
In this way, a company utilizing FlexAB
could e-mail a bill of sale (Object) to
another company that uses another
FlexAB tool, and the latter could use
the Object without having to enter
the data again: TOTAL INTEGRATION.
Are FlexAB Applications Integrable?
Aplicacin
EGP II
Aplicacin
PIM
Aplicacin
EGP
UNIVERSO 1 UNIVERSO 2
Aplicacin
RCM
OBJETO
ORIGINAL
OBJETO
VINCULADO
OBJETO
DUPLICADO
FLEXIBLE APPLICATION BUILDER
FlexAB has the capability of representing their Objects in a graphic environment, as with CAD
applications (AutoCAD InteliCAD, etc). In this way, once the Objects and their Attributes have
been defined these can be inserted as blocks in the plans or drafts maintaining synchronism and
integrity with the objects of the database. This type of functionality is tremendously powerful for
the realization of Engineering, Architecture, GIS, etc., Applications which require that their
"object" be visualized in an administrative environment as well as graphically.
GRAPHICS
As shown in the above diagram of
FlexAB work, the latter enables the
management of all the software applica-
tions needs of any company distributed
in different Universes (database servers
and servers of different files). On the
other hand, in each Universe, within the
Model or Definitions Environment, seve-
ral Systems (Invoice and Other) can be
defined with the definitions of Classes
and Spaces that they may contain. The
figure shows the Model Environment in
which three Spaces of work have been
defined: Bill for the handling of the
billing (Billing) information (Objects),
Cities for the Cities information, and
Other for additional information. In each
of these Spaces, Classes that may be
entered and operated by Users have
been defined. Each Class defines the
information to be handled. For example,
Class H, that defines client data, shall
have a certain type of Attributes such as
Name, Client Number, Description, etc.
Note that the definitions of Classes are
general and shared among the different
Systems.
On the other hand, within the same
Universe, the Real Work Environment
exists which is that of the Systems instan-
ces in Applications and instances of
Object Classes. This work Environment
enables a system User to load data from
one of the defined Classes into the
Model Environment. For example, when
creating in the system Objects of the
above defined Class H, data will have to
be completed for, for example, the speci-
fic client Carl, Ben, Kim, etc. Users in this
environment have restricted access to
the information they access in terms of
their permits per Users Groups as shown
in both North and South groups.
The graphic also shows that only the
Administrator-type Users have access to
these work spaces: Model and Real,
having Users that belong to the North
and South Groups access only to the
environment of Instances and Objects.
For end users all information and techni-
cal nature is transparent since they just
see forms which allow them to load and
handle data (grouped in types of objects
such as Clients, Cities, Billings, etc.).
Technical work synthesis with FlexAB
OBJECT
VERSION 1
OrDBC
OBJECT
OBJECT
VERSION 0
FlexAB SUI
Edit: XML + HTML
FS
SERVER
COM
H
T
M
L
X
M
L
C
A
D
CAD XML
SPA POR ITA FRE GER ENG
H
T
M
L
X
M
L
C
A
D
Attributes (data +files)
Relations (ST +Func +Inc)
HTML
Methods (for Events)
Reports
Helps
Icons
Automatic ID's
SPA POR ITA FRE GER ENG
Creating a DOOR
Class Object
PROPERTIES
If you still have any doubt about
FlexAB power give us the chance
to show you how FlexAB works
in a real case, in a case you might
be keeping in folder and which
has not been already developed
or that you might be currently
developing. AppliWare creates it
for you in FlexAB, free of charge,
with no obligation, and in half
the time you have already estima-
ted. Please contact our sales divi-
sion for a meeting. You are not
loosing your time, get a real
demonstration, and compare the
results directly.
FlexAB is Powerful.
Would you like a
demo?
AW
AppliWare
SOLUTION
PROVIDER
How to become an AppliWare Partner
AppliWare does not develop applications. We understand that the applica-
tions must be developed by people with a specific knowledge of a solution,
who incorporate that added value into the tool they choose for the develop-
ment. That is why in AppliWare we promote the creation of alliances with
development companies or business consulting firms interested in using
FlexAB as a tool for their solutions.
Advantages of becoming a FlexAB Solutions Integrator (SI)
The advantages of becoming a member of FlexAB Official Integrators are:
Access to discussion forums
Periodic product updating
Solutions Promotion developed in AppliWare web
Access to joint promotions in fairs and events
Sent us an e-mail to
sales@appliware.biz