MyInstaller: Difference between revisions

Latest revision as of 16:24, 25 November 2024

There are several types of installations, maintenances and unninstalations.

Types of maintenances:

With device replacement
1. With Device replacement, the checklist is done, and the technician gets to the conclusion that the device must be changed. In part of validate the current IMEI, the technician will need to inform that it needs a new device. In this part he will give the new IMEI, he will confirm, and this new IMEI will be activated, but it keeps communicating in the stock company, it only gets migrated after a good validation. So after the activation the technician will validate the events, functionalities, and when he will close the tasks, the device is migrated to the final costumer
Without device replacement
1. Without device replacement, the checklist is done, the events are checked and the technician validates the same device with the same features or some new features but without many changes.

Types of installation:

With wizard
1. With wizard the task must have a contract, the device must be disabled and in a state different from Active, the rules for some events follwing the QBM wizzard rules and not the simple kind of installation (point 2)
Without wizard
1. Without wizard, the task can-t have a contract, the device must be enabled and the pre/active state.

@@ Line 1: / Line 1: @@
-{{QuatenusHeader}}There are several types of installations, {{QuatenusFooter}}
+{{QuatenusHeader}}There are several types of installations, maintenances and unninstalations.
+Types of maintenances:
+# '''With''' device replacement
+## '''With''' Device replacement, the checklist is done, and the technician gets to the conclusion that the device must be changed. In part of validate the current IMEI, the technician will need to inform that it needs a new device. In this part he will give the new IMEI, he will confirm, and this new IMEI will be activated, but it keeps communicating in the stock company, it only gets migrated after a good validation. So after the activation the technician will validate the events, functionalities, and when he will close the tasks, the device is migrated to the final costumer
+##
+# '''Without'''  device replacement
+## '''Without''' device replacement, the checklist is done, the events are checked and the technician validates the same device with the same features or some new features but without many changes.
+#
+Types of installation:
+# With wizard
+## With wizard the task must have a contract, the device must be disabled and in a state different from Active, the rules for some events follwing the QBM wizzard rules and not the simple kind of installation (point 2)
+# Without wizard
+## Without wizard, the task can-t have a contract, the device must be enabled and the pre/active state.
+{{QuatenusFooter}}