BISCIT Delivery Planning: Release Process

BISCIT Delivery Planning (BDP) Release Process Overview

At BISCIT, we periodically release new versions of the BISCIT Delivery Planning (BDP) to ensure our users benefit from the latest features and improvements.

Some BDP releases will require dependent changes to be performed in client's Epicor instance (like BPM, BAQ or UD Services). These changes are pushed to the Epicor instance as a package in the form CAB file during the new version update

Each release will notify users of the new version, provide access to test it, and inform them of the timeline for its release to the production environment.

Release Process:

Pilot Environment Release: BISCIT will first release the new BDP version to the pilot environment (Dispatch Portal Pilot). Upon logging into the production environment (Dispatch Portal Production), users will receive a notification informing them that a new version has been deployed to pilot. They can then test the release using their PILOT Epicor environment.
Production Beta Release: Two weeks after the pilot release, the BDP version will be promoted to the production beta environment: Dispatch Portal Beta. At this stage, users will log in using their LIVE Epicor environment credentials. This allows them to install the CAB file updates on their live servers, complete the update process, and test the new version in a real-world scenario before it goes to production.
Final Production Release: By testing the production beta version in advance, users ensure a seamless transition when the new version is promoted to the production environment. Since the update has already been installed and validated, users can immediately start using the new production version without needing to perform additional installations.

Benefits:

This release process ensures thorough testing and minimizes disruption, allowing users to confidently transition to new BDP versions with minimal downtime or inconvenience.