FormCreator was GLPI's most popular plugin for years. With GLPI 11, its forms were incorporated into the core. See what changes and when to use each option.
What FormCreator does (GLPI 10)
- Custom forms with conditional fields
- Visual service catalog for self-service
- Fields: text, dropdown, checkbox, upload, date, textarea
- Sections and display logic based on answers
- Automatic ticket creation from the form
- Integrated approval workflow
What native forms do (GLPI 11)
- Visual forms with a drag-and-drop editor
- Conditional fields and sections
- Direct integration with the core (no plugin required)
- Linking to ticket categories and templates
- Visibility by profile and entity
Comparison
| Feature | FormCreator | GLPI 11 Native |
|---|---|---|
| Conditional fields | Yes | Yes |
| Sections | Yes | Yes |
| Visual catalog | Yes | Yes |
| Approval | Yes | Yes |
| Compatibility | GLPI 9 and 10 | GLPI 11+ |
| Maintenance | Plugin (community) | Core (Teclib) |
When to use each one
- GLPI 10: use FormCreator – it is the only option for custom forms
- GLPI 11: use native forms – FormCreator is not compatible
- Migrating 10→11: document your FormCreator forms first and recreate them in GLPI 11
