Thanks again Rob, just needed to pass it around on the main workflow and it worked great.
Hello,
I have an issue where I want to use a portion of the filename used to trigger the workflow in Service Connect as a group #, or at least report it via an email. The issue is, in the workflow, the only place I can see this information is if I look at the "Start" process, but the first transformation schema change doesn't have this information.
Would anyone be able to help me figure out how to get the filename available to map in the workflows?
THanks,
Create a Msgext called ChannelInfo; for a schema, assign the schema from UserSchemas/Standard/ChannelInfo/ChannelInfoFile.xsd Map from the inbound Wfl.User.ChannelInfo.File.Path node to the corresponding node on the outbound schema…
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, January 07, 2015 10:48 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Making file name of Service Connect input available in workflow
Hello,
I have an issue where I want to use a portion of the filename used to trigger the workflow in Service Connect as a group #, or at least report it via an email. The issue is, in the workflow, the only place I can see this information is if I look at the "Start" process, but the first transformation schema change doesn't have this information.
Would anyone be able to help me figure out how to get the filename available to map in the workflows?
THanks,
[Non-text portions of this message have been removed]
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, January 07, 2015 10:48 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Making file name of Service Connect input available in workflow
Hello,
I have an issue where I want to use a portion of the filename used to trigger the workflow in Service Connect as a group #, or at least report it via an email. The issue is, in the workflow, the only place I can see this information is if I look at the "Start" process, but the first transformation schema change doesn't have this information.
Would anyone be able to help me figure out how to get the filename available to map in the workflows?
THanks,
[Non-text portions of this message have been removed]
Thanks rob!
Only part I'm shaky on is if I have to have the subworkflows inherit that extension as well even if I'm only using that data in the main workflow and if I have to map that extension on every transformation I have or just the one.
If it suits you just map it to a process variable after that and pass that down to your subs…
Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-3119
FAX: (715)284-4084
[cid:1.234354861@...]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, January 08, 2015 9:01 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Making file name of Service Connect input available in workflow
Thanks rob!
Only part I'm shaky on is if I have to have the subworkflows inherit that extension as well even if I'm only using that data in the main workflow and if I have to map that extension on every transformation I have or just the one.
[Non-text portions of this message have been removed]
Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-3119
FAX: (715)284-4084
[cid:1.234354861@...]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, January 08, 2015 9:01 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Making file name of Service Connect input available in workflow
Thanks rob!
Only part I'm shaky on is if I have to have the subworkflows inherit that extension as well even if I'm only using that data in the main workflow and if I have to map that extension on every transformation I have or just the one.
[Non-text portions of this message have been removed]