Please be sure of your agent type and version and pick the right documentation accordingly.
This is the documentation of the forest-express-sequelize and forest-express-mongoose Node.js agents that will soon reach end-of-support.
forest-express-sequelize v9 and forest-express-mongoose v9 are replaced by v1.
Please check your agent type and version and read on or switch to the right documentation.
This is still the latest Ruby on Rails documentation of the forest_liana agent, you’re at the right place, please read on.
This is the documentation of the django-forestadmin Django agent that will soon reach end-of-support.
If you’re using a Django agent, notice that django-forestadmin v1 is replaced by v1.
If you’re using a Flask agent, go to the v1 documentation.
Please check your agent type and version and read on or switch to the right documentation.
This is the documentation of the forestadmin/laravel-forestadmin Laravel agent that will soon reach end-of-support.
If you’re using a Laravel agent, notice that forestadmin/laravel-forestadmin v1 is replaced by v3.
If you’re using a Symfony agent, go to the v1 documentation.
Please check your agent type and version and read on or switch to the right documentation.
Create a Smart Collection with Amazon S3
Creating the Smart Collection
On our Live Demo, we’ve stored the Legal Documents of a Company on Amazon S3. In the following example, we show you how to create the Smart Collection to see and manipulate them in your Forest admin.
First, we declare the legal_docs collection in the forest/ directory. In this Smart Collection, all fields are related to S3 attributes except the field is_verified that is stored on our database in the collection documents.
You can check out the list of if you need it.
You MUST declare an id field when creating a Smart Collection. The value of this field for each record MUST be unique. On the following example, we simply generate a random UUID.
First, we declare the legal_docs collection in the forest/ directory. In this Smart Collection, all fields are related to S3 attributes except the field is_verified that is stored on our database in the collection documents.
You MUST declare an id field when creating a Smart Collection. The value of this field for each record MUST be unique. On the following example, we simply generate a random UUID.
You can add the option isSearchable: true to your collection to display the search bar. Note that you will have to implement the search yourself by including it into your own get logic.
Implementing the GET (all records)
At this time, there’s no Smart Collection Implementation because no route in your admin backend handles the API call yet.
In the file routes/legal_docs.js, we’ve created a new route to implement the API behind the Smart Collection.
To access the details view of a Smart Collection record, you have to catch the GET API call on a specific record. One more time, we use a custom service services/s3-helper.js that encapsulates the S3 business logic for this example.
To access the details view of a Smart Collection record, you have to catch the GET API call on a specific record. One more time, we use a custom service services/s3-helper.js that encapsulates the S3 business logic for this example.
To handle the update of a record we have to catch the PUT API call. In our example, all S3-related fields are set as read-only and only is_verified can be updated.
Now we are able to see all the legal documents on Forest Admin, it’s time to implement the DELETE HTTP method in order to remove the documents on S3 when the admin user needs it.
On our Live Demo example, creating a record directly from this Smart Collection does not make any sense because the admin user will upload the legal docs in the company details view. For the documentation purpose, we catch the call and returns an appropriate error message to the admin user.
/routes/legal_docs.js
...
router.post('/legal_docs', permissionMiddlewareCreator.create(), (request, response) => {
response.status(400).send('You cannot create legal documents from here. Please, upload them directly in the details view of a Company');
});
...
module.exports = router;
/routes/legal_docs.js
const P = require('bluebird');
const express = require('express');
const router = express.Router();
const models = require('../models');
const S3Helper = require('../services/s3-helper');
const Serializer = require('../serializers/legal_docs');
// ...
router.post('/legal_docs', (req, res, next) => {
res
.status(400)
.send(
'You cannot create legal documents from here. Please, upload them directly in the details view of a Company'
);
});
module.exports = router;
You can check out the list of if you need it.
The logic here is to list all the files uploaded on a specific S3 Bucket. We use a custom service services/s3-helper.js for this example. The implementation code of this service is .
Finally, the last step is to serialize the response data in the expected format which is simply a standard document. We use the very simple library for this task.
The logic here is to list all the files uploaded on a specific S3 Bucket. We use a custom service services/s3-helper.js for this example. The implementation code of this service is .
Finally, the last step is to serialize the response data in the expected format which is simply a standard document. We use the very simple library for this task.
The implementation of the reconcileData() and Serializer.serialize() functions are already described in the section.
The implementation of the reconcileData() and Serializer.serialize() functions are already described in the section.
The implementation of the reconcileData() and Serializer.serialize() functions are already explained in the section.
The implementation of the reconcileData() and Serializer.serialize() functions are already explained in the section.
