Step 5: Archive and Backup

To implement version control in a collaborative environment, use the Two-Branch Strategy: - main: Production-ready version - changes: Development and staging updates - A Git repository (on GitHub, Azure DevOps, etc.) - Git installed locally - Access to the repository - Your .acrepox previous exported file bash git clone https://your-repo-url.git cd your-repo-folder bash git checkout -b changes` If changes already exists: bash git checkout changes` Place your exported file (e.g., CustomerDW.acrepox) into the project folder. Then run: bash git add CustomerDW.acrepox git commit -m "Updated repository with latest model changes" git push origin changes` From GitHub or Azure DevOps: - Go to the Pull Requests section. - Create a new PR from changes → main. - Include a clear description of what’s changed. Review Checklist: - Have you tested the export? - Are credentials excluded? - Have you added documentation for changes? Store previous versions of .acrepox files in a versions or archive folder within the repo for traceability, or use releases. Best Practices

• Export regularly during development milestones
• Use folders to organize models by project/component
• Use tags or naming conventions for major releases
• Communicate changes clearly in PR descriptions
• Use secure CI/CD pipelines for automated deployment Restoring a Version

To restore a specific version: 1. Checkout the version or tag in Git 2. Open the .acrepox file in AnalyticsCreator:
File > Open from file 3. Your full repository structure will be restored as exported.