Smart Actions
This is the official documentation of the forestadmin-agent-django and forestadmin-agent-flask Python agents.
In legacy agents declaring a Smart Action was a two-step process:
First, you had to declare by changing the parameters of the
collectionfunction in the appropriateapp/forest/*.pythonfile.Then, you had to implement the action by creating a route handler in the appropriate
app/urls.py/app/views.pyfile.In the new agent, the process is simplified to a single step.
Code cheatsheet
type: 'single' type: 'bulk' type: 'global'
scope: 'Single' scope: 'Bulk' scope: 'Global'
download: True
generate_file: True
reference: 'otherCollection.id'
{ type: 'Collection', collection_name: 'otherCollection' }
enums: ['foo', 'bar']
{ type: 'Enum', enum_values: ['foo', 'bar'] }
Request object
context.get_record_ids()
Response object
return result_builder.success(...) return result_builder.error(...) ...
Steps
Step 1: Calling add_action for the appropriate collection
add_action for the appropriate collectionStart by calling the add_action function on the appropriate collection and passing the appropriate parameters.
Most notably, you will need to pass:
typeshould becomescopeNote that the values are now capitalized (e.g.
singlebecomesSingle)Legacy agents defaulted to
'bulk'if no type was specified. The new agent requires you to specify the scope.
downloadshould becomegenerate_file. This is still a boolean and the same value can be passed.endpointandhttpMethodshould be removed. The agent will now automatically handle the routing.
Step 2: Porting the form definition
Forms are now defined in the form property of the action.
You can simply copy the field's definition from the legacy agent to the new agent with the following differences:
fieldsshould becomeform.widgetchoice is no longer supported. A default widget will be used depending on the field type.hookcan be removed, those will be handled by the new agent automatically.referenceno longer exists. Use{ type: "Collection", collection_name: '... }instead.enumsno longer exist. Use{ type: "Enum", enum_values: ['...'] }instead.
Step 3: Porting the route to the new agent execute function
execute functionIn the legacy agent, users had to implement the action by creating a route handler in the appropriate app/urls.py file.
This is no longer needed as the new agent provides a context object that contains all the information that is needed to implement the action.
When porting the route handler to the new agent, you will need to:
Move the body of the route handler to the
executefunction of the action.Replace
self.get_ids_from_request()call withcontext.get_record_ids().Replace
return JsonResponse();calls withreturn result_builder.success()orreturn result_builder.error(), or the appropriateresult_buildermethod.
Step 4: Porting Smart Action hooks
Load hooks and change hooks have been replaced on the new agent by the possibility to use callbacks in the form definition.
Here is an example of a load hook where the default value of a field is set to 50 euros converted into dollars:
And another for a change hook which makes a field required if the value of another field is greater than 100:
Last updated
Was this helpful?