Using Requests
- Support Specialist 5
- Former user (Deleted)
- Customer Care
- Igor Stjepanovic
business professional
Requests are the simplest type of data collection in Gruntify, used for the quick recording and submission of data into smart forms. If the term request is not right for your organization, you can change it to Audit, Claim, Deal, Device, Incident, Inspection, Report, Survey, Tender or Update.
A field worker or controller in the office can create a New Request by clicking New Request, filling in the form, uploading any media, allocating the request to a location, then saving the form. The data that has been collected is automatically timestamped and the location recorded.
You can also assign selective permissions to Requests via their forms - controlling who can create, edit and view particular types of requests.
Requests are good for simple workflows, one-off inspections or audits, or tasks that can be done in one visit.
Requests have a very simple workflow. The request is created as “Submitted” and then either “Accepted” or “Rejected” by the controller staff in the Administration web-app.
Archiving Requests
Often when dealing with historical data, you want to keep it on hand but secure it so that it is free from modification. This is exactly what the ‘Archived’ Request status is built for. You can archive any Request that has been Accepted or Rejected. By default, only users with the ‘Owner’ role can mark Requests as Archived. Archiving a Request makes it permanently read-only, and requires an additional permission in your role. You may archive an individual Request by clicking it and changing the status in the top-right of your screen. Alternatively, you may also Bulk Archive Requests.
Assigning Requests
web App
This feature enables assignment and tracking within the Requests module, allowing team members to allocate Requests to specific users on the web app. When assigning a Request, the assignor can include notes to provide context or instructions, helping the assignee understand the task more clearly. Once assigned, the assignee receives a notification with all relevant details for their review. Additionally, the Requests Manager page includes a filter by assignee, making it easier for users to view and manage Requests based on individual responsibilities.
If you have more complex needs, including tracking work time on each task, setting up recurring schedules, and dispatching based on the skill set, then you need Jobs.
This tutorial should give you some ideas on how you can use Requests.
If you are working your way through the Getting Started tutorial trail, go on to Step 6: Using Jobs.