Task Changes Slow in Metadata Read Snap
I have been changing task schedules and then trying to read them with the SnapLogic Metadata Read snap. There seems to be a several minute delay in the Read snap noticing the change but the change ap...
Forum Discussion
Depending on what you’re trying to do later in your pipeline, the approaches that don’t involve Pipeline Execute are either awkward or not possible.
With Pipeline Execute, this becomes straightforward. Urge your organization to reconsider their decision to avoid one of our product’s most powerful and useful features.
Thanks. I think that this is good advice.
As a integration layer, the tool is always expected to apply some level of logic to transformation or conditional routing. Business Logic is a very wide terminology, and it should be propagated to integration layer only if it is complex in implementing either at source or destination. For the given scenario, it is complex to implement in Source / Destination layer, so nothing wrong in implementing in Snaplogic. Based on the acceptance, there might be a scenario where all the business logic will be pushed to Snaplogic, you got to discuss with the Integration and Enterprise Architect and let them take the decision on where the business logic should be. This is completely my opinion based on my experience in Integration area.
hey,
I also had same doubt as you are having, however we had it for more complex one.
in scenario you explained, you can make use of ternary operator (like if statement ? do this : else do that) , additionally you can use router also to separate out the result to different flows.“set the invoice date or generate revenue recognition…”
this should be possible with snaplogic.however in case more complexity such as looking up from existing datasets and complex multi source comparisons, its better to handle it at application end as offers more functionality.
Thanks
Thank you for the response. I definitely agree that is easily doable to handle this type logic in SnapLogic, and I personally think it makes sense. I’m just curious as to why they state that application/business logic should be handled in the source/target applications over SnapLogic. Perhaps my definition of business logic is different than theirs.
