I am developing a software store catalog where each software item is created as a separate catalog entry using the new interface. The process leverages the out-of-the-box "step-based request fulfillment" flow, which retrieves assignment and approval group details from a configuration table and processes them at runtime. Currently, this requires creating separate assignment and approval records for each catalog item. Since most software items are assigned to and approved by the same team, this setup creates significant maintenance overhead, as new configuration records must be added to the table whenever a new software catalog item is introduced. Given that using this flow is an architectural requirement, what would be the most efficient approach to reduce maintenance efforts and streamline the process?
