Morning everyone,

Context: Business is looking at saving messaging cost, by sending an email instead of an sms - as it works out cheaper. In the business we do however face a concern with regards to the correctness of the email addresses captured by agents. We are now looking at reporting on incorrectly captured contact details in an attempt to increase the success rates of contacting our customers.  

Approach: We looked at using the decision tool's Is Regex functionality, with regular expression /^\w+([\.-]?\w+)*@\w+([\.-]?\w+)*(\.\w{2,3})+$/ to validate an email.

Problem: We found that the functionality is not working as expected - when entering a valid email address the validation fails instead of passing.

I have attached a sample workflow to demonstrate the concern: EmailValidation.bite 

When the advanced recordset tries to process a recordset that does not exist it does not throw an error but instead makes the rest of the workflow unresponsive.

Hello Team,

The Get Web Method Tool does not provide / map an output when using "Generate Outputs" on Warewolf 2.8.4.0, however execution level works fine for tools that were mapped with certain previous versions of Warewolf.

Example of Mapped output on Warewolf 2.8.3.19:

Example on Warewolf 2.8.4.0:

Herewith a recording with Yogesh regarding the topic - Catch-up; Masi, Wynand and Igor-20230720_100030-Meeting Recording.mp4

Problem:
I checked date difference and date format in Utility - Date and Time Difference example of Warewolf where I found it calculated wrong difference and also date format was not correct.

Warewolf Version I am using is 2.8.1.3

Current Date: 3rd July 2023
Date Format passed in example is: yyyy/mm/dd 12h:min:ss am/pm
New date should be like 2023/07/03 but in example it was resulted 2023/03/07.

Date Difference:

Warewolf version I am using is 2.8.1.3.

Millisecond part is being eliminated while getting records from database. While in my case millisecond is required. 

Hi team,

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?

Regards,

Wynand GetCustomerDetails.bite

When splitting a string in WW version it converts value into Date time format as shown below and Datetime is incorrect

Version: 2.8.3.7

"TU015725753-1,1649998986,Savings,470010,A ROUX,2023-05-05,230.000,202305,8,TU015725753-1"

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.

Hello,

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 2.8.1.63.

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: 
https://generic.insidedata.co.za/ID.Generic.API.TheUnlimited/IDServiceRest.svc/CreateDistributionWithShortener.

The request body is as follow (Please note - should be in Raw Text format - Not JSON:

{
"PassPhrase":"B7CC5331-12A8-46AA-A5B0-D6AB6D4AFC93",
"BusinessID":"TheUnlimited",
"Campaign":"TUG - Price Increase",
"BatchName":"PostMan Test - 2022-08-01",
"DistributionMethod":"SMS",
"DistributionTemplate": "TheUnlimitedInsurance",
"CompositionTemplate":"PriceIncrease",
"TransformData":true,
"Approval":false,
"ArchiveOnly": true,
"LoadData":{
"SourceDataType":"CSV",
"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!",
"Customer":{
"Reference":"TUS000721271-2",
"Name":"Journey Test",
"Surname":"",
"Initials":"",
"Title":"",
"Language":0,
"EmailAddress":"wvermaak86@gmail.com",
"NumberMobile": "0726105303"
},
"Reference":{
"RefAmount1":"20.0",
"RefAmount2":"132.0",
"RefDate1":"March 2023",
"Version":"1"
},
"Distribution":{
"SendSMS":true
},
"ExternalID":1234567890123,
"IsValid":true
}
}

Lastly, the workflow in question is:

GetPDFLinkDetails.bite

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 : 

 Resources.zip