0011394: Context properties cannot be used in repository-defined components

Notes
(0037075) mhirt (administrator) 2010-01-29 14:47	Repository Wizards does already have a export as context button. Job templates is a Talend integration Suite feature. Regards,

(0037077) haplm (reporter) 2010-01-29 14:59	This is a misunderstanding. I'm not talking about job templates in Talend. For simplicity, simply forgot that I have ever said the word template ;-). I'm also not talking about "Export as context". What is really important is this sentence: It would be really nice if context properties could be used in metadata components defined in repository (left pane). Thus it wouldn't be necessary to change all such components to built-in (in order to replace hard-coded values with properties) after drag&dropping them from there to the transformation. Let me give you a simple example: I want to reference my working directory by property workingDir. In a component in Job, I can say context.workingDir and it gets correctly translated. Unfortunately I can't say this when I'm defining a component (let's say tFileInputDelimited) in the repository. I have to specify full path the the file - thus this full, absolute path is stored. When you drag&drop such component (where workingDir is already defined), you have still the full path there, so you have to change component type to built-in and then you are allowed to specify name of the property there.

(0037082) mhirt (administrator) 2010-01-29 16:30	I confirm that context were already added to Metadata wizards. Please check this screenshot and read the documentation.

(0037083) haplm (reporter) 2010-01-29 16:49	Again, this is misunderstanding, I want something completely else. I will try to post a screenshot.

(0037093) mhirt (administrator) 2010-01-29 19:37	But did you tried it ?

(0037118) haplm (reporter) 2010-01-30 17:34	Sure I did. It doesn't work - logically. Context is bound to a specific job, which metadata defined in repository are not. Thus it doesn't know what should be the value of the property. Possible solutions is the one that I mentioned - you should create new context, not bound to a specific job, but rather to a project. Variables in this context will be resolvable in repository entries. This context will be also accessible in all the jobs. This is actually a pretty common design - there're usually several contexts, which are somehow merged together at the end (during execution). In Talend, I can imagine product context, project context and job context. That will allow one to use properties everywhere. Right now, you have just job context, which is definitely not enough.

(0038518) tdrees (developer) 2010-02-26 01:31	Your request is completely possible. When you hit "export as context" it creates a context group for all the values of that metadata. Under contexts you can edit this context group to add new contexts. Once you have the metadata set to a context, when you import it each of those values(such as file location) will have context values inside the job. These values reference the project context group.

(0038695) haplm (reporter) 2010-03-01 11:08	You're right, but only partially. I can export the component settings as properties in context, but the problem is that these properties work for the given component only. Imagine you have to create 10 Salesforce schemas, ALL of them using THE SAME property for username. Export as context will create 10 username properties with the same value, so if I want to change the username, I have to edit 10 properties. So, could you please improve TIS/TOS to really allow entering context properties in the wizards? Export as context is a nice thing, but it is not really useful in this context.

Issue History
Date Modified	Username	Field	Change
2010-01-29 09:48	haplm	New Issue
2010-01-29 14:47	mhirt	Note Added: 0037075
2010-01-29 14:47	mhirt	Status	new => closed
2010-01-29 14:47	mhirt	Resolution	open => no change required
2010-01-29 14:59	haplm	Note Added: 0037077
2010-01-29 14:59	haplm	Status	closed => feedback from Talend
2010-01-29 14:59	haplm	Resolution	no change required => reopened
2010-01-29 16:29	mhirt	File Added: 2010-01-29_163103.jpg
2010-01-29 16:30	mhirt	Note Added: 0037082
2010-01-29 16:30	mhirt	Status	feedback from Talend => closed
2010-01-29 16:30	mhirt	Resolution	reopened => no change required
2010-01-29 16:49	haplm	Note Added: 0037083
2010-01-29 16:49	haplm	Status	closed => feedback from Talend
2010-01-29 16:49	haplm	Resolution	no change required => reopened
2010-01-29 16:49	haplm	File Added: Screen shot 2010-01-29 at 16.48.03.png
2010-01-29 19:37	mhirt	Note Added: 0037093
2010-01-29 19:45	mhirt	Status	feedback from Talend => feedback from reporter
2010-01-30 17:34	haplm	Note Added: 0037118
2010-02-26 01:31	tdrees	Note Added: 0038518
2010-02-28 20:51	mhirt	Status	feedback from reporter => closed
2010-02-28 20:51	mhirt	Resolution	reopened => no change required
2010-03-01 11:08	haplm	Note Added: 0038695
2010-03-01 11:08	haplm	Status	closed => feedback from Talend
2010-03-01 11:08	haplm	Resolution	no change required => reopened

Relationships