In SCV implementations we often implement component functionality in subflows for reasons such as re-usability, maintainability and performance. We often want to reuse the same functionality in other batch jobs or web services and only want to maintain it in one place. We also may want to use a sub flow so that we can configure distributed processing to help achieve vertical and horizontal scalability across Spectrum servers in a cluster. However, some sub flows require many input and/or output fields specified in the sub flow Input and Output stages for the required functionality. Manually entering 10s or 100s of field names in these stages can be tedious, time consuming and error prone. One solution is to build your Subflow as a Job and then convert into a Subflow in order to inherit the required fields into the Input and Output stages. Attached is a SCV Advanced Topic 'How To' Short Training Video on how to so this.
------------------------------
Jeremy Peters: GISP, CIMP - Master Data Management & Data Quality
Solutions Architect / Principal Consultant/ Distinguished Engineer
Pitney Bowes Customer Information Management and Location Intelligence
350 Jordan Rd | Troy, NY 12180 USA
jeremy.peters@pb.comhttps://www.linkedin.com/in/jeremypeters1/------------------------------