After you change the contents of an application, you might want to redeploy the application to apply the changes.
You might redeploy the application for the following reasons:
You edit, add, or delete application objects in a full application and you want to apply the changes to the deployed full application.
You delete application objects in an incremental application and you want to apply the changes to the deployed incremental application.
An application patch for an incremental application contains a large number of objects and it is inefficient for the user to deploy the patch. Deploying a patch might be inefficient if the patch contains a large number of objects due to patch inheritance or there is a large number of affected objects in the run-time application.
When you deploy an edited application, you choose to retain or discard application state information. State information refers to mapping properties, mapping outputs, and the properties of run-time objects.
If you want to redeploy an application, you must choose to stop the application. If you do not want to abort running objects, you can rename the application or deploy the application to a different service.
When you update an application and export it to a network file system, you can replace the application archive file or cancel the deployment. If you replace the application archive file, the Developer tool replaces the objects in the application and resets the object properties.