{"id":7224,"date":"2019-08-05T19:22:22","date_gmt":"2019-08-05T13:52:22","guid":{"rendered":"https:\/\/www.argildx.us\/?p=7224"},"modified":"2020-07-02T17:55:33","modified_gmt":"2020-07-02T12:25:33","slug":"on-deploy-scripts-an-acs-aem-commons-utility","status":"publish","type":"post","link":"https:\/\/www.argildx.us\/technology\/on-deploy-scripts-an-acs-aem-commons-utility\/","title":{"rendered":"On-Deploy Scripts \u2013 an ACS AEM Commons Utility"},"content":{"rendered":"

Developers need to perform certain tasks during deployment to AEM server. Component reauthoring is one of the major tasks for a developer making changes to existing components. In this article, we’ll talk about using on-deploy scripts<\/strong> to simplify reauthoring tasks in AEM.<\/p>\n

Problem Statement:<\/u><\/strong><\/p>\n

If the component is to be configured on one or two pages, then reauthoring is simple. However, if the component needs to be configured on many pages, then it’s tedious for an author to reauthor the same component on every page.<\/p>\n

This is one of the scenarios in which we can use on-deploy script. Here is a list of problems we will try to solve.<\/p>\n

What Problems are We Trying to Solve?<\/u><\/strong><\/p>\n