Enable product records to use the shared job engine
Purpose
Product areas connect their own record rules and persistence to a common job engine rather than defining separate bulk-processing behavior.
How It Works
Each product area declares which record operations can use the engine. The declaration connects input contracts and authority to domain validation and writes. Unsupported declarations fail before serving requests. Consumer persistence supplies the common job records under workspace security. CRM uses workers and bulk workflows for its record jobs. Platform processes bounded datasets within request handling after the submission transaction commits. Its field definitions and custom records still use their domain rules. Platform has no rollback declaration for these imports. Membership’s operation declarations remain incomplete integration rather than runnable job surfaces. The product should complete that foundation before relying on Membership migration.
Relationships
- Submission selects declared operations.
- Migration runs submit supported datasets to those operation surfaces.