Rank: Newbie
Joined: 3/10/2013
Posts: 2
Location: Earth
|
The product is pretty dynamic but comes up short in last mile functionality in two areas:
First is the ability to map using "Filter node-rows" conditionally to two fields in the textfile output of fixed length and then treat the empty fields as absent.
If my mapping logic said on Monday send free coffee coupon to Vlad in length of 10, and Tuesday send free coffee coupon to Paul in length of 15, and I mapped the coupon data to two fields in the text-file and ran-conditionally on the day of the week and selected fixed length output and treat empty fields as absent.. the requirement to meet both lengths is not met. Somebody doesn't get the free coffee coupon without allot of additional effort
Second is the ability to map using "Filter node-rows" conditionally to a single EDI object and provide conditional delimiters so you could have your coffee delivered! In one scenario Vlad prefers vendor A to deliver his coffee and that vendor uses their coffee edi with one implementation of:
ComponentSeparator
DataElementSeparator
SegmentTerminator
ReleaseCharacter
Paul prefers another vendor! His vendor uses a different
ComponentSeparator
DataElementSeparator
SegmentTerminator
ReleaseCharacter
The lack of an ability to using "Filter node-rows" conditionally at run-time for setting serviceChars makes getting your coffee delivered more difficult
These scenarios are the only two short-comings in the product in my opinion..
It would be neat if you guys started thinking about data pairs for hadoop.. and see some objects for map-reduce and hadoop as the GUI is good
But those two last-mile items make simple scenarios difficult
|
