If you see this arrow, click to expand for more information!
If you see this arrow, click to expand for more information!
We will add additional information and images under these arrows.
Reviewing performed tasks
Why might the Re-apply sub-tasks button not appear after changing the task to an I&T type?
Why might the Re-apply sub-tasks button not appear after changing the task to an I&T type?
If the 'Re-apply Sub-tasks' button fails to appear, the issue may stem from asset base dates or how the routine servicing has been set up. Consider the following possibilities and fixes:
Asset Base Date Alignment: Ensure that the assets' base dates align with the major servicing due dates for the routine. If routines are added as ‘unscheduled maintenance,’ they’ll adopt the task’s due date.
Update or Adjust Dates:
Option 1: Update the routine start date to match the base dates of the assets. Then delete the 'unscheduled maintenance,' refresh the routine, and add the relevant 'scheduled maintenance' back.
Option 2: Modify the asset base date to match the routine start date and follow similar task updates as in Option 1. These adjustments will ensure the button appears and functions as intended. Why does the Re-apply Sub-tasks button suggest deleting newly added assets? This scenario usually arises when the new assets do not meet the inclusion rules of the routine. For instance:
Routines may be configured only to include assets with specific tags.
Newly added assets without those tags will not match the routine's criteria and may be flagged for removal when the button is used. To resolve this:
Review asset tags: Check whether the newly added assets lack required tags or have mismatched entries.
Ensure assets match the inclusion rules of the routine. How can I resolve asset deletion issues flagged by the Re-apply Sub-tasks button? To address issues where new assets are flagged for deletion:
Apply Correct Tags: Add the required tags to the newly added assets so they comply with the routine's inclusion rules.
Reapply Sub-tasks: Return to the task and click the 'Re-apply Sub-tasks' button again. Once assets match the routine’s criteria, they will be added to the task instead of being flagged for deletion.
What if more products are added to the tasks created from a quote?
What if more products are added to the tasks created from a quote?
When extra products are added to the task which were not part of the quote, Variations have occurred appears above the profitability summary on the main page of the task - hovering the mouse over this notification will inform you that additional works have been added that are not part of the originally quoted works and must be toggled on to be invoiced.
What is the Re-apply sub-tasks button on the Work tab of the task?
What is the Re-apply sub-tasks button on the Work tab of the task?
The Re-apply sub-tasks button appears on I&T tasks when changes are made to the property assets serviced under these routines AFTER the task is created:
A pop-up screen will display summary changes, showing which service tasks will be added or removed based on updates to the property assets.
By clicking Confirm, you can apply the updates so that the task accurately reflects the up-to-date asset list and their required routines.
Key Notes
This feature ensures that tasks remain consistent with asset modifications, like additions or deletions, after a task has been created.
It is only accessible on the web version of the platform, not in the mobile app.
Use the button whenever assets or routines linked to a task are modified to ensure alignment.
Can field users on the app use the Re-apply sub-tasks button?
Can field users on the app use the Re-apply sub-tasks button?
The Re-apply sub-tasks is only available on the web and cannot be accessed from the app.
Why is an asset listed more than once on the Work tab?
Why is an asset listed more than once on the Work tab?
If an asset is linked to multiple routine services or levels on a single task, a separate service task is created for each routine and level, resulting in the asset appearing multiple times.
How is the Value column calculated on the tasks list?
How is the Value column calculated on the tasks list?
The task value is calculated based on performed billable items, including:
Invoiced amount from Fixed billing contracts on Billing tasks.
Any performed billable service tasks.
However, the task value is only updated overnight, so any items performed today will be reflected the next day. For more up-to-date information on task profitability, review the Task profitability and Task work in progress reports in Insights and Reporting.
Dispatching and closing the tasks
Is it necessary to create and publish a report before dispatching a task?
Is it necessary to create and publish a report before dispatching a task?
Reports are automatically created and published when the task is dispatched.
Why does the dispatch email say the service report is non-compliant?
Why does the dispatch email say the service report is non-compliant?
In some cases you may see mention of the service report being non-compliant in the dispatch email like the example below:
The compliance of the report is determined by the Report Failure Criteria on the report type. By default, any result marked as Fail or No Test will make the report non-compliant.
What can dispatching errors mean?
What can dispatching errors mean?
PartnerRateLimitExceeded: The accounting partner has received too many requests in a short period of time, please try again later.
Authorisation failure –(invalid_grant): This error occurs when a sync refresh token expires and can be fixed by disconnecting and the reconnecting the accounting partner.
PostDataInvalidException: Please reach out to [email protected] for further investigation.
How to Track the Origin of a Task (e.g., from API, Portal, Manual)
How to Track the Origin of a Task (e.g., from API, Portal, Manual)
Understanding where a task originated can be crucial for workflow management and troubleshooting. While Uptick doesn't have a single dedicated field that explicitly states "Created by API" or "Created via Portal," you can determine a task's origin by examining its details and associated information on the Uptick Web Platform.
Here's how to trace the source of a task:
Manually Created Tasks:
Identifier: Look at the Author field on the task details page. If a task was created manually by an office user, their name will be listed as the author.
Timeline: The task's timeline will show "Task Created" with the name of the user who created it.
Tasks Created from the Customer Portal:
Identifier: When a client creates a task through the Customer Portal, the Author will typically be the primary contact associated with that client's portal access.
Notes and Documents: Check the task's notes or documents for any information submitted by the client, which often indicates it came from the portal.
Tasks Created via API:
Identifier: Tasks created through an API integration (e.g., from a third-party system) will often have a generic or system-level user listed as the Author. The name might be something like "API User" or the name of the integration itself.
Task Name/Reference: The integration might populate the task name or an extra field with a unique identifier from the external system. Check for patterns or specific prefixes in the task name.
Tasks Generated from Defect Quotes:
Identifier: If a task was created from an approved defect quote, it will be linked to that quote. On the task page, look for a link to the "Source Defect Quote."
Automatically Generated I&T Tasks:
Identifier: Routine maintenance (I&T) tasks are generated automatically based on your servicing schedules. These tasks will not have a specific user as the "Author" in the same way a manually created task does. Instead, their creation is tied to the system's schedule for the property's routines.