Hey all!
I’m really excited to see Generative Scheduling finally out in the wild! While first releases always have room for improvement, here are a few things I noticed after tinkering with it for a few hours:
- The filters are currently quite basic and difficult to navigate. The most unintuitive aspect is the lack of a 1:1 relationship between FGS and FPT/SG naming conventions:
- Resources = Task Names
- Categories = Asset Types
- Tags = Pipeline Steps
- Custom fields need to be able to mark the production order/priority of main entities (e.g., episodes that must be completed in a specific, non-alphabetical order, and its child entities’ tasks).
- Activity IDs display what each entity is and their ID in SG, but they are not filterable yet. This results in an endless list of tasks to browse through. However, kudos on the performance—loading this much data without crashing my browser is impressive! I can’t wait for this performance to be ported into FPT/SG.
Back in FPT/SG, there NEEDS to be a way to revert to previous states after applying proposed dates. It’s too risky not having an easy rollback option in case of user error.
Either way, these are exciting developments after so much anticipation!
Congrats to the SG team! 