Release Update 10/18/2024

SDLC

Capability for Improved Import and Export Process in Informatica Pipeline Workflow

A new capability is added for unzipping packages while pushing to Git and zipping them while uploading to Informatica. This helps users in environments where large files or multiple files need to be handled effectively.

Opsera conducts a thorough scan of all folders and subfolders within the package folder during the import process. If any additional zip files are found, they will also be extracted and included. This approach enhances data handling efficiency by ensuring that no pertinent zip files are missed, regardless of their location in the folder hierarchy.

During the export process, if a package.zip file is not provided, the system presumes that an updated package folder exists from a prior import step. In this scenario, the Opsera pipeline wizard will use CSV files located within this package folder to present relevant file information. Furthermore, a recursive check for zip files within the package folder has been implemented. When a zip file is detected that corresponds to its containing folder’s name, the system will remove the old zip file and generate a new one containing the latest content from that folder.

Salesforce

Enhancement in the Handling of File Deletion

The commit process for Opsera’s merge sync tasks has been refined to improve how files are marked for deletion. Previously, if a file that depends on a bundle or custom object was present in the target branch but absent in the source branch, it would be deleted upon commit. This could result in unintended deletions.

To address this issue, we have implemented new logic that distinguishes between files that are genuinely intended for deletion and those that are simply missing from the source branch but not meant for removal. As a result, only files that are explicitly marked for deletion will now be removed.

Additional Capabilities

• A validation has been introduced for the Create Package Pipeline step by implementing a systematic validation process for each XML file before proceeding with further operations. This helps to identify any structural issues within the XML files, early in the pipeline process, allowing teams to receive actionable feedback.

  

The Salesforce Deployment Report generated for external deployments will include the field “Executor for External Deployment”. This field will capture and display the username corresponding to the Salesforce account that executed the deployment.