Framework Database Tools

None - not job specific.

Applies to all Framework tables.

When troubleshooting data issues, such as when data is missing or not displayed.

(Typically only when instructed by Insula.)

When logistics orders on jobs are not linked to logistics items.

This may be after orders have just been integrated from a 3rd party system, to prevent the need for supervisors and/or admin saff to perform the linking on a job by job basis.

When job(s) require a linked file folder structure to be created on disk.

The folders may not have been created when the job(s) was initially created in Framework.

Permanently delete the client(s) from the Framework database, for the client(s) specified by the tool criteria.

Note: that this process is a permanent (physical) delete and cannot be undone.

Permanently delete the file(s) from the Framework database, for the file(s) specified by the tool criteria.

Note: that this process is a permanent (physical) delete and cannot be undone.

Permanently delete the job(s) from the Framework database, for the job(s) specified by the tool criteria.

Note: that this process is a permanent (physical) delete and cannot be undone.

When logisitcs items have had partial progress ticked off but their % complete is not accurate.

This may have been due to logistics item and call data syncing between updates from various other sites/sources.

This is typically not required as the Framework logistics system regularly updates this information during normal operation.

None - not job specific.

Performs the following construction-related updates for the selected job(s):

• Update logistics progess
• Update workflow stage
• Raise Construction Claims
• Update Construction Delays

When logistics and/or construction data needs to be completely updated based on all recent data updates/uploads.

This may be used to bring all construction stats up to date for various reasons, e.g: for running reports

When construction claims data needs to be completely updated based on all recent data updates/uploads.

This may be used to bring all construction stats up to date for various reasons, e.g: for running reports

When construction delays data needs to be completely updated based on all recent data updates/uploads.

This may be used to bring all construction stats up to date for various reasons, e.g: for running reports

Updates the construction period history notes for the selected job(s).

This tool copies the Operator and Supervisor notes from the current construction period to the construction record, as seen on some Construction Overview screens) 

When construction overview notes needs to be refrshed to the notes from the current construction period.

This may be required when tablet sites have uploaded other notes or when the 'current' construction period has been updated to the next period where no notes exist.

Recalculates the construction progress stats for the job(s) specified by the tool criteria.

This tool recalculates stats across any 'dirty' construction periods for the selected job(s) i.e only for construction periods that have had activity recorded since the job's last progress update.

When construction progress stats need to be completely updated based on all recent data updates/uploads.

This may be used to bring all construction stats up to date for various reasons, e.g: if the preferenes for auto-progress updates is Disabled, or for running reports. 

Recalculate the construction stats for the job(s) specified by the tool criteria.

This tool recalculates stats across ALL construction periods for the selected job(s), regardless of whether or not there has been any recent activity recorded since the job's last progress update.

When construction progress stats need to be completely updated based on all recent data updates/uploads.

This may be used to bring all construction stats up to date for various reasons, e.g: if the preferenes for auto-progress updates is Disabled, or for running reports.

Update Job Status

When logisitcs items have been call-completed but the item stats do not reflect this.

This may have been due to logistics item and call data syncing between updates from various other sites/sources.

This is typically not required as the Framework logistics system regularly updates this information during normal operation.

When maintenance requests have inaccurate workflow stages according to the workflow dates on the requests.

This may be required when logistics sites have updated and synced maintenance requests ir if requests have been updated outside of the Framework suite.

Updates Framework's internal record of current Primary Key (PKID) values across all tables in the Framework database.

This tool incorporates site-specific system keys as well as keys for the main Framework database, whereby remote sites (e.g logistics tablets) can reserve block ranges of Ids for exclusive record insertion in a table.

None - not job specific.

Applies to all Framework system keys.

When troubleshooting data issues, such as duplicate key runtime errors.

This is required when data has been inserted into the Framework database outside of the Framework suite, e.g via custom queries or integration

(Typically only when instructed by Insula.)

Sets diary appointment links and diary item numbers for tender appointments for the selected job(s).

This tool also clears presentation and current appointment links and counts for non-final tender documents.

When the count of tender appointments is incorrect for the job.

This may be required when tender appointments have changed and/or tender documents have been superceded.

Recalculates the workflow stage for the selected job(s).

This tool executes the usp_updateWorkflowstages stored procedure for each selected job.