Custom modules give customers the ability to reskin work request modules to fit a specific need within their organization.

Some common custom modules are Building Health, Project, Supply, Human Resources, Guest Registration, Incident, and Custodial Requests; however, there are many more possibilities.

Each custom module follows a similar framework and thus, the bulk import templates are identical excluding any custom fields.

The custom module bulk import template is broken out into multiple sheets in order to record both open and completed (historical) data. The sheets are as follows:

Requests: This is the "main" sheet and will need to be filled out for both open and historical work requests. The data on this sheet will need to be referenced on the subsequent sheets.

Responses: This sheet captures the communications and ongoing labor recorded on each work request.

Resolutions: This sheet captures the completion information of a work requests. Use this sheet only if you're importing completed work requests.

Reopenings: This sheet captures completed work requests that have been reopened. 

To bulk import work requests into your FMX site, follow the steps below:

*The ability to bulk import data is configured at the user type level by each module. This must be set up by a site administrator. 

1. Navigate to Bulk Imports tab on the left-hand side of your page:

BULK_IMPORTS.png

2. Click on the Import button at the top right of the page:

IMPORT.png

3. Select Custom Module Request Import:

*We will use a Building Health Request costume module as an example.

mceclip0.png


Requests 

4.1. Populate the template with the necessary information. Columns that contain an asterisk (*) are required.

mceclip1.png

 

Name*: This is the title of the work request. If you're importing historical data from another system, you may want to include the ID number for tracking purposes.

*FMX will create a unique ID for each work request when imported.

Examples: Contact tracing form request, Room 231 needs sanitized, Student injured on playground, Employee quarantine absence, etc.

Building*: This is the building where the work order needs to be completed.

Name*: Room 231 needs sanitized
Building*: Elementary School


*Work requests cannot be imported unless the building exists in FMX.

Request Type*: This refers to the category of work request.

Name*: Room 231 needs sanitized
Building*: Elementary School

Request Type*: Room Refresh

*Work requests cannot be imported unless the request type exists in FMX.

 

On behalf of: If another user requested the work request but didn't directly enter the request in FMX, type their name in here.

Location*: This refers to the specific area in the building where the work request needs to be completed.

Name*: Room 231 needs sanitized
Building*: Elementary School

Request Type*: Room refresh

Location: Classroom 231

Equipment items: List any fixed assets that are associated with the work request

Due date*: the date when the work request is expected to be completed

Description: detailed notes about the particular issue or inquiry

Custom Fields: Custom fields are always an option if you need to add any other required/non-required details to your work requests. Custom fields must be added by a site administrator. 

Created Date* and Time*: the date and time when the work request was submitted

User*: the user who submitted the work request

Followers: Followers can track and view the details of the request through email notifications. Type in their names here.

Assigned Date and Time:  the date and time when the work request was assigned to user

Assigned users: the name(s) of the user(s) assigned to the work order

Outsourced: If the work request needs to be completed by an outside vendor, you can mark "Y" for yes or leave blank.
*If you're not importing completed (historical) data, proceed to step 5; otherwise continue reading the next section.

Responses

4.2. Populate the template with the necessary information. Columns that contain an asterisk (*) are required.

mceclip2.png

 

Request*: This refers to the name of the work request listed on the Requests sheet.

Date* and Time*: the date and time when the response was submitted on the work request

User*: the user who submitted the response

Followers: Followers can track and view the details of the request through email notifications. Type in their names here.

Response*: a comment or detailed description of the work performed on the work request

Private: If your organization has private comments enabled, marking this column with a "Y" for yes, will create a private comment; otherwise, leave this field blank.

Custom Fields: Custom fields are always an option if you need to add any other required/non-required details to your work requests. Custom fields must be added by a site administrator. 

Work Hours - Users: the names of the users who logged labor hours on the response

Work Hours - Hours: the amount of labor hours each user logged on the response

Inventory used - Names: the names of the inventory items used on the response

Inventory used - Quantities: the quantity of the inventory items used on the response

Resolutions

4.3. Populate the template with the necessary information. Columns that contain an asterisk (*) are required.

mceclip3.png

 

Request*: This refers to the name of the work request listed on the Requests sheet.

Date* and Time*: the date and time when the work request was completed

User*: the user who resolved the work request

Cost: any miscellaneous cost needed to resolve the work request

Resolution*: a comment or detailed description of the work performed on the work request upon completion

Custom Fields: Custom fields are always an option if you need to add any other required/non-required details to your work orders. Custom fields must be added by a site administrator. 


Work Hours - Users: the names of the users who logged labor hours on the resolution

Work Hours - Hours: the amount of labor hours each user logged on the resolution

Inventory used - Names: the names of the inventory items used on the resolution

Inventory used - Quantities: the quantity of the inventory items used on the resolution

Equipment items - the name or names of the fixed assets used in the work order resolution

Reopenings

4.4. Populate the template with the necessary information. Columns that contain an asterisk (*) are required.

mceclip4.png

 

Request*: This refers to the name of the work request listed on the Requests sheet.

Date* and Time*: the date and time when the work request was reopened

User*: the user who reopened the work request

Reason*: a comment explaining the reason for reopening the work request

5. Once you have completed filling out the import template, save the document to your device.

6. Navigate back to the Bulk Import page in FMX.

7. Title the name of your import in the Title section.

mceclip4.png

8. Next, click on the paperclip icon in the Template section to upload your completed import file 

mceclip5.png

9. Once your bulk import is titled and the file is uploaded, hit the Save button to complete your import.

mceclip3.png

10. If there are any errors on the import, such as typos or mismatched records, FMX will steer you in the right direction by pinpointing the column, row, and cell of the error.

Click here to read more about bulk import errors and how to fix them.

11. Once you have corrected the errors on your template and re-saved the file, repeat steps 7-8.

12. When your import has been completed, a green banner message will appear at the top of your screen that reads "Success! (Your template name) has been imported with (x of records) records".

mceclip6.png

Was this article helpful?

  • 0 out of 0 found this helpful