Feedback 
program
Report an issue
Updates
Visual Flow team added some new features.
New Features:
- now you can create your own data frame on the Read stage with a new Dataframe storage,
- the ability to upload/download data from/to a local file has been implemented into the Read/Write stages,
- new storage Click House has been added to the list of available storages on the Read/Write stages,
- now you can tag jobs while creating them. So you can easily find your jobs by these tags afterwards.
Looking forward for a new release. Stay tuned!
Visual Flow team fixed bugs and discrepancies.
Fixes:
- STDOUT and Local File has been removed from the connections list.
- Resolved the Elasticsearch connection issue. The cert data field is now enabled when SSL is true.
- The status of a draft job on Job History has been corrected.
- On Settings → Connections a new connection is now not saved unless all required parameters are entered.
Looking forward for a new release. Stay tuned!
Visual Flow team updated functionality and made UX/UI improvements
New Features:
- now you can create your own data frame on the Read stage with a new Dataframe storage,
- the ability to upload/download data from/to a local file has been implemented into the Read/Write stages,
- new storage Click House has been added to the list of available storages on the Read/Write stages,
- now you can tag jobs while creating them. So you can easily find your jobs by these tags afterwards.
Looking forward for a new release. Stay tuned!
Did you find a bug?
- Make sure the bug has not already been reported by searching on GitHub under Issues.
- If you’re unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring. For more detailed information on submitting a bug report and creating an issue, visit our reporting guidelines.
Did you write a patch that fixes a bug?
- Open a new GitHub pull request with the patch. The development team will be reviewing pull requests on a regular basis and according to the team’s priorities and bandwidth.
- Make sure the PR description clearly describes the problem and solution. Include the relevant issue number, if applicable.
Did you fix whitespace, format code, or make a purely cosmetic patch?
Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of Visual Flow will not be accepted.
Do you intend to add a new feature or change an existing one?
- Contact us via email: info@visual-flow.com
- Do not open an issue on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for bug reports and fixes.
Do you have questions about the source code?
Get in touch
