Nextworld's Internal Hot Patching Process

When a critical issue is identified in a Nextworld production release requiring an urgent fix, does Nextworld follow the same hotpatching process as its customers?

If by customers you mean SD Partners then yes, it does, and it goes through a formal internal approval process as part of that. What Nextworld considers to be customers are end consumers of the platform and not responsible for delivering/hot patching metadata to production environments.

2 Likes

Thanks and just to confirm then, only the objects in a metadata manifest will move as a part of the hot patch? Just want to make sure this wouldnt be similar to the auto a patch that moves all objects in an environment.

Hot Patches only move the metadata listed on the associated manifest. Nextworld as a platform also does ‘No-Code Platform’ hot patches which aren’t metadata but are the underlying code that displays the platform on your web browser and that interprets the metadata; my understanding is the entire build is shipped for that type of hot patch.

Also FYI scheduled patches which in 2026 are scheduled to happen every 4 weeks do not move all metadata objects in an environment. They only move metadata that has been modified since the cutoff of the previous scheduled patch.

1 Like