Workshop applicatie multi-user
When using the workshop app where multiple users are logged in, the first user to be registered in the app will be the 'admin user'. Until now, there was no indication anywhere in the app who this admin user is.
From the next release, of the workshop application, the name of the admin user of the workshop app will appear in the settings – Version info. This user can add/remove other users.
Settings workshop application with multiple users
From the next release of the workshop application, the settings can only be managed by the admin user. The admin user is the first person to be registered in the workshop app. As described above, after updating the app to the latest version, you can find the admin user under 'settings – version info'.
If only 1 user was registered in the workshop application, the settings are all visible to this one user.
Admin user:
Regular user:
Extra log – change repair type
From now on, a new log was added. It is now possible to see in the logs when a repair type has been changed. You can adjust a damage flow type by going to the damage details in the PlanManager job.
Additional fields damage details job
2 additional fields were added to the damage details of the job. You can now indicate on which date the calculation was created and on which date the estimation was approved.
You can find these fields by going to the damage details in the job.
You can also filter on these fields in the job list. When the job list is exported, these fields are also exported.
CAPS field updates
There have been a number of updates and additions to certain data fields that are sent to CAPS. Data fields and their trigger to populate CAPS are as follows:
|
CAPS field |
PlanManager trigger |
|
Job-Offer -> Accepted, Datetime-Accepted |
The date/time when the user clicks on Accept in the Workprovider queue |
|
Job-Detail -> Collection-Reqd |
Send YES, if the job is linked to Logistics where Arrival-Appointment type = Collection |
|
Job-detail -> Mgt-System |
Send “PLANMANAGER” |
|
Job-detail -> Est-System |
Send “AUDATEX” if there is at least 1 estimation linked to an AEG assessment. Send “MANUAL ESTIMATE” if there are 0 estimations linked to an AEG assessment |
|
Event -> Send event "SCHEDULED_HANDOVER" |
The date/time entered in the job for “Book out date” |
|
Event -> Send event "IN PROGRESS" |
The date/time entered in the job for “Start” |
|
Event -> Send event "WRITTEN OFF" |
Send date from first Log, type= “Total loss” when the total loss checkbox is checked, if none found, do not send event |
|
Event -> Send event "JOB COMPLETE" |
Send date/time from first log with type = “STATUS”, value “Completed” |
|
Event -> Send event "ORIGINAL EXPECTED COMPLETION" |
Send VALUE from first log with type = “PREDICTED_ENDDATE” |
|
Process -> Progress-Percentage |
Send 0 if task is not “completed”, Send 100 if task is completed |
|
External-Communication |
Currently all communication with type = 'public note', direction = 'send to' and status = 'concept'. Now will be everything but not internal/other, direction = ‘send to’ |
|
Communication-To-Name |
Send the name of the party the communication is being sent to/received from. If no name can be found, send NULL |
|
Event -> Send event "JOB CANCELLED" |
Send date/time from first log with type = “STATUS”, value “No repair” |
|
Event -> Send event "AUTHORISED" |
Job->Damage Details->Authorised. If empty do not send |
|
Event -> Send event "ESTIMATED" |
Send date in Job → Job details → Estimated. If empty do not send |
|
Event -> Send event "ESTIMATE APPOINTMENT" |
Send Job → Date estimate appointment |
|
Event -> Send event "ESTIMATE BOOKED" |
Send date/time of “CHANGED ON” for log type “Date appointment quote” |
|
Event -> "REPAIRER NOTIFIED" |
This should be the File-> Creation date in the database |
