Methods for identifying Foundation data customizations

Use these tips to identify your customizations:

• Documentation—If your customizations are documented, you can use this information to create a list of the workflow, fields, and forms that have been added or changed within your application. 
• Naming conventions—Application developers sometimes use a naming convention that identifies customized workflow. The workflow is then placed within a namespace reserved for this purpose. For example, if the HPD:HPD-GetPerson active link is modified, it could have been copied to HPD:CUS-GetPerson, by using CUS in the name to indicate that it is customized workflow.

After you identify customizations, you must determine their impact on the data load functionality. The types of customizations to BMC Helix ITSM that can impact the functionality of the Data Management tool are as follows:

• Custom fields with Required entry mode—Whether these fields are new or are modified on existing BMC Helix ITSM forms, they impact the data load. You must make sure that these fields are populated with data. Otherwise, the data load fails. 
• Fields with Optional entry mode—If these fields have custom workflow to enforce data entry when records are created or updated, they impact the data load. If required, duplicate the custom workflow on the data load staging forms to enforce the same constraints. To determine the appropriate staging form, see Spreadsheets provided and target form mapping.
• Custom workflow—In most cases, workflow customizations do not impact the Data Management tool. When data is loaded by the tool, all BMC Remedy ITSM workflow on forms targeted for the load are bypassed, with the exception of workflow firing from the tool itself. This workflow bypass on target forms is performed by using filter workflow with goto actions. These filters fire on execution order 0 based on keywords that are received from the data load staging forms.
  Some custom workflow, however, does impact the data load function. For example, the workflow might be triggered on creation of the record on the form to create other child or dependent records elsewhere. 
• New customized forms—In most cases, new forms do not impact the data load function. If dependencies are created between a new customized form and data load target forms, however, you must perform additional evaluation.