Scenario
When the user executes the BIX extract repeatedly by modifying filter criteria, the file name does not change as expected. Ideally, the file names should increment with each run, like xxx_1.zip, xxx_2.zip, xxx_3.zip, and so on. However, the file name stays as xxx_1.zip for all runs. As a result, instead of having multiple files, only a single file is retained across multiple executions.
Explanation
The behavior is as expected.
The BIX extract file name on the Pega cloud is formatted as BIX_<Classname>_<Bixextractrule>_<date>_<sequence>.
The <sequence> part of the file name changes if the BIX extract is run multiple times within a single day. However, if the BIX extract rule is modified (for instance, if the user performs a private edit and check-in), the pzInsKey changes. This change resets the sequence number back to 1.
Environments
The issue was reported in the Pega Cloud environment.
Solution
Run the extract rule without modifying the filter criteria.
In scenarios where a zip file is not generated automatically and the user needs to intervene manually, run the file listener after the BIX job is completed. The file listener is run to ensure all the latest files are picked up. Once the BIX extract rule is changed, its pzinskey is also changed and hence the sequence is reset. In the consecutive run, the sequence starts from 1 again and it does not conflict with any of the existing files.
Best practice
It is advised not to private edit any extract rule in the production environment. If the user needs to make modifications, it should be done in the lower environment first, and then promote these changes to the production (or higher) environment.