Continental Plans

Version Date Notes By
0.1 2021-02-27 Initial release jto

Description

This project was done specifically for Continental and involves a custom plan module which features and detailed in a video which the link is in the section below

Documentation

Please see video in the link below in order to understand all the functionality present in the project: https://drive.google.com/file/d/1u9onAynA2xT6JCxIGB4cJzKsDkWU_zYF/view?usp=sharing

Changes to the original requirements

Please see the project changelog, contains both Lousado and Malaysia most updated changes and corrections.

This excel only contains the malaysia changes there were made during the project development and testing: https://docs.google.com/spreadsheets/d/1osGIIVB6xl8rmYGmbTHXX_PhzhocNfZx/edit#gid=951244593

Integration

The software at the time of writing is present in two continental factories. The malaysia factory:

  • Bitwarden credentials as Continental MY
  • Repositories: https://gitlab.wemake.pt/continental

For tech support and for sending the application files for update contact chi-siang.poh@conti.my and CC CST_AO_IT_Infrastructure@conti.my, mohd-izammudin.ishak@conti.my

The people responsible for the project are: mohd-izammudin.ishak@conti.my (preferential) and nicolas.hovnanian@conti.de

The Lousado factory:

  • Bitwarden credentials as Continental PT
  • Repositories: https://gitlab.wemake.pt/continental

For tech support contact and for VPN activation contact ctire_lo_sysmgt@conti.de and CC sara.azevedo@conti.de

The person responsible for the project is: sara.azevedo@conti.de

Scheduled jobs

In the Malaysia factory you can use the commands:

  • plans:force-dispatch-other-action-alerts
  • plans:notify-action-responsibles

To trigger the jobs in cause of failure

The Lousado factory: Uses default jobs which are activated in the software

Update

In order to update continental software its advise to have a copy of the project in your local machine. With a copy in your local machine update the application normally as you would the default sgi. Then encrypt the files and zip the backend and frontend and send it to the server. If the client is Malaysia Continental you have to email tech support with the files (use google drive to send them a link for the file download). If it is the Lousado Continental there is a share folder in the C drive that you can access for copying the files. In your computer you should go to file explorer and use the following address: \10.205.32.38/share

After the files are in the clients machine unzip them. Before doing anything else please put the application in maintenance mode and backup the data.
The frontend can be updated exactly the same as any other SGI installation. The backend its a little different because you have to pay attention to the storage, config and public folder before copying new data.

The storage folder unless new files have been added you don't need to change anything there.

The config folder please be careful about copying files because there may be changes in the client machine you should check the files for differences before overwriting.

The public file may have changes in the .htaccess and web.config so please check those files before overwriting data.

The rest of the files can be overwritten, after that run the usual procedures:

  • Composer dump autoload
  • php artisan migrate and reseed
  • Restart queues and clear redis
  • Remove application from maintenance mode

Now the application is up and running please access it and check if it doesn't have errors.