Configuring 'Edit' pages for status-related actions
You can make it possible, or even mandatory, for field engineers to add additional information when they select a new action on the app (such as Work, Travel, Wait and so on). Selecting a new action on the app causes a status change for the work assignment, which is communicated to the back-office, together with the added information.
The field engineers can add their additional information via 'Edit' pages. These are text boxes that can be configured for each action on the app. To be precise: on the destination status ('To' status). For example, all status transitions that move to Work will get the same Edit 'Work' form on the app.
You configure the Edit […] pages by hiding / displaying fields, and/or making them mandatory or read-only. Commonly used fields are Action date-time (the start of the status transition), Comment or Reason.
 | For the app to function properly, it is strongly recommended not to remove all fields from Edit […] pages. Some fields are protected from removal, because they are vital to the workflow / process. Sometimes, these fields also have a fixed position on the block's layout. Pinned fields can be recognized by this icon:  |
Examples of Edit […] page configuration:
• If field engineers start work on a different date-time than the original date-time provided on the work assignment, you can allow them to adjust the Action date-time (start date-time) upon selecting the status Work.
• If field engineers complete their work, you might want to make the Action date-time read-only.
• If field engineers select the Travel status, you can allow them to specify a Action date-time and an expected arrival date-time.
• If field engineers select the Wait status you might want them to specify a Reason.
• If field engineers select the Discontinue (Stop) status on the app you might want to make it mandatory for them to specify a reason before the work assignment is returned to the back-office.
• If field engineers cannot complete the work assignment themselves and want to directly allocate it to another team member, without redirecting to the back-office, you can allow them to select the Reassign status. When they reassign the work, they will go through the signing off procedure themselves, while a new work assignment is created and immediately reassigned to the selected team member. The edit form that belongs to the Reassign action can be configured, for example by adding fields, changing labels and changing other settings.
• If field engineers are required to complete a work-related questionnaire before they start their work, you can configure this for the status Work. Similarly, this can be configured for the statuses Temporary fix, Travel and Done.
| | At the bottom panel, the Edit details pages for the statuses Work, Temporary fix, Travel and Done all include a Questionnaire details page. This page is a reference to a 'Questionnaire - Work assignment' scope which can be configured in the Questionnaires TSI. The scope ensures that a work-related questionnaire is displayed at an appropriate point in the work flow, i.e. when the engineer selects an applicable work assignment status on the app. See: for more information. The questionnaires themselves must also be configured in the Questionnaires TSI. |
• etc.
Procedure
1. In > , select and expand the relevant sub web definition.
Edit […] pages are displayed for every available action (status transition) in the sub web definition:
◦ Accept
◦ Reject
◦ Travel
◦ Work
◦ Wait
◦ Pause
◦ Stop
◦ Temporary fix (Note: only for sub web definitions that are not based on a PPM order)
◦ Done
◦ Reassign
2. Select the Edit […] page you want to display and / or configure.
3. At Module settings, set the Navigation name, Code, Description and Icon as required.
4. At the bottom panel, select the Edit details page.
5. In the data section, on the Page properties tab, edit the page properties as required.
6. Select Work assignment details block.
7. On the data panel, select the Edit fields tab and edit the available settings with regard to visibility, position and icon, and add fields, as required.
| | • On the > , the Is visible setting is read-only, to avoid breaking work flows on the app, like for example being able to confirm that all work has been completed on the Edit 'Done' page. • The Work assignment details blocks for the Reject, Reassign, Wait, Pause and Stop statuses have the Action date-time and Reason fields configured by default. Actions and reasons must be configured in Planon ProCenter , see Action and reason configuration (MM and PMFS). |
8. If available on the web definition, like on the Edit 'Reject' page for example, select the Communication log details block.
9. On the data panel, select the Add fields tab and edit the available settings and fields, as required.
10. Repeat the procedure for any of the other Edit […] pages, as required.
The Edit 'Stop' page includes the configuration for the Engineer's overview details page on the app. This is the page that engineers get to see before they sign off. Edit the page properties as required, by adding additional field or adjusting field settings on the corresponding Work assignments details block.
11. The Edit 'Done' page and Edit 'Temporary fix' page include the sign-off procedure for the engineers and, optionally, their customers. This is explained separately. See Configuring the Engineer's overview and Sign-off pages.
12. Click Save.
The configured edit options for field engineers become available on the app.