• Assets changes — assets include the following: Type Properties, SSH, and Templates.

◦ Types—types include either a set of rules (such as filtering rules, links, search results, and so forth) or a setting for a source or data type such as PARTSLIST IS PDFM. Change in type definitions require re-indexing of the data.

◦ SSH—the stylesheet usually used for data transformation after data load. Changes in SSH require updating the SSH, but do not require re-indexing.

◦ Templates—templates define the structure of specific types of sources in the system (such as PART, PARTSLIST, PI, and so forth). When a template is changed, that means the data structure is changed. Any change in a template requires re-TAL.

◦ No changes in Assets means that no re-indexing is required.

• Core software changes —

◦ Any change in a template under <InService.Home>InS_SW\Config\System\Config\Core\Version2\Templates\NewPublicationXSL requires deleting and recreating the segments and reloading the data.

◦ Any change in other templates under <Ins.Config.Home>\System\Config\Core\Version2\Templates requires re-indexing of the data.

◦ A significant software change might require re-indexing or re-creating the segments. Any changes in the Core data structure might also require those steps. Those cases are decided based on the type of change.