Installation options
On-premises or cloud – suited to your operating environment.
ROLES · VERSIONS · DEPLOYMENT · SECURITY · DOCUMENTATION
Operations, security and scale. Transparent and secure.
Roles, app access, versions and deployments form a traceable operating model. Flowzy provides a basis for stable and controlled operations.
Permissions, roles & app access
Set clear access rules and responsibilities.
Versioning & deployment
Manage changes traceably and publish safely.
Visual documentation
Document applications, processes and configurations clearly.
FLOWZY INSTALLATION OPTIONS
Operate where it fits your IT.
Flowzy can run in your own environment or privately hosted by ilicos. Architecture, access and responsibilities remain clearly defined in both cases.
On-premises, virtualised or self-hosted
Flowzy runs in your controlled IT environment – in your data centre, virtual infrastructure or Azure tenant. You retain responsibility for data, access and operations.
Hosting by ilicos
ilico hosts Flowzy for you in Germany.
ACCESS MODEL · RESPONSIBILITY
Permissions, roles & app access.
Flowzy separates roles, permissions and app access. A role describes a person’s task; assigned permission profiles determine what they can use.
Roles
App Operator
Uses approved apps and performs business processes.
App Designer
Creates and changes apps, pages and workflows.
Access Control Administrator
Manages permission profiles and user assignments.
A person may have several roles. A role alone does not grant access to a specific app.
Permissions
- View — View and open an app or object
- Execute — Run actions and workflows
- Modify — Change configuration and content
Operators mainly need View and Execute. Modify is for design and administration tasks.
App access
A user’s access has two components:
- App-Operator-Profil — General access to the Flowzy interface
- App-spezifisches Profil — Permitted apps, pages and actions
Multiple profiles are combined. The resulting effective permissions matter, not just a role or profile name.
RELEASES · VERSIONS · ENVIRONMENTS
Versioning & deployment.
Flowzy clearly separates versions, activation, publication and deployment as stages of an app lifecycle.
Key terms
Version
Defined state of a page, workflow or another design object
Activate
Select the version used in the respective runtime path
Release
Collection of approved app objects and their dependencies
Publish
Make a release available to its intended users on an instance
Deployment
Transfer an approved release to a target environment
Rollback
Restore a previously verified state
Lifecycle
- 01Develop
- 02Version
- 03Test
- 04Activate
- 05Publish
- 06Deploy
- 07Monitor
Pages and workflows have their own versions. A new or active version does not automatically update every link and dependency within the app.
TRANSPARENCY · PROJECT KNOWLEDGE
Visual documentation.
Flowzy makes project development transparent and traceable. Changes to apps, pages and workflows remain visible across versions and can support customer documentation.
Visually traceable
The structure, processes and dependencies of a project are shown in Flowzy. Changes are recorded technically and remain visually clear.
Compare versions
Different project states can be compared to see what changed and which version is currently in use.
Automated documentation
Project and configuration data can be exported in a structured way and automatically incorporated into customer documentation processes. Exportable items include apps, pages, workflows and other design objects.
Structured export
AppsPagesWorkflowsNavigationData objectsConfiguration
THE RESULT Current, traceable and reusable project documentation without duplicate manual maintenance.
PLATFORM QUESTIONS
What you want to know before you start.
No, not necessarily. We ideally bring existing systems and capabilities into the optimal process. We show you the options, and you decide.
Flowzy’s data transformation module combines a range of integration technologies with visual mapping to bring field names and values into the required target structure and format.
We compare the available features with your requirements and configure the necessary adjustments, process and automation components, and integrations.
Flowzy can be installed locally, in a virtualised environment, in your data centre, in your private cloud environment (such as Microsoft Azure), or in a system environment hosted by ilicos in Germany.
After process analysis and agreement on scope, ilicos leads the technical implementation. After go-live, ilicos remains available to support and extend the system.
A QUESTION FROM US
If you could change one thing about your processes now, what would it be?
Your processes, your rules. Tell us what you need – we are listening.