Changes can now be committed in 3 modes:
- Single Commit
- PeopleCode Separate
- Top Level Separate
Single Commit is the default behavior, all changes are committed in a single commit.
PeopleCode Separate will commit all PeopleCode changes in a separate commit, and everything else in another commit.
Top Level Separate will commit each top level folder in the repository as its own commit.
All deleted objects are still committed in a single "Deleted Objects" commit.
To set a commit style there is a new property CommitStyle that goes on the Repository object like so:
{
"Name": "JOB_NAME",
"EnvironmentName": "ENVIRONMENT_NAME",
"ProfileName": "PROFILE_NAME",
"OutputFolder": "PATH_TO_WORKDIR",
"Repository": {
"CommitStyle": "TopLevelSeparate",
"CommitByOprid": false,
"Url": "REMOTE_GIT_URL",
"User": "REMOTE_USER",
"EncryptedPassword": "REMOTE_ENCRYPTED_PASSWORD"
}
},
Valid values for CommitStyle are: SingleCommit, PeopleCodeSeparate, and TopLevelSeparate
Stylesheet Processor now only version controls free form stylesheets.
Previously it would produce 0 byte files for PeopleSoft stylesheets.
To version control PeopleSoft stylesheets, an enhancement to RawDataProcessor has been made which allows specifying ExtraCriteria to RawData entries. ExtraCriteria will be concatenated to the SQL Select statement like this:
SELECT * FROM <Table> (<like statement(s)>) AND <ExtraCriteria>
To version control PeopleSoft Stylesheets, add the following RawData entry into your config.json:
{
"Record": "PSSTYLSHEETDEFN",
"FilterField": "STYLESHEETNAME",
"NamePattern": "{STYLESHEETNAME}.css",
"Folder": "Stylesheets\\PeopleSoft\\",
"IncludeRelated": true,
"RelatedBlacklist": [],
"ExtraCriteria": "STYLESHEETTYPE <> 2"
},