In the trigger operation, I hope to increase the function of converting the database

For example, I want to fill in the requirements database with specific dates and verification methods, and automatically convert them into object database

For a given database, the actions available in automations are effectively based on / limited to the fields/relations that exist for that database.
So, if you want an automation in your requirements database to create an entity in the object database, then the databases need to be related in some way.
To achieve ‘convert’, you would have an action to create an object (with it’s fields populated based on the triggering requirement’s fields) and then (optionally) delete the original requirement entity.

1 Like