We are moving and on-premise Pega application to the Pega Cloud. One issue we recently encountered was the way the BIX extracts are created. Currently we generate the BIX extracts to a CSV file which is stored on a local NAS. When we use that same process on the Pega Cloud to generate the CSV file it creates that file then ZIP’s it up so only a ZIP file exists with the CSV inside. That breaks the process that was picking up the file to process.
Are there some option flags we can specify on the BIX extract jobs to have them only create the CSV file (not create the ZIP) or if it has to ZIP the file can we have it also leave the CSV file?
There should be a way to tell that process to keep generating the files as it did before.
Sorry, I can’t think of a configuration in Pega Cloud to extract csv files instead of zip files. Can you create a CC ticket to check with the cloud team regarding the feasibility?
Thank you for the response. We currently have our application on premise and the BIX files are created as CSV files. From all the docs I’ve read online so far it mentions that we can have exports in CSV or XML formats. Those were the formats mentioned. It seems that in the Cloud we can still get those formats but at the end they automatically get encapsulated within a ZIP file. For the moment that is an extra step we want to prevent from happening. I can see some instances a ZIP file would be better but in our case for these file it is not.
Ideally there should be a flag to change that behavior as needed. I don’t care what the default it. Just as long as we have a mechanism to override it.
So having a flag to specify if the extracts should be in ZIP file or left alone would preserve the old functionality and give users the ability to specify the output they need per extract jobs.
We have tried all sorts of things but have been unable to extract just the CSV files on the Pega side. Very frustrating that Pega changed to automatically ZIP them without having a flag to skip that extra step and make it act like prior versions. The system that pickups up the files is managed by another team which can’t easily make a change to pickup the ZIP and then unzip to get that original CSV file.
So, we may have to setup our own intermediate service to pickup the file, extract it, and then publish it so the target system can pickup a CSV. This one change on the Pega side to force the BIX extract to be a ZIP file without a way to keep it as it was if desired has wasted a lot of time and may cause us to write a service to undo that change.
I hope that someone on the product side at Pega and the developers and product owners of that BIX extract feature read this and will make an update to specify HOW the extract should be done. I do think having it ZIP the files is a good idea as long as we can still do just the plain CSV too is good. Please add a flag that we can specify to skip the extra ZIP process.’
Maybe if more users complain about it, they will listen and make it more flexible.
For a change like this I think it is best practice to leave the default behavior alone and then add a flag if we wanted it zipped. Then it is a smooth transition to new versions without breaking existing processes. Just changing default behavior is bad but worse when no methos exists to revert to the old way.