optimization-extension-developer

Building optimization extensions requires structuring your project with sked.proj.json, wiring handler functions, defining transformer routes, and managing state and deployment files to ensure your extension runs safely on the Skedulo Pulse optimization engine.

An optimization transformer hook is a function that intercepts optimization input or output data to modify it before or after the engine processes it. You need one when you want to filter jobs and resources or apply custom constraints to the scheduling logic.

You implement pre-optimization hooks by using the provided TransformerInput types to intercept and modify the optimization input data. This allows you to filter jobs and resources or apply custom constraints before the Pulse engine executes the scheduling run.

Optimization extensions break the data contract when they fail to return both productData and featureModel correctly. Ensuring data contract safety requires avoiding common transformer mistakes and following safe patterns when modifying optimization inputs and outputs.

TypeScript is required to develop Skedulo optimization extensions because you must use the provided TransformerInput and TransformerOutput types. These types ensure your data transformation hooks maintain the engine's data contract safely during development and tenant deployment.

You load configuration variables in an optimization extension by accessing them through the context.configVarClient object. This method ensures your custom transformation hooks can securely retrieve necessary settings during the optimization run without breaking the deployment workflow.