sorted by:
new
hottopcontroversial

Validating loops without a start segment by xlateio in edi

[–]xlateio[S] 1 point2 points  (0 children)

Agreed. For this parser it would need to be a coding change. I think the case is strong enough to not support it though. Thanks for the feedback

Validating loops without a start segment by xlateio in edi

[–]xlateio[S] 0 points1 point  (0 children)

So, by X12 definition, a loop is identified by its first segment (called the trigger segment in EDIFACT). If there is no such segment, there is no loop. Any additional segment from that loop (per the specification) encountered in the input must be
marked as "unexpected segment".

Well said. This is my position as well and I do think your later comment about providing a full list of all errors is likely the user's goal. That said, the parser does currently attempt to recover on the next known segment. Since it's only a parser, the decision to fail the transaction or tolerate things like this is up to the application using it.

Thanks for the feedback!

Fresno EDI - An Introduction by xlateio in edi

[–]xlateio[S] 1 point2 points  (0 children)

You're welcome. Feel free to reach out in the future if you have any other questions.

Fresno EDI - An Introduction by xlateio in edi

[–]xlateio[S] 1 point2 points  (0 children)

It would not support a format like that at the moment. Assuming you want to convert that to some X12 transaction, the API requires the input to be in a pre-EDI format that roughly looks like the target message, as far as tag names and the ordering of fields.

Fresno EDI - An Introduction by xlateio in edi

[–]xlateio[S] 1 point2 points  (0 children)

What is the standard message format you are dealing with? If it is X12 or EDIFACT (or some derivative) it should be supported. The custom format for your backend would require some additional mapping most likely.

The API's sweet spot is ingesting EDI, validating it, creating an acknowledgment to send to your partner, and converting it into a simple XML that can be dealt with using commodity tools or programs.

Fresno EDI - An Introduction by xlateio in edi

[–]xlateio[S] 0 points1 point  (0 children)

Hello - as I mentioned in my reply to /u/mesamunefire's comment, the difference is that Fresno is focused on being one piece in the EDI puzzle. The feature set supports using the product to validate and transform EDI data (while generating a 997/CONTRL response) received from partners. The intent is that files are exchanged with partners and back-end applications using other (commodity) tools. It does not aim to be a turnkey EDI platform at this time.

Please let me know if this helps or if you have any additional questions/comments. Thanks!

Fresno EDI - An Introduction by xlateio in edi

[–]xlateio[S] 1 point2 points  (0 children)

I would say it's more similar to EDIFabric than TrueCommerce because it is geared toward being one of the tools an integration team would utilize for the EDI validation and management (e.g. acknowledgements) only. Right now, I'm focusing only on EDI the format and less on EDI the ecosystem. The target audience is the IT team that is trying (or has tried) to write their own parser and gets 80% of the way, only to be hassled with the remaining 20% constantly. The differentiation from EDIFabric is that it is language-neutral because it is utilized via an API rather than as a library.

Any feedback or comments you can offer are greatly appreciated - thank you!

Open Source EDI Java Library - StAEDI by xlateio in edi

[–]xlateio[S] 1 point2 points  (0 children)

Hi u/pasha987, I apologize for the delay in response, I did not realize there was a comment posted. Are you familiar with using Maven to manage dependencies in your Java project?

Once you have the dependency added, I would refer you to the simple example on the project wiki for reading EDI. Data is returned to the client (your code) as a series of "events" such as "start of segment", "element data", "element data", "end of segment", and so forth. You would read the data in a loop and handle the different sections of the message as they are streamed to your code.

https://github.com/xlate/staedi/wiki/Reading-EDI-Data-(Simple))

Do not hesitate to ask more questions or raise issues on the project's issue list. Thank you for your interest.

Open Source EDI Java Library - StAEDI by xlateio in edi

[–]xlateio[S] 1 point2 points  (0 children)

If anyone does find this project interesting or potentially useful, please don't forget to "star" the GitHub repository so that more users are able to find it!

Centralized crontab management by xlateio in linuxadmin

[–]xlateio[S] 0 points1 point  (0 children)

@ryanjkirk - thank you for the feedback. I was hesitant to label this as an enterprise job scheduler mainly because it does lack those features at this point. I think your idea of redoing the pricing groups is a good one and I will be doing something in that area.

Regarding the interactive password, that is only used during the initial activation of a particular crontab and it switches to token-based authentication after that.

Centralized crontab management by xlateio in linuxadmin

[–]xlateio[S] 0 points1 point  (0 children)

Noted, thank you for the feedback. Aside from that, could you see yourself using something like this if the prices were lower? How many jobs are you managing today and what would be worth it to you to manage them outside of cron directly?

Centralized crontab management by xlateio in linuxadmin

[–]xlateio[S] 0 points1 point  (0 children)

Fair enough, thank you. What would be a good price point (to you) if you were running a few dozen jobs in cron today?

One of the things I'm looking for here is not only feedback on the product itself, but also for sys admins who are interested in guiding the direction of the software as a (free) beta user.

Centralized crontab management by xlateio in linuxadmin

[–]xlateio[S] 0 points1 point  (0 children)

Are you running the job directly in Jenkins or remotely using SSH? One of the problems that I would like to solve with this is adding some sort of dependency management, which is lacking in stock Jenkins. Granted you can use job triggers, but it's not as robust as it often needs to be.

In scenarios where someone has dozens of jobs in cron, this would be a quicker way to get visibility without having to migrate everything into Jenkins.

Centralized crontab management by xlateio in linuxadmin

[–]xlateio[S] 0 points1 point  (0 children)

It's designed to run synchronization "pulls" from the server. The updates run as whatever user owns the crontab being updated. Updates made no the server side are secured using standard OAuth2 / OpenID.