feature list

• A complete separation of case processes where each process has:
  • Its own set of administrators.
  • Its own subset of users with access.
  • Its own imported subset of the global resources such as users, forms or data imported from external systems.
  • Its own advanced but optional permission model.
  • Its own resources such as:
    • forms and validation rules for them.
    • data imported from external systems
    • categories for tagging users and objects
    • link types
    • role types
    • various settings
• Case workflow using directed graphs of stages and transitions defined per Process.
  • All validation tied into stages and transitions meaning that a user can always save invalid cases, but the available transitions in the graph will then be limited.
  • Automatic graphical rendering of workflow graphs visually showing current stage and available transitions per case.
  • Optional automatic transferral of responsibility based on stage transitions.
• Fully user defined forms and fields per Process with many different field types.
  • Customizable submission forms per Process for creating and editing cases.
  • Customizable additional forms that can be added to cases by the user or automatically when a case makes certain transitions in the workflow graph.
• Separate user and person objects so that persons that are not users can still be entered and referred to.
• Role based assignment meaning that users (or persons) can be assigned specific roles in a case.
  • Builtin singular roles are #responsible, #reporter, #source.
  • Builtin multiple roles are #assigned, #alerted, #interested.
  • Additional custom role types can be defined per case Process.
• Simple attachments handling
• Bidirectional typed links between cases even across Processes.
• Complete and advanced email integration using POP3 and SMTP.
  • Ability to monitor multiple POP3 accounts each using multiple aliases.
  • Case submission using cloning of prepared case prototypes chosen based on the email address.
  • Automatic assignment of roles #alerted and #interested based on the CC: and TO:-fields in cases created by email.
  • Automatic attachment extraction
  • Subsequent threaded discussion using email in combination with the web UI. Users can participate using email only.
• Complete history based on full transaction logging. This also enables offline operation.
• Advanced free text indexing using Swish-e.
• Advanced search and filtering based on composable filters that generates database queries with index support.
• Full dynamic abilities to change workflow model, forms, fields and validation rules during runtime.
• Dynamic import of external objects using ODBC or files. Typical usage is importing various objects from external systems and use them in selection lists in case forms.
• Advanced event/subscription model for fine grained user defined notifications by email.
• Simple and clean user interface with integrated embedded wiki help, tooltips throughout the system and Ajax enhanced functions.
• Integrated scheduler for periodically running services.
• SOAP service for programmatic remote access.
• Plugin architecture to easily add functions and integrations enabled per Process.
• Translation architecture so that Gjallar can run in multiple languages.
• LDAP integration to mirror user accounts from the network, for example Active Directory.
• Logging architecture including a filtering log viewer, log file rotation and a log watchdog able to send emails to alert an administrator of abnormal conditions.
• Very flexible component architecture for the web user interface built upon the continuation based web framework Seaside. This makes it trivial to add or modify different parts of the user interface.
• Simple but flexible user defined reports and export of data into CSV, XML or HTML files.
• Unit tests for most parts of the system, and we are adding more.