Or leave us a private message
Can we please confirm that the condition "If there is no error" on the Decision tool recognizes and catches all HTTP error codes
We recently ran into a number of issues, and upon investigating we've come to the conclusion that the "If there is no error" condition on the Decision Tool doesn't catch all API HTTP errors - the ones we've experienced a number of times is 400, 404, 500, 503, 504.
I have attached a sample workflow, as an example, indicating the standard way we map our API GET or Post tools. Can you please use a similar setup during testing to confirm if all HTTP errors are recognized and caught?
Split Tool Splits Date values incorrectly
When splitting a string in WW version it converts value into Date time format as shown below and Datetime is incorrect
Word Document reading, Checkbox reading
I would kindly like to know if you have in your "ToolBox" along with your Control flow tools, have the ability to open and read the contents of a word document or bonus points a PDF?
Could you kindly point me to one of your example videos demonstrating that? Our customers are dealerships and have a significant amount of paperwork that needs to be automated.
They primarily rely on checkbox inputs on their paper forms.
There is no tool that does it explicitly. If you are paid subscriber, we could build one for you.
Post Tool - Various issues
I recently started working on a certain part of the Price Increase Journey that worked last year. What has changed since then? Only the Warewolf version. The workflow in question is the GetPdfLinkDetails which contains an API Post to a 3rd party provider - InsideData. Please note that this API response is an escaped json format. For the sake of completeness, I'm using Warewolf 18.104.22.168.
In the latest version of Warewolf, the API doesn't return a response in Warewolf. Whether the default - output to variable or output to object is selected, as per the below screenshots:
However, we are able to get a response in Postman as per the following screenshot:
I then decided to downgrade Warewolf to a version prior to Dev2's Post Tool changes. Once downgraded, upon opening the workflow, I get the following error:
When I tried to delete the former Post Tool, highlighted in red, in order to drag on a new post tool, I get the following error:
This concludes the issues experienced. The following is additional information to help with the troubleshooting:
1. The API in question can be called via a post request to the following URL:
The request body is as follow (Please note - should be in Raw Text format - Not JSON:
"Campaign":"TUG - Price Increase",
"BatchName":"PostMan Test - 2022-08-01",
"CSVData":"TUS000721271;Journey Test;R20.0;R132.0;March 2023;Yes! You get INSTANT CASH BACK on selected groceries like bread, milk, nappies and more!",
Lastly, the workflow in question is:
Warewolf Changes format of dates when receiving from stored procedure
I have a stored procedure that outputs a date format of yyyy-MM-dd, my system regional settings date format is set to yyyy-MM-dd
When Warewolf receives the dates from the output of the stored procedure it uses a different date format not set by me or the database. I have attached sample workflows and the stored procedure to test with
see image :
Advance record set failing with character in data
Warewolf version :- 22.214.171.124
While using Advance recordset , it is giving us error whenever we use Singlequotes for example can't.
Giving error :- SQL logic error.
Convert numeric input into words
Hi Guys, I new please help I am trying to convert numeric values into words.
Password functionality in File Tools break after deployment
We recently encountered an issue where the password functionality on the File tools break during deployment. It seems that the hard-coded password inside the tool gets "distorted" during the deployment process. We found that the only way to get it to work is by making the password field a [[variable]] inside the tool and to pass the actual password value from outside the tool - from Globals or an Assign tool.
Can this please be fixed?
In WW 126.96.36.199 - Facing issue with post tool. if in the response of API, if there is any special character(' + etc) exist then post tool is converting it to '???'.
Servicio de atención al cliente por UserEcho