Added action that creates lists where are added asset versions by specified filters. The filtering supports status name/s and custom attribute values. Single list definition can have multiple filters to match the condition. It does support only AssetVersions assignment.
The action has chrono callback so it can run some of the lists creation automatically on specific day and time.
Additional information
The list is not created if there are no AssetVersions to assign, which may be confusing. Maybe the list should be created all the time?
Testing notes
Create addon package and upload it to AYON server.
Use the addon in a bundle.
Setup the action in ayon+settings://ftrack/service_event_handlers/create_daily_lists.
For simple testing just create list definitions and add filters e.g. to add all AsserVersions with Approved status.
For automated testing also mark at least one of the definitions to Run automatically and change cycle hours (I would recommend use current time +3 minutes (If it is 16:43 then use 16:46:00) -> to propagate cycle hour settings you have to restart processor service.
Start service. Please use service_tools in repository root (read its readme to know how to use it). Don't forget you can use --variant <Settings variant or Dev bundle name> arguments when testing in staging or in dev bundle.
Run the action and validate the list is created and has assigned AssetVersions.
Remove the created list and wait for automated run via cycle hours.
Description
Added action that creates lists where are added asset versions by specified filters. The filtering supports status name/s and custom attribute values. Single list definition can have multiple filters to match the condition. It does support only AssetVersions assignment.
The action has chrono callback so it can run some of the lists creation automatically on specific day and time.
Additional information
The list is not created if there are no AssetVersions to assign, which may be confusing. Maybe the list should be created all the time?
Testing notes
ayon+settings://ftrack/service_event_handlers/create_daily_lists. For simple testing just create list definitions and add filters e.g. to add all AsserVersions withApprovedstatus. For automated testing also mark at least one of the definitions toRun automaticallyand change cycle hours (I would recommend use current time +3 minutes (If it is 16:43 then use16:46:00) -> to propagate cycle hour settings you have to restart processor service.service_toolsin repository root (read its readme to know how to use it). Don't forget you can use--variant <Settings variant or Dev bundle name>arguments when testing in staging or in dev bundle.