Parent/Child Requests

Parent/Child request relationships allow users to relate requests together, create dependencies, and track projects in FMX.

How it Works

Create parent/child relationships for requests with any work request module in FMX. Work request modules include maintenance requests, technology requests, project requests or custom. Requests that have parent/child relationships will be linked together. The requests will also display the status of the related requests. 

Creating Parent/Child Requests

One way to create a new child request is by selecting the "New request" button on the request you would like to be the parent request. Then select which module you would like the child request to be from. If you select the option without "child" then this will just create an associated request which will not total costs or have to be completed prior to the parent. 

Once you select making a new child request the request will automatically populate the following from the parent:

• Building
• Location
• Equipment
• Due Date

These can be changed while filling out the other fields and submitting the request. 

Or when editing/creating a request add existing requests to be child requests. When you select the "plus" button in the "Child requests" section of a request you can choose from existing requests on your site. These can be from the same work request module or from a different work request module. The field is a typeable dropdown where you can search by name or the FMX ID number. When a child request is opened a parent request can be added in the "Parent" request section. 

Dependencies

Child requests and associated requests can have dependencies added to them. Requests that have a dependency blocking it, will have a "blocked" status. Users can choose the following dependency options:

• No dependency - the order does not matter
• Is blocked by this request - the current request must be completed first
• Is blocking this request - the request that must be completed first 

When viewing the request that has a dependency there will be a warning at the top with a link to the request that is blocking it. The request can not be resolved until the dependency is. 

To add a dependency when editing/creating a request select the option you would like on the dependency dropdown field. A child request can block parent to cause the parent to have the "blocked" parent.*

*Child requests always have to be completed before a parent request can be resolved. 

Associate child requests to add dependencies between them. This will allow you to make sure child requests requests are completed in a particular order. To do this when editing or creating a child request go to the "Associated work requests" field. Then use the field to find the child request you would like to associate. Then select if this is request is "blocked by this request" or "blocking this request". Then select save when you are done.

For example(see below):

• The child tasks of "Office Change" (Parent) are dependent on a specific order of completion.
• "Framing" is blocked by "Demolition", therefore "Demolition" must be completed first.
• "Framing" is blocking the completion of "Electrical"
• Framing must be completed before "Electrical".

Costs & Actions

Costs logged from a child request will total on the parent. 

Actions logged on child requests will also have timeline entries on the parent request. These will have a link back to the child request and display the action that took place. 

Costs logged on a parent request(from child requests and the parent request) will connect to Capital Planner. If you would like to add the Capital Planner please reach out to your account manager at FMX.

Setup

To setup parent/child requests on your FMX please follow the below steps:

1. Go to the admin settings and to the "General" section

2. Next go to the work request module(maintenance, technology, project or custom) settings and select the modules you would like to have parent/child relationships and associations. Then select "Save". 

Once the above steps are done then you can choose which users have access by following the below steps:

1. Go to Admin Settings and to the "User type" section

2. Then select edit for the user type you would like to have access 

3. In the "User Type" section change the "View request associations"  to "Any", "Accessible buildings", or "Own". Then change the "Associate requests" field to "Any", "Accessible buildings", or "Own". Users also must have access to the modules you want to associate as well. 

4. Select Save.