How to Store Plugin Data in Fusion Field Service

Hi everyone,

We are planning to create a plugin that will be displayed before a route is activated. The user will enter certain details in the plugin, and once the details are submitted, the route will be activated.

We would like to understand whether there is a way to persist the data entered through the plugin in Fusion Field Service. Specifically, can this information be stored against each resource for each day, either using a standard field or a custom field through an available API or configuration?

What would be the recommended approach for persisting the plugin-entered data in Fusion Field Service before the route is activated, while ensuring that the data is associated with the appropriate resource and date?