Version 1.158

Features The Slice JSON rule already had the ability to remove a certain part from the slice rule in order to make sure the result fits in raw data and the heap size limit is not overused. Now the possibility is added to keep the first element in case the Remove JSONPath points to an array. Sometimes parent information is found in each of the child elements and then it’s useful to keep one of these child elements in the raw data result. Bread now has fields Transform Batch Size and Load Batch Size. These drive how the bread is executed, not the same fields on Recipe Version. Fields on Recipe Version determine the initial value of the Bread. Connected Orgs Added the ability to define multiple views for the Connected Orgs page. Views are configured in field Corrected Org Views of custom metadata type Settings. A view consists of the following attributes: Name Recipe To Include: The names of recipes to include breads with issues for. % Can be used as a wildcard. Recipe To Exclude: The names of recipes to exclude breads with issues for. % Can be used as a wildcard. Hide if there is no breads. Do not show the org card if there are no breads with issues. 16-1-2025 | 159 orgs | 641 unit tests

Version 1.155

Features Introduced immediate transform and load execution modes. If selected, recipes are executed directly in the context of the trigger (usually through Bulk API) that creates or updates the slices. This execution mode should only be used if the Asynchronous Apex Execution Limit (250,000 executions per 24-hour period) is a challenge. Added ability to add custom soql to query rules. Sliced Query Into Records and Slice Query Into Buckets already had this ability. Only recipe parameter merge fields can be included. Added section Metadata Function to the formula rule and added functions OBJECTHASFIELD (already existed, but hidden) and HASPICKVAL. Small tweak to which breads are shown in the “in progress breads” table: A cancelled Bread is immediately not shown anymore. Before it would still be shown for 5 minutes. 12-1-2025 | 157 orgs | 632 unit tests

Version 1.154

Features Introduced Connected Systems (hidden, not included in app). One type supported: SFTP. Introduced Recipe Jobs (hidden, not included in app). Introduced Slice Archive Delay. Bug Fixes Solved bug with discard rules not drag-and-droppable between transform and load phases. Solved bug with Load Batch Size not included when exporting a recipe. Solved bug in Excel slicer with sheet name not being url encoded when calling AWS. This gives issues when for example the sheet name contains a space. 5-1-2025 | 152 orgs | 608 unit tests

Version 1.149

Features Optimized DeleteSlicesBatch such that one batch can handle multiple breads, not just one. The old solution sometimes led to too many batches on the flex queue (limit: 100). 3-12-2024 | 149 orgs | 597 unit tests

Version 1.148

Bug Fixes Solved bug with query rule output validation on no query result is set to Fail. For situations requiring more than one query to handle the rule, the query rule could say that there was no query result, whereas there was one. In unit tests added isFilterable checks before executing assertions including queries like “select Id from Contact where Email = :email”. These queries were preventing package upgrades on some orgs, most likely because of Salesforce Shield. 1-12-2024 | 140 orgs | 595 unit tests

Version 1.147

Features Connected org now also displays package version indication. The highest version of a package in the namespace “thn” is currently displayed. On the next customer, this namespace will become configurable. Removed icon in front of output validations No Query Result. Bug Fixes Fixed recipe builder query rule editor bug with input validation rule selection not working if query contains fixed value query criterium or contains a virtual field multiple times in the query criteria. Added protection for a load plan which is larger that fits into the Slice Load Plan field. 24-11-2024 | 147 orgs | 594 unit tests

Version 1.146

Features Excel wizard now supports selecting a sheet name. Process Slices API: Introduced an api to process slice raw data using Extract, Load and Transform of a recipe. 10-11-2024 | 143 orgs | 591 unit tests

Version 1.145

Bug Fixes Solved timezone bug in Archiver. 5-11-2024 | 143 orgs | 583 unit tests

Version 1.144

Features Add limit Daily Api Requests limit to the connected org functionality. Made the following changes to the Recipe Builder settings modal: Renamed Non-Load Execution mode / Batch Size to Transform Execution Mode / Batch Size. Using transform here is more intuitive. Transform Execution Mode / Batch Size used to be an advanced feature. This has been removed for the following reasons: (1)More often than expected it needs to be changed, so it’s not an advanced feature. (2) It made the order of the settings: first load, then transform, which was confusing. 3-11-2024 | 143 orgs | 583 unit tests

Version 1.142

Features Added a new AWS region: Israel (Tel Aviv). Both in the package and on AWS. Improved performance of the Recipes page by moving generating the content for exported recipes – JSON and Apex – to after selecting one of the two export options. If the name of recipe contains “Health” and “Check”, the following icon is used: Connected Orgs Show the 3 limits most relevant to Sliced Bread: data storage, file storage and daily async apex executions. Show not-failed breads and breads without failed slices only after 4 hours. Purpose of this is to make the connected orgs overview a clean overview of issues, not in-progress items. Always show the incidents icon left-top of the component if there is one or more breads to show. Before it would also show the ready to load icon in some situations. Removed the limit of just showing 5 breads. Now it will show all breads with an issue. Bug Fixes Previous release contained this change: Store transform and load rule json in a Recipe Version record as non-pretty if needed to better fit in a Long Text Area field (131,072). Now the same solution has been applied to importing a recipe. Before it was always pretty, now it’s not-pretty if it’s too large. 27-10-2024 | 138 orgs | 583 unit tests