Ksivagurunathan
Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Date Validation using Expression Library
it wasn’t a straight forward solution. we developed a custom javascript function that read input data,rules and validate them and add a json output for every row in case of any error. Javascript function is generic for all data type, nullable and not nullable. Input rules and input rows could change3.4KViews0likes1CommentRe: Dynamic Data Validation
the way we developed, we don’t need to make changes to the snaplogic pipeline if we want to validate different set of files. it could be new set of validation or few new column validation to the same set of files. all we need to do is add validation rule to the table and corresponding file name. its more dynamic validation of data and column name in a file1.6KViews0likes1CommentRe: SnapLogic August 2019 (4.18) Release
Looks like snaplogic released a patch 3 version a week before the deadline to upgrade the nodes. I would expect snaplogic to send a communication ahead of time(few days) like major release notification. Based on the email from Snaplogic patch3 version upgrade is recommended strongly by snaplogic but we don’t have enough time to check and make changes to regression test plan. Another request is - UAT release package name is different than elastic.snaplogic.com release package name atleast for few days or a week . eg - snaplogic-sidekick-4.master-5771-x86_64.rpm the UAT environment is package name is not updated the same day as elastic.snaplogic . as we deploy the packages in automated way, we had pass two different package name and later again update UAT package name in our automated deployment code process.998Views0likes0CommentsRe: Triggered Task node not available
cjhoward18: This is done upon every trigger separately The triggered tasks are tied to a particular plex, but not a particular node within the plex.–> If you look at the on-premise URl of triggered task it is tied to a node and our caller application uses that onpremise url instead of cloud URL. So we are impacted here, could we continue to use the cloud URL even after decommission the node(Triggered task on premise url is pointing to this node) , we don’t need to create new task ?2.8KViews0likes6Comments