Version Control for Kinetic Customizations/BPMs/BAQs/etc

I’ll try to be novel and keep it short. I’m a big proponent of adopting modern development practices, which of course includes source control. There’s a very old Epicor Idea that has a lot of votes and Epicor was going to share some plans by Summer of 2024… :person_shrugging:

Source control is great, but mostly what we have done is exporting components and store them. Useful, but to really get the benefit of source control is to treat it like source code and be able to deploy from a repository. One thought is to use the REST output (JSON or XML) and use that to export and import. @klincecum has done great work on the exporting, but to deploy we’ll need some help.

Another repository thought is to push an export file (directive, BAQ, etc.) to GitHub. A GitHub action would extract the archive, maybe un-BZip it where necessary, make a folder representation of the export file and convert certain elements (code, images, etc.) into their native formats. Now the export file and its contents would be in a repository in a state usable by diff tools and have a known commit hash/ID.

3 Likes