Attach an example of a good file to a file request
Updated
Attach a sample of what you want to a file request, and Aero compares each customer upload with it. You can also let customers download the example so they know what to send.
This feature is available when it's turned on for your organization. If you don't see it, contact your OnRamp team.
Before you begin
The task needs a Request Files element in its form.
To edit a task's form inside a project, you need permission to manage that project's subtasks. Without it, the task builder is read-only. Playbook tasks don't have this limit.
If you plan to share the example with customers, use a sample with no real customer data.
Attach an example file
Open the task's form in the task builder.
Select the Request Files element to open its Properties settings. The example fields are available when file checks are turned on for your organization. If you don't see them, contact your OnRamp team.
Optional: In What does a good file look like?, describe what a good upload contains.
In Example of a good file, attach your sample file. This field is optional, and Aero uses up to two files. Duplicates are ignored.
Optional: To let customers see the example, turn on Let customers download the example. This toggle appears only after you attach a file.
Uploads are checked when the request has a description, an example, or both. An example on its own is enough to turn on the check. Each request allows 25 checks in any 24-hour period. Once it reaches that limit, new uploads to it aren't checked until earlier checks are more than 24 hours old. A file that matches one already reviewed against the same description and examples reuses that review, and it doesn't count toward the limit.
Aero can read PDFs, images (.png, .jpg, .jpeg, .gif and .webp), Word (.docx), PowerPoint (.pptx), Excel (.xlsx and .xlsm), CSV and text (.txt and .md) files. Other file types still upload, but Aero doesn't check them. The customer sees that OnRamp AI can't review this type of file yet and that their team will review it. Files larger than 20 MB also upload without a check, and the customer sees a message saying so.
What customers see
If Let customers download the example is off, customers don't see the example. It's left out of what the customer portal receives. Your team still sees it in the app.
If the toggle is on, customers see See an example of a good file under the request and can download it.
Test the check with a sample file
You can test the check on a saved Request Files step in a playbook task. This test isn't available on a task inside a project.
In the element's Properties, go to Try it with a file.
Select Try with a file and choose a file to upload.
The result shows under What the customer would see. The file you upload isn't saved. To test again, select Try another file.
The test needs a description or an example first. If you change either one after a test, the app warns that the result may be out of date. Select Check followed by the file's name to run it again.
Changing the description or the examples also means customer files are reviewed again against the new version.