Skip to content
TheChatArchiveThe Chat Archive
Googlegemma-3n-e4b-it· GoogleHugging Face LMArena Human Preference 140K

the tool will be selfhosted. LimeSurvey is okay but is its missing Workflow automation:…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Qwenqwen3-235b-a22b-no-thinking’s answer.
  1. User

    the tool will be selfhosted. LimeSurvey is okay but is its missing Workflow automation: (e.g., submission → admin review → rejection with feedback → revision).

  2. Google Assistant

    You are absolutely right to highlight the workflow automation aspect. While LimeSurvey is a powerful open-source survey tool, its built-in workflow automation for complex scenarios like rejection with feedback and revision isn't as straightforward as some other options.

    Let's revisit the suggestions, keeping your need for self-hosting and robust workflow automation in mind. Here's a breakdown of options, with LimeSurvey's limitations clearly stated, and stronger recommendations:

    1. Formr (Strong Recommendation)

    • Self-Hosted: Yes, it's designed for self-hosting.
    • Multi-Section Questionnaires: Excellent support.
    • User Authentication: Built-in user accounts and login.
    • Admin Review Workflow: Formr has a built-in review workflow. Admins can review submissions, add comments, and reject forms with specific feedback. The rejected form is then automatically sent back to the employee.
    • Employee Dashboard: Employees can see their submitted forms and their status (e.g., "Pending Review," "Rejected," "Completed").
    • Workflow Automation: This is Formr's strength. It handles the submission -> admin review -> rejection with feedback -> revision cycle well.
    • Ease of Use: Relatively easy to set up and use, with a user-friendly interface.
    • Limitations: While powerful, it might not have every advanced feature of commercial survey platforms.

    2. Nextcloud Forms (Good Option, but requires more setup)

    • Self-Hosted: Yes, it's a module within the Nextcloud ecosystem.
    • Multi-Section Questionnaires: Supports multi-section forms.
    • User Authentication: Leverages Nextcloud's user authentication.
    • Admin Review Workflow: Nextcloud Forms has a review workflow, but it might require some configuration and potentially scripting to achieve the exact rejection-with-feedback-and-revision flow you desire. You'll likely need to use Nextcloud's scripting capabilities (PHP) or integrate with other Nextcloud apps.
    • Employee Dashboard: Employees can see their submitted forms in the Nextcloud Forms interface.
    • Workflow Automation: Requires more manual configuration or scripting to achieve the desired level of automation.
    • Integration: Seamlessly integrates with other Nextcloud apps (file storage, calendar, etc.).
    • Learning Curve: Can have a steeper learning curve if you're not familiar with Nextcloud.

    3. Odoo Forms (Powerful, but more complex)

    • Self-Hosted: Yes, Odoo is a self-hosted ERP system, and Forms is a module within it.
    • Multi-Section Questionnaires: Excellent support for complex forms.
    • User Authentication: Uses Odoo's user management system.
    • Admin Review Workflow: Odoo Forms has a robust workflow engine. You can configure a workflow that includes admin review, rejection with comments, and automatic routing back to the employee.
    • Employee Dashboard: Employees can see their submitted forms and their status within the Odoo interface.
    • Workflow Automation: Odoo's workflow engine is very powerful and allows for highly customizable automation.
    • Complexity: Odoo is a full ERP system, so it has a steeper learning curve than Formr or Nextcloud Forms. You'll need to set up and configure the entire Odoo environment.
    • Cost: While the core Odoo Community Edition is open-source, you might need to pay for certain modules or support.

    Why LimeSurvey is less ideal for your workflow:

    • Workflow Automation: LimeSurvey's workflow capabilities are limited compared to the other options. While you can set up some basic workflows, it's not designed for the complex rejection-with-feedback-and-revision scenario you described. You'd likely need to rely on external scripting or integrations, which adds complexity.
    • User Experience: The user interface can feel a bit dated compared to Formr or Nextcloud Forms.

    Summary Table:

    FeatureFormrNextcloud FormsOdoo FormsLimeSurvey
    Self-HostedYesYesYesYes
    Multi-SectionExcellentGoodExcellentGood
    User AuthBuilt-inNextcloudOdooLimited
    Admin Review WorkflowExcellentRequires ConfigExcellentLimited
    Employee DashboardYesYesYesLimited
    Workflow AutomationExcellentRequires ScriptingExcellentLimited
    Ease of UseHighMediumLowMedium

    Recommendation:

    For your specific requirements, Formr is the best balance of features, ease of use, and workflow automation. It's designed for this type of scenario and will likely require the least amount of configuration.

    If you're already heavily invested in the Nextcloud ecosystem, Nextcloud Forms is a viable option, but be prepared for more configuration and potential scripting.

    Odoo Forms is a powerful choice if you need a full ERP system and have the resources to manage its complexity.

    I strongly advise trying out Formr first. It has a free tier and is relatively easy to set up for testing. You can then evaluate whether it meets your needs before committing to a full deployment.

  3. User

    give me the complete roadmap how to build Workflow automation: (e.g., submission → admin review → rejection with feedback → revision). in lime survey

  4. Google Assistant

    You're right to ask for a detailed roadmap for workflow automation in LimeSurvey. While it's not as straightforward as Formr or Odoo, it's possible to achieve the desired workflow with a combination of LimeSurvey features and potentially some scripting. Here's a comprehensive roadmap outlining the steps involved:

    Phase 1: Setting up the Basic Survey and Submission

    1. Create Your Survey: Design your multi-section questionnaire in LimeSurvey. Ensure you have the necessary questions and sections.
    2. Configure Submission Settings:
      • Enable Submission Tracking: Go to Admin -> Settings -> General and ensure "Enable submission tracking" is checked.
      • Submission Confirmation: Configure the submission confirmation message that employees will see.
      • User Authentication: Ensure user authentication is enabled (Admin -> Settings -> General -> "Enable user authentication"). This will allow employees to log in and see their submissions.

    Phase 2: Implementing the Admin Review Workflow

    1. Create a Review Group (Optional but Recommended): In Admin -> User Management -> Groups, create a group for your administrators who will be responsible for reviewing submissions. This helps in managing access.
    2. Configure Review Permissions: In Admin -> Settings -> Permissions, ensure that the review group (or individual admins) has the necessary permissions to:
      • View submitted surveys.
      • Access individual submission details.
      • Mark submissions as "Rejected."
      • Add comments/feedback to submissions.
    3. Set Up a Review Queue (Manual Approach): Since LimeSurvey doesn't have built-in automated review queues with feedback, you'll need to rely on manual review.
      • Admins will periodically log in to the LimeSurvey admin panel (Admin -> Submissions) to review new submissions.
      • For each submission, they will open it and decide whether to accept or reject it.

    Phase 3: Handling Rejection with Feedback

    1. Manual Rejection: When an admin decides to reject a submission:
      • They will select the submission in the Admin -> Submissions page.
      • They will click on the "Reject" button.
      • Crucially, they will add feedback in the "Comments" field for that specific submission. This is where you'll provide the missing information or details required.
    2. Notification to Employee (Manual Approach): LimeSurvey doesn't have automated email notifications for rejection with feedback out of the box. You'll need to implement this manually:
      • Admins will manually copy the rejection details (including the feedback) and send an email to the employee who submitted the form.

    Phase 4: Implementing the Revision Process

    1. Employee Receives Feedback: The employee receives the rejection email with the admin's feedback.
    2. Employee Updates the Survey: The employee logs back into LimeSurvey (Login page) and finds their submitted survey in their dashboard (My Submissions).
    3. Employee Resubmits: The employee makes the necessary updates to their survey responses and resubmits the form.
    4. Admin Reviews Revised Submission: The admin logs back into the admin panel (Admin -> Submissions) and reviews the revised submission.
    5. Admin Accepts or Rejects Again: The admin can then accept the revised submission or reject it again, providing further feedback if needed.

    Phase 5: Potential Enhancements with Scripting (Advanced)

    To automate parts of this workflow, you might need to use LimeSurvey's scripting capabilities (PHP) or integrate with external tools. Here are some potential enhancements:

    1. Automated Email Notifications: You could write a simple PHP script that triggers when a submission is marked as "Rejected." This script could then automatically send an email to the employee with the rejection details.
    2. Automated Routing (More Complex): For a more automated routing system, you could potentially:
      • Create a custom script that monitors the status of submissions.
      • Based on the rejection status, the script could automatically send an email to the employee with the feedback and a link back to their survey.
      • This would require a deeper understanding of LimeSurvey's API and PHP.
    3. Custom Dashboard Views: You could potentially create custom dashboard views for employees to see the status of their submissions more clearly.

    Limitations of LimeSurvey for Full Automation:

    • No Built-in Workflow Engine with Feedback: LimeSurvey lacks a robust, visual workflow engine that automatically routes submissions and captures feedback.
    • Limited Automation of Notifications: Automated email notifications for specific workflow events require scripting.
    • Manual Review is Primarily Required: The core review and rejection process relies heavily on manual admin intervention.

    Key Considerations:

    • Complexity: Implementing a fully automated workflow in LimeSurvey can be complex and require technical expertise in PHP and the LimeSurvey API.
    • Maintenance: Any custom scripts will require ongoing maintenance and updates.
    • User Experience: Ensure that the manual steps and any automated notifications are clear and user-friendly for both admins and employees.

    In conclusion, while LimeSurvey can facilitate this workflow, achieving full automation requires manual steps and potentially custom scripting. Formr or Odoo Forms would offer a more streamlined and automated experience for this specific use case. However, if you are already invested in LimeSurvey and have the technical resources, the roadmap above outlines how to build the necessary functionality.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.