PowerBuilder Applications Deployment Process (CCARCS, DAPLS, FTAE)

Owned by Sufyan Maghur
Last updated: Sept 26, 2023 by Alain Asgill
1 min read

  1. Build & Deploy an EXE Package from Appeon PowerBuilder

  2. Copy Package to \\CIVAV Shared (Specific Application Directory) with new version

  3. Allow System Administrator to test the application package (Already copied to CIVAV directory)

  4. Review the DEPLOYMENT USERS Excel sheet (If required) to update the users receiving the application package (Optional)

  5. Create an SM-GS ticket to deploy application (Corporate Application Packaging and Support Team requires 2 weeks from ticket creation to Deployment date)

  6. Inform the Deployment Team (Corporate Application Packaging and Support) to give them heads up

  7. Copy the Application Package from \\CIVAV Shared (Directory) to the deployment team general directory \\ncras22\CSSG Release\CSSG Staging\ (Specific to the application and efined SM-GS Ticket

  8. When the package is ready (Corporate Desktop Quality Assurance and Testing) will contact you by e-mail providing 2 remote devices to test the application installed using the deployment package

  9. Test the application to confirm the version number and that it is performing as expected (You can involve the System Administrator in the process)

  10. Follow up on the deployment process with the Corporate Application Packaging and Support on the deployment date

  11. Update the Application Version and message in the System Table

  12. After a validation period restrict access to previous versions from the System Table