It is very common in most integration flow design we need to refer to configuration files for mapping information, file path info, lookup values etc. As of today we keep these configuration files in SLDB or SFTP server and load them to pipeline using FileReader snap. This is not very ideal, reading the configuration file is not part of my integration flow design but the configuration is needed for the integration flow, loading of configuration should be outside of my flow design. This is making pipeline design complicated with steps involved in reading configuration file. Also the read of file is considered in document count, resulting is not so accurate document count in the dashboard.
Solution: Configuration files (lets limit to JSON) should be part of pipeline settings and they should be loaded as part of pipeline preparation and available throughout the pipeline. Either a new section to load configuration files or enhance parameters to load value (JSON) from a file.
Looking forward to hear from SnapLogic team.