Advanced Training(Academy 2) - Calculate Client Security Hash Walkthrough Light

[luchovelez]

i dont understand this section i dont know where is entry region

● Open the Main workflow and expand the Init state by double clicking it.
o On the Entry region, locate where the KillAllProcesses workflow is invoked.
o Add a new sequence after the Invoke KillAllProcesses activity to read the
input transactions data table.
o Inside this sequence, invoke four of the previously created workflows, as
follows:
System1 Login
System1 Navigate to Work Item
System1 Extract Work Item Data Table
System1 Close

is here?

[ovi]

Hi Luis,

Yes, it’s that one:

And after “Add log fields” you add a new sequence:

[luchovelez]

the other problem i was mapping thr arguments but the variables (in_configFiles) can be accesed and why repeat the process that exist in init all applications?

[ovi]

System1_Login is invoked in two places: in InitAllApplications and in Main at first initialization(your case now).

In InitAllApplications the config is passed as an Argument, in_Config, like it is stated in the Walkthrough.
In Main, you are getting an error if you pass it in the same way, right? That’s because in Main file you get the config from the initialization workflow and ‘memorized’ as a variable, type Dictionary. So please check again the variables in the Main xaml and i’m sure you’ll figure it out.

Sorry for the summarized explanation, but it’s hard to put it in words and still not giving the solution.

[luchovelez]

thanks ovi
but i have another problems import arguments in the get data transaction

in the internal workflow the new argument for inWIlist in not avaliable can you help me?

[Sachin_Tayade]

So do we just invoke the login alone in InitAllApplications ? Not the other workflows to navigate?

[ilemon]

Hi ovi, I’m confused about where “in_Config” comes from…

[luchovelez]

in_config is the dictionary of configuration loaded from the excel