<?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: using different context group for different environments for jobs published to cloud in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/using-different-context-group-for-different-environments-for/m-p/2287133#M60755</link>
    <description>&lt;P&gt;Have a read of my blog series on Context Variable Best Practices. These don't necessarily describe exactly what you want to do, but they will give you some ideas as to what is possible and the advantages and disadvantages you can come across. Start with blog 1 and work your way through. They aren't too long. If you have any questions, I will be happy to answer anything you want &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt; 
&lt;P&gt;&lt;A href="https://www.talend.com/blogger/rhall/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://www.talend.com/blogger/rhall/&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 01 May 2019 11:20:46 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2019-05-01T11:20:46Z</dc:date>
    <item>
      <title>using different context group for different environments for jobs published to cloud</title>
      <link>https://community.qlik.com/t5/Talend-Studio/using-different-context-group-for-different-environments-for/m-p/2287132#M60754</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I haven't tried implementing this but just would like to get an idea of how this can be done.&lt;/P&gt;
&lt;P&gt;So my job have a set of context variables with values assigned for 3 different environments.&lt;/P&gt;
&lt;P&gt;If I have to run the job locally I can choose the environment in the dropdown in run window.&lt;/P&gt;
&lt;P&gt;If this is published to TIC to three different environments say DEV,QA and PROD, then how is the respective context chosen for each environment?&lt;/P&gt;
&lt;P&gt;my second question is&amp;nbsp;&lt;/P&gt;
&lt;P&gt;if I don't want to hardcore these context variable values in the job but want to load it from db, how do I do it for different environments in the TOS and TIS.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;any input is much appreciated.&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 05:57:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/using-different-context-group-for-different-environments-for/m-p/2287132#M60754</guid>
      <dc:creator>nivedhitha</dc:creator>
      <dc:date>2024-11-16T05:57:23Z</dc:date>
    </item>
    <item>
      <title>Re: using different context group for different environments for jobs published to cloud</title>
      <link>https://community.qlik.com/t5/Talend-Studio/using-different-context-group-for-different-environments-for/m-p/2287133#M60755</link>
      <description>&lt;P&gt;Have a read of my blog series on Context Variable Best Practices. These don't necessarily describe exactly what you want to do, but they will give you some ideas as to what is possible and the advantages and disadvantages you can come across. Start with blog 1 and work your way through. They aren't too long. If you have any questions, I will be happy to answer anything you want &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt; 
&lt;P&gt;&lt;A href="https://www.talend.com/blogger/rhall/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://www.talend.com/blogger/rhall/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 May 2019 11:20:46 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/using-different-context-group-for-different-environments-for/m-p/2287133#M60755</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-05-01T11:20:46Z</dc:date>
    </item>
  </channel>
</rss>

