DeeEmm
Member
Hi all.
I've decided to use Fabrik to rewrite a web based app that I originally wrote using Logos form and reports manager (LFRM) but would like to better understand the limitations / possibilities of Fabrik.
Out of all of the offerings in the JED, Fabrik seems to most closely fit the bill and was by far the easiest to use. I've already created a test installation and created a basic form and visualization in just a few minutes. The interface, its layout and the terminology used make it a very intuitive experience, so hats of to the Author(s).
My web app is basically an incident reporting and tracking service. Incidents are created and details entered. This part is easy enough to figure out in Fabrik. The incident can then generate further follow up actions that need to be carried out and updates can be entered to record progress of these further actions. The progress can be tracked by the author and by management.
Part of the service revolves around automatic reporting, informing members of a predefined usergroup (management) when certain thresholds are reached. For example, when incidents are not closed within a certain period of time or when a pre-defined number of incident types are opened simultaneously, an email will be automatically generated and mailed to the management.
Is this functionality something that Fabrik can handle? Is it possible to run a CRON job to interrogate the database and send emails out based on the results?
I would be interested to learn of any similar usage of Fabrik and any insights that you may have in operating Fabrik in a similar manner to this.
Thanks in advance.
/DM
I've decided to use Fabrik to rewrite a web based app that I originally wrote using Logos form and reports manager (LFRM) but would like to better understand the limitations / possibilities of Fabrik.
Out of all of the offerings in the JED, Fabrik seems to most closely fit the bill and was by far the easiest to use. I've already created a test installation and created a basic form and visualization in just a few minutes. The interface, its layout and the terminology used make it a very intuitive experience, so hats of to the Author(s).
My web app is basically an incident reporting and tracking service. Incidents are created and details entered. This part is easy enough to figure out in Fabrik. The incident can then generate further follow up actions that need to be carried out and updates can be entered to record progress of these further actions. The progress can be tracked by the author and by management.
Part of the service revolves around automatic reporting, informing members of a predefined usergroup (management) when certain thresholds are reached. For example, when incidents are not closed within a certain period of time or when a pre-defined number of incident types are opened simultaneously, an email will be automatically generated and mailed to the management.
Is this functionality something that Fabrik can handle? Is it possible to run a CRON job to interrogate the database and send emails out based on the results?
I would be interested to learn of any similar usage of Fabrik and any insights that you may have in operating Fabrik in a similar manner to this.
Thanks in advance.
/DM