Customize File Type Detection

When you perform populate operation from SCM, files are organized in various types based path, file extension etc. You can customize this behavior by updating project properties in many cases and further customizations can be done by using groovy script a.k.a Match Script override.

Match script override is done for specific project type. For example, you can customize how FlexDeploy determines type for EBS project files as shown below.

Access object type details screen by using menu option - Administration - Customize - Object Types.

Search for specific Project Type, in this case EBS. Click on project type name in Project Type column.

Update Match Script (groovy), then click Save.

Here is an example of matching files from /install/sql as Concurrent Program SQL and /install/bin as Script with Execution.

if (!binding.variables.containsKey('FDEBS_APPLICATION_SHORT_NAME'))
{
    throw new Exception('Application Short Name not found. Please Configure FDEBS_APPLICATION_SHORT_NAME property');
}
FILE_CONTENT_NEEDED=Boolean.TRUE;
CP_SQL_DIR='install/sql';
if (FILE_PATH_PREFIX.contains(CP_SQL_DIR) && FILE_EXTENSION.toUpperCase().equals('SQL'))
{
  return 'CP_SQL';
}
SCRIPT_DIR='install/bin';
if (FILE_PATH_PREFIX.contains(SCRIPT_DIR))
{
  return 'SCRIPT_EXECUTION';
}
return null;

Now let's talk about how you write such groovy script. You have access to various details about file and project properties. You can make decision based on available variables about file, then return appropriate Object Type Code, or you can return null in which case FlexDeploy will make determination based on default logic as documented in EBS Object Types Reference.

Match Script Variables

Return FILE_CONTENT_NEEDED as Boolean.TRUE if file content is necessary to derive attribute defaults or return Boolean.FALSE.

Also, return one of the following object type when you can derive type, otherwise return null and FlexDeploy will determine object type in the usual manner.]

EBS Object Type Codes