Communication logs for order data storage
In the app, the engineer can:
• perform actions such as Temporary fix, Reassign, Wait, Pause or Discontinue
• enter a reason for the selected action,
• take photos,
• add signatures.
This data is sent from the app to the back-office (
Planon ProCenter ) and stored in unique
communication log records on the order. In > on the
Main tab, you can define which user-defined communication logs will be used for this purpose. See
Main.
Configuring communication logs in ProCenter
Make sure that Communication logs selection steps are available on the following selection levels:
• Photos, actions or signatures added to a job are stored in the communication logs of the Orders business object. These communication logs are displayed on the Order details selection level in Work Orders .
• Photos added to a maintenance activity are stored in the communication logs of the maintenance activity. The communication logs of maintenance activities are displayed on the Orders sub-details selection level in Work Orders . Drill down as follows to go to that level: > > .
Generating codes for communication logs
Since the code of the communication log is mandatory, make sure that the Code field of the communication log has a code generator on it:
1. Go to Field definer and put the Communication logs business object under construction.
2. Go to the Fields step and select the Code field. Enter an automatically generated mask in the Default value field. For example &CODEGEN(####,F). This is mandatory in order to enforce that each communication log record is unique.
3. Put the business object to completed and press F9.