Good day,

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?

GetAllProductDetailsBasedOnOffice

We have created One DAL Workflow. In which we are just inserting data into table with the help of procedure. So Problem is it is not updating 2 column of the table when we called this DAL workflow into our process. However when we execute this DAL workflow independently then it is working fine. 

Let me know if you want to see this workflow. Because I can not attach all the process workflow here. 

Hi team,

Please see the recording below: Call with Hiren and 1 other-20220418_175527-Meeting Recording.mp4

It appears that Warewolf closes when a user tries to generate a test for a "big" workflow. It happened on all three of our machines (Hiren, Vijay and myself).

Attached is my server log for reference: wareWolf-Server.log

Hi team,

Please refer to the screenshot below.

1. Pls look at current DateTime in the far lower right corner of the snip = 2022-04-12 12:31

2. Tool is set to add 10 minutes

3. When executed, in the debug pane, Input date should be 2022-04-12 12:31, however, it is currently giving the Output DateTime's value as the Input DateTime.

Regards,

Wynand

Hi team,

I'd like to suggest a possible enhancement to the suspend tool. The functionality will be very valuable to the Journey team, but I'm sure that other teams may also find it valuable.

We'd like the ability to pass a DateTime field as an input on the Suspend tool. This will give us more control over the date and time that a workflow needs to be executed.

Please refer to the attached snip as an example:

Good day,

Suppose we have a workflow with several test cases. When we make changes to the workflow, due to a change in requirement, all our current test cases will fail, because the pattern of the nodes on the workflow is now different.

Currently, we need to delete all of these test cases and re-create them in order for it to pass. Is it possible that instead of deleting them, we have the functionality to "refresh" them in order to pick up the new nodes / pattern of the nodes and from there we can make the relevant changes if needed?

Regards,

Wy

Hi Team, I have workflow which have "Select and apply" tool then i have "Find Record index" tool. I have created test case for this workflow. I found some error. I am attaching the video for that. 

Test Case Creation in ww-2.6.6.mp4

Also input this workflow is object. I am pasting here for sample input 

{
"JourneyName": "Beneficiary Update Journey",
"ReferenceId": "e9b53199-5d99-ec11-b400-000d3a24d450",
"AdditionalData": [
{
"Key": "MandateId",
"Value": "0becaaca-5d99-ec11-b400-000d3a24d450"
},
{
"Key": "CustomerBenefitId",
"Value": "e1ebaaca-5d99-ec11-b400-000d3a24d450"
},

]
}

In warewolf go to setting -> Logging. Set Elastic Source as logging and save it. Restart Server. I am coming back to check my logging source persist or not. but it again set to default. It should be Elastic search source. Here I am attaching video for better understanding.WWSettingLoggingSource.mp4

Created workflow to use redis cache. to test this workflow I have used jmeter.

In Jmeter, out of 10 requests, 2 requests returning blank value for for Redis key. 

Here I have attached video.

https://theunlimited-my.sharepoint.com/:v:/g/personal/wynand_vermaak_theunlimited_co_za/EYEva2n1gjJDibftfg5AN7sBTbk4GywW6W6w_UAYrC670w