{"id":30,"date":"2019-06-19T10:18:49","date_gmt":"2019-06-19T04:48:49","guid":{"rendered":"https:\/\/forsysinc.com\/blog\/?p=30"},"modified":"2024-05-06T10:30:28","modified_gmt":"2024-05-06T05:00:28","slug":"why-template-versioning-is-important-in-apttus-cpq","status":"publish","type":"post","link":"https:\/\/www.forsysinc.com\/blog\/why-template-versioning-is-important-in-apttus-cpq\/","title":{"rendered":"Why Template Versioning is important in Apttus CPQ?"},"content":{"rendered":"\n

While working on proposal\/contract output documents, one of the most common issues faced is to do changes, minor or major, in the data on the template in areas such as merge fields, clauses and static text. And it is a tedious task for a configuration engineer to go back and forth to make manual changes in the template.<\/p>\n\n\n\n

To overcome this problem, we can change the settings in \u201cComply System Properties Details\u201d by enabling document versioning.<\/p>\n\n\n\n

Let us understand how Apttus CPQ Template Versioning works.<\/p>\n\n\n\n

Once the document versioning is enabled under the setup, it will save the new version of the template after every change in it. To illustrate, if any modification takes place in the current template once checked in, it will be saved as V2.0 and the former as V1.0. It is to note that every time the template is checked in the version will be incremented by 1.5.<\/p>\n\n\n\n

Now, all the versions of the master template will be stored under the Versions related list of the master template. The activated version will be clearly mentioned on the template header of the master template record.<\/p>\n\n\n\n

This allows a configuration engineer to compare the different versions of the document and track changes at one go. This feature permits activation of the required version of the template that is appropriate.<\/p>\n\n\n\n

Key Advantages<\/p>\n\n\n\n