<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Variables type use case in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Variables-type-use-case/m-p/2362357#M126515</link>
    <description>not in Your order 
&lt;BR /&gt; 
&lt;B&gt;Environment&lt;/B&gt; - it is OS level variables, such as ORA_HOME, JAVA_HOME and etc. You can for example define OS variable - RUN_ENV - dev or qual or prod, than Your Talend Job will check this variable and use in Job logic 
&lt;BR /&gt; 
&lt;B&gt;Global variable&lt;/B&gt; - most often used way for: 
&lt;BR /&gt;- store value between component 
&lt;BR /&gt;- save value and etc 
&lt;BR /&gt; 
&lt;B&gt;Context variables&lt;/B&gt; - some time could be used as global, but main goal - define context group (like - dev, prod, qual) and anywhere where it possible - use context variable for PATH, name, connection information and etc 
&lt;BR /&gt;then changing only 1 parameter You can run Job with different set of all parameters&amp;nbsp; 
&lt;BR /&gt;also You can store context variables values in csv file and change them for compiled Jobs&amp;nbsp;</description>
    <pubDate>Sat, 15 Oct 2016 10:25:05 GMT</pubDate>
    <dc:creator>vapukov</dc:creator>
    <dc:date>2016-10-15T10:25:05Z</dc:date>
    <item>
      <title>Variables type use case</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Variables-type-use-case/m-p/2362356#M126514</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;I can see at least three kind of variables (There might be even more ?):&lt;BR /&gt;-Context variables&lt;BR /&gt;-Environnement variables (With component tSetEnv)&lt;BR /&gt;-Global variables (With component tSetGlobalVar)&lt;BR /&gt;&lt;BR /&gt;Could someone help me to understand use cases of these three kind of variables ?&amp;nbsp;&lt;BR /&gt;And especially when context variables cannot be used and one of two others has to be used ?&lt;BR /&gt;Eric&lt;/P&gt;</description>
      <pubDate>Sat, 15 Oct 2016 08:46:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Variables-type-use-case/m-p/2362356#M126514</guid>
      <dc:creator>_AnonymousUser</dc:creator>
      <dc:date>2016-10-15T08:46:13Z</dc:date>
    </item>
    <item>
      <title>Re: Variables type use case</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Variables-type-use-case/m-p/2362357#M126515</link>
      <description>not in Your order 
&lt;BR /&gt; 
&lt;B&gt;Environment&lt;/B&gt; - it is OS level variables, such as ORA_HOME, JAVA_HOME and etc. You can for example define OS variable - RUN_ENV - dev or qual or prod, than Your Talend Job will check this variable and use in Job logic 
&lt;BR /&gt; 
&lt;B&gt;Global variable&lt;/B&gt; - most often used way for: 
&lt;BR /&gt;- store value between component 
&lt;BR /&gt;- save value and etc 
&lt;BR /&gt; 
&lt;B&gt;Context variables&lt;/B&gt; - some time could be used as global, but main goal - define context group (like - dev, prod, qual) and anywhere where it possible - use context variable for PATH, name, connection information and etc 
&lt;BR /&gt;then changing only 1 parameter You can run Job with different set of all parameters&amp;nbsp; 
&lt;BR /&gt;also You can store context variables values in csv file and change them for compiled Jobs&amp;nbsp;</description>
      <pubDate>Sat, 15 Oct 2016 10:25:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Variables-type-use-case/m-p/2362357#M126515</guid>
      <dc:creator>vapukov</dc:creator>
      <dc:date>2016-10-15T10:25:05Z</dc:date>
    </item>
  </channel>
</rss>

