·Name - The name for the new list. (Mandatory)

·TemplateName - The numeric code of the template to use. (Mandatory)

·Description - A description of the list.

·Title - The title for the new list.

·IsOnQuickLaunch - Indicates if the list should be added to the quick launch.

·HasVersions - Indicates if the list should enable major versions.

·HasMinorVersions - Indicates if the list should enable minor versions.

·RequiresContentApproval - Indicates if the list should require content approval.

·Transformers - The collection of data transformers which the action needs to run. Note that if the passed-in value for this parameter does not include transformers which are considered mandatory, they will be added automatically.

·Quiet - If set, the operation will not report progress to the PowerShell console.

·JobFile - The name of a job file to use for logging. If the file does not exist it will be created.

·Source - The source node for the actions.

·Target - The target node for the actions.

·JobDatabase - The connection string of a jobs database to use for logging. If the connection string is invalid, an exception is thrown. If both 'JobFile' and 'JobDatabase' parameters are specified, then the 'JobDatabase' parameter will take precedence and the job will only be written to the job database.

·URL - The URL name for the new site. If not specified, it will be automatically generated from the given name.

·Name - The name for the new site. (Mandatory)

·TemplateName - The name of the template to use, either in [Name]#[Config] form or by the name of the STP file. (Mandatory)

·Transformers - The collection of data transformers which the action needs to run. Note that if the passed-in value for this parameter does not include transformers which are considered mandatory, they will be added automatically.

·Quiet - If set, the operation will not report progress to the PowerShell console.

·JobFile - The name of a job file to use for logging. If the file does not exist it will be created.

·Source - The source node for the actions.

·Target - The target node for the actions.

·JobDatabase - The connection string of a jobs database to use for logging. If the connection string is invalid, an exception is thrown. If both 'JobFile' and 'JobDatabase' parameters are specified, then the 'JobDatabase' parameter will take precedence and the job will only be written to the job database.

·ClearGuidMappings - Indicates that global GUID mappings should be cleared.

·ClearURLMappings - Indicates that global URL mappings should be cleared.

·ClearUserMappings - Indicates that global user mappings should be cleared.

·ClearDomainMappingss - Indicates that global domain mappings should be cleared.

·CompareFolders - Indicates whether or not to compare folders.

·CompareItems - Indicates whether or not to compare items.

·CompareVersions - Indicates whether or not to compare item versions.

·CompareMetadata - Indicates whether or not to compare object metadata.

·VerboseLog - Indicates whether or not to compare object metadata.

·HaltIfDifferent - Indicates whether or not to halt the comparison if a difference is encountered.

·FilterListsAndFolders - Indicates whether or not to filter lists and folders.

·ListAndFolderFilterExpression - The filter expression applied to lists and folders.

·FilterItemsAndVersions - Indicates whether or not to filter list items and their versions.

·ItemAndVersionFilterExpression - The filter expression applied to list items and versions.

·Transformers - The collection of data transformers which the action needs to run. Note that if the passed-in value for this parameter does not include transformers which are considered mandatory, they will be added automatically.

·Quiet - If set, the operation will not report progress to the PowerShell console.

·JobFile - The name of a job file to use for logging. If the file does not exist it will be created.

·Source - The source node for the actions.

·Target - The target node for the actions.

·JobDatabase - The connection string of a jobs database to use for logging. If the connection string is invalid, an exception is thrown. If both 'JobFile' and 'JobDatabase' parameters are specified, then the 'JobDatabase' parameter will take precedence and the job will only be written to the job database.