Skip to main content

3 posts tagged with "error handler"

View All Tags

🚧 Improvement

  • HTML2PDF app configuration has been simplified to use less required parameters having default values instead.
  • Improved the loading time of some internal queries

🐞 Bug fix

  • Fixed an issue that was causing a flow (from a "run a flow" app) to trigger its parent's error handler flow.
  • Fixed the search by flow name in the reports section.

🚧 Improvement

  • Improved the loading of the speed of the Environment detail when clicking in the left menu.
  • MACRO preg_replace() now accepts multiline text.
  • Show a new object in the report to represent that a user restarted a data record manually.

🐞 Bug fix

  • When editing a flow, if the user navigates to another page, only after having modified the flow, a warning appears to remind that you will lose the changes.

🚀 New feature

  • Update Environment code: Now, it's possible to start or schedule an update in your environments when a new version of Flowize comes out. If the latest version is a major update, you won't be able to update the projects until you apply the update.
  • Error handling per App: Now, it's possible to configure per App in the flow and what to do when an error happens. You can configure the number of retries and also if you want to stop or continue the flow if that specific error occurs.
  • App GatewayAPI: It uses the service GatewayAPI to send SMS. GatewayAPI is an API service providing out- and ingoing SMS message services at competitive prices.
  • App Otys: Upload files to Otys service.

🚧 Improvement

  • Now we can delete a flow that has status running. We are warning the user if it's being used in other flows.
  • Added Variables button in Sync URL Headers.
  • Added option to include white spaces or other characters on the left side of a decision parameter for dynamic decision tool in the flow.