0
Fixed

DateTime Tool - Incorrect InputDate given in Debug

Wynand Vermaak 3 years ago in Studio / Output updated by anonymous 3 years ago 1

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.

Image 1026

Regards,

Wynand

debug studio tool workflow
0
Completed

Enhancement - Suspend Tool

Wynand Vermaak 3 years ago in Studio / Toolbox updated 3 years ago 2

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:

Image 1024

studio tool workflow
Answer
Gandalf 3 years ago

This functionality already exists. The default option on the suspend tool: "Suspend Untill:" takes a datetime input.

+3
Under review

Enhancement - Warewolf Test Framework

Wynand Vermaak 3 years ago in Studio updated by Gandalf 3 years ago 8

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

0
Fixed

UAT-Test case issue in warewolf version 2.6.6. Same problem I face in new version too.

maya khambhayata 3 years ago in Studio updated by anonymous 3 years ago 5

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"
},

]
}

0
Fixed

Warewolf 2.7.2.0 - Logging Source setting issue.

maya khambhayata 3 years ago in Studio updated by anonymous 3 years ago 1

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

0
Fixed

Redis cache - from jmeter out of 10 requests, 2 requests returning blank value for redis key

maya khambhayata 3 years ago in Studio updated by anonymous 3 years ago 4

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

studio
0
Not a bug

Facing Service Unavailable issue with Warewolf version 2.5.2.88

Anonymous 3 years ago updated by Siphamandla Dube 3 years ago 2

I have already tried below Scenarios

Scenario:1

1) Uninstall warewolf existing version

2) Remove Warewolf files from (ProgramData, ProgramFiles (x86), App Data)

3) Restart the system

4) install the warewolf version 2.5.2.88


Scenario:2

1) Install .Net Framework 4.8 

2) Uninstall warewolf existing version

3) Remove Warewolf files from (ProgramData, ProgramFiles (x86), App Data)

4) Restart the system

5) install the warewolf version 2.5.2.88


Scenario:3

1) Update my windows

2) Uninstall warewolf existing version

3) Remove Warewolf files from (ProgramData, ProgramFiles (x86), App Data)

4) Restart the system

5) install the warewolf version 2.5.2.88


Scenario:4

1) Perform the Repair for the warewolf version 2.5.2.88


Scenario:5

1) Restart the Warewolf Service

Scenario:6

1) Install the new version of Warewolf 2.7.1 & Still facing the same issue 


Please find attachment here for server logs. 

ServerLogs

0
Not a bug

For each loop issue: All Recordset index values not passing into child workflow

Ashley Lewis 3 years ago in Server / Execution updated by Siphamandla Dube 3 years ago 2

Hi,

I have noticed that All the values of recordset are not passing into child workflow for each loop. I have checked this same behavior into the Select & Apply tool and it's working fine.

Please check the sample attached workflows & issue into screenshot.

forloop_recordset_all_values_not_pass_issue....png
ForLoopIssue-MainWorkflow (1).bite
ForLoopIssue-ChildWorkflow (1).bite

Gandalf 5 months ago

It looks like the For Each is getting confused with 2 different recordset inputs: User(*) and Benefit(*)

Gandalf 5 months ago

Change For Each to use No. of Executes = 3 and see different result. This is from the tool handeling the replacement of * differently and incorectly.

Yogesh Rajpurohit yesterday at 9:13 a.m.

We have checked and found that the sequence of BenifitID in User Payload is incorrect so we changed the sequence and checked the result. Output is coming properly.

Attached are the Edited Workflows.

ForLoopIssue-ChildWorkflow (2).bite
ForLoopIssue-MainWorkflow (2).bite

execution server variables
0

For Each CSV not working

Gandalf 3 years ago 0

CSV not working inside a workflow.
Output of workflow should be :For Each with CSV not working.bite
X

Q

X

Q

X

0
Fixed

WW 2.6.10.0 - Suspend tool - Error in resume - Execution return TransactionAbortedException: re-queue with caution

Anonymous 3 years ago updated by anonymous 3 years ago 2

in WW 2.6.10.0, Created sample workflow to test suspend tool and suspended for 10/20 seconds but at the time of resume it is in processing mode for longer period of time and then it is failing in hangfire database. 

below information I got from database.

suspend2.bite


I have video for this bug but not able to attached here. Let me know if you want. (Maya)

Reason
==========================
Execution return TransactionAbortedException: re-queue with caution.


Data:
==============
{"FailedAt":"2021-12-23T09:05:58.6891892Z","ExceptionType":"System.Exception","ExceptionMessage":"The transaction has aborted.","ExceptionDetails":"System.Exception: The transaction has aborted."}


Arguments:
=======================
["{\"resourceID\":{\"m_MaxCapacity\":2147483647,\"Capacity\":36,\"m_StringValue\":\"e5c4d591-dbaa-4b70-b152-86d2b9c06a7a\",\"m_currentThread\":0},\"environment\":{\"m_MaxCapacity\":2147483647,\"Capacity\":122,\"m_StringValue\":\"{\\\"Environment\\\":{\\\"scalars\\\":{\\\"input1\\\":\\\"var1\\\",\\\"input2\\\":\\\"va2\\\"},\\\"record_sets\\\":{},\\\"json_objects\\\":{}},\\\"Errors\\\":[],\\\"AllErrors\\\":[]}\",\"m_currentThread\":0},\"startActivityId\":{\"m_MaxCapacity\":2147483647,\"Capacity\":36,\"m_StringValue\":\"6f2c5415-aaa2-4912-806c-077cfe68ca53\",\"m_currentThread\":0},\"versionNumber\":{\"m_MaxCapacity\":2147483647,\"Capacity\":16,\"m_StringValue\":\"0\",\"m_currentThread\":0},\"currentuserprincipal\":{\"m_MaxCapacity\":2147483647,\"Capacity\":20,\"m_StringValue\":\"CYGNET\\\\mmkhambhayata\",\"m_currentThread\":0}}",null]