0

Advanced Recordset functions not working

bbuchan 1 day ago in Studio / Variables 0

Given I have an Advanced Recordset tool on the design surfcae

When the SQL is "SELECT SUM(sales) AS Count FROM Table"

Then my variable list has a Field called SUM and a field called Count added to the Table recordset

Given I click Generate Outputs

Then nothing happens and not outputs are generated.

Given I then amend the SQL to "SELECT sales FROM Table"

When I click Generate Outputs

Then Still nothing happens

Given I create a new Advanced Recordset tool on the design surface

When I copy the SQL statement to the new tool

and When I click Generate Outputs

Then Outputs are generated

+1
Under review

Facing Issue while Inserting value into Database

Anonymous 5 months ago in Studio / Variables updated by Ashley Lewis 4 months ago 1

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. 

0
Under review

Post Tool is not recognising the variables in the body when generating outputs

Wynand Vermaak 1 year ago in Studio / Variables updated by Yogesh Rajpurohit 1 year ago 1

Hi guys,

I worked with the Post Tool this morning and experienced the following bug. When declaring variables in the body of the Post Tool, it doesn't automatically populate in the Variables Toolbar. Also, the output variables from the Post Tool also doesn't populate the Variables Toolbar. Please refer to the following snip:

I proceeded by entering the variables manually, but as you can see from the following snip, it appears that the Variables Toolbar is not recognizing them.

Please feel free to contact me if additional info is needed.

Regards,


W

studio variables workflow
0
Under review

Email Address format change on the Input "Assign Object" tool

Hiren Khatri 1 year ago in Studio / Variables updated by Gandalf 1 year ago 1

In the "Assign Object" input variable, If we pass the correct email address the first time then it will be fine but after 2nd time if we try with the same payload as input then their email address format change from "hiren@gmail.com" to "hirengmail.com".

Replicate on version "Warewolf-2.6.1" and "Warewolf-2.6.2.0".

Input Payload:

"{
"BusinessEvent": {
"RequestID": "40CA026F-8A5A-4695-AEEF-A5FEDF37B371",
"ReferenceId": "9307deed-273c-44d2-8124-2b970223c175",
"Customer": {
"Mandate": [
{
"MandateShortId": "TU000000150",
"MandateId": "e52805a2-2da2-440f-8d59-7d46683b6834"
}
],
"PlanId": "74",
"EmailAddress": "hiren@gmail.com",
"FirstName": "Sune",
"DisplayNumber": "TU00000",
"MobilePhone": "27832640"
},
"ExternalSourceType": "CRM"
}
}"


For reference, attach snaps and sample workflow.


Sample Workflow


0

Bug: Can’t override the object in child workflow.

Anonymous 1 year ago in Studio / Variables 0

We Found Issue while override the object in sub work flow. It is also giving duplicate errors as per the below Screenshot. Please find below workflow for more detail.Main Workflow
ChildWorkflow

0
Under review

Connector MS SQL Server - sp output variable

zsery 4 years ago in Studio / Variables updated by Elmo 4 years ago 3

Variable is declared (stored procedure) as output only. Studio needs declare as input too, why?
Response exists but MS SQL connector does not retrieve value in this variable (response  empty), why?

Generate mapping functionality generate only recordset mapping, it is correct< Is not missing mapping for output variable from stored procedure?

0

test

Anonymous 5 years ago in Studio / Variables 0

test

deploy
0
Answered

SignalR Connector

Anonymous 7 years ago in Studio / Variables updated by Gandalf 6 years ago 6

Hi!

I have a SignalR hub with some data that I want to set into warewolf variables and then use this variable value either to store or call other services/web api as a trigger.
Do I need to create a connector to accomplish this behavior?

In order to monitor this variable value, do I need to put this variable within a loop?


Thanks.

tool variables
Answer
Gandalf 6 years ago

Hi victor

Make the call to the URL of the service (Look above the workflow for this). Something like this:



In this example I have a folder called Examples with a workflow called Handler in it which is the workflow you can see on the design surface. In the Variables list on the right, I have set the two variables I want to use as Input so they can be accepted by the workflow. After that, I just use them, as in the decision.

Hope that helps.

+2
Not a bug

Recursive Evaluation

Anonymous 7 years ago in Studio / Variables updated by Gandalf 6 years ago 5
After reading about how the Datalist caters to recursive evaluation I thought this was interesting and wanted to try it out.
From the technical documentation page:
"i.e. [[hello[[world]]]] would be recursively evaluated as [[hellobob]] where [[world]] had the value of “bob” and then [[hellobob]] as “my name is bob” where [[hellobob]] had the value “my name is bob” stored in it.

I decided to test this out myself. I created a variable [[hellobob]] and assigned the string "my name is bob" Then I created a variable [[world]] and assigned "bob". Finally I created a variable [[result]] and assigned [[hello[[world]]]]. To my disappointment I received a parse error.

I went back and added the variable [[hello]] and assigned "hello"
And then changed my assignment of [[result]] to [[[[hello]][[world]]]]
This produced the expected result. In the debug window it read my assignment as Variable [[result]] = New Value [[hellobob]] with the string "my name is bob" as its value.

I don't know if this is technically a bug since it did behave in a recursive manner when I tried the second time, but perhaps the documentation is wrong. When I set [[result]] to [[hello [[world]]]] It returned [[hello bob]] an unassigned variable. But with no space there, [[hello[[world]]]] results in a parse error.
+1
Answered

As part of our architecture framework for WareWolf development, I need to come up with a set of naming conventions for variables(inputs or outputs) in WareWolf workflows.

Logan Govender 8 years ago in Studio / Variables updated by Gandalf 8 years ago 2
Can you suggest a naming convention for WareWolf workflow variables(below are my thoughts):



-For input variables (eg . WorkflowName_In_Variablename)

-For output variables (eg . WorkflowName_Out_Variablename)

-For variables from other workflows that kick off other work flows (eg . WorkflowNameParent_WorkflowName_In_Variablename)