Ideagen Internal Audit (Aura): What happens to Pentana’s ‘actual time’ data when synchronisation with RetainTime is disabled?
Who is this article for?Users who want to learn about what happens to Pentana’s actual time data when synchronisation with RetainTime is disabled.
Elevated permissions are not required.
It is possible to simultaneously disable the synchronising of data between RetainTime and Pentana and to activate time recording in Pentana. We do not migrate existing timesheet data, although existing summary data against audit assignments and audits remains in place.
If a customer wishes to switch to recording actual time in Pentana then care should be taken to input in Pentana data for audits where time information is still being entered, as starting a timesheet in one system and completing it in the other will give incorrect results.
This article describes the effect of disabling RetainTime on existing Pentana data.
1. Detail and Examples
- Where a system is comprised of RetainTime and Pentana, data is held in two places
- The Retain database holds detailed information about each timesheet row, like the recording of time by a person against a job for a time period
- The Pentana database holds summary information about time recorded by all people for their audit assignments, which is further summarised against audits
- The synchronisation process takes the Retain data and does the summarising, then records that information against audit assignments and audits.
- Running the Disable RetainTime customisation breaks the link between the two systems but does not make any changes to the data on either side. This means that where time data is stored against an audit it will remain as is, however if a Pentana timesheet entry is then made it will overwrite what’s there, with undesirable consequences.
1.1 Example: Before disabling the RetainTime link
Two auditors, Jeff and Jemima, work on Audit XYZ and record time in RetainTime.
Timesheet data
|
|
21 May |
22 May |
23 May |
24 May |
25 May |
|---|---|---|---|---|---|
|
Jeff |
7h |
7h |
7h |
7h |
7h |
|
Jemima |
7h |
7h |
7h |
7h |
7h |
In Pentana this displays as follows.
Audit Assignments
| Person | Actual Time |
|---|---|
| Jeff | 35h |
| Jemima | 35h |
Audit Details
|
Audit |
Actual Time |
|---|---|
|
Audit XYZ |
70h |
1.2 Example: After disabling the RetainTime link
The summary data remains the same until a change is made, but as there is no historic timesheet data, adding a timesheet for an existing audit will cause the summaries to recalculate based on only the new Pentana timesheet.
As an example of the impact that can have.
Jeff wants to add a day in the following time period to Audit XYZ.
The timesheet would look like this.
|
|
28 May |
29 May |
30 May |
31 May |
1 June |
|---|---|---|---|---|---|
|
Jeff |
7h |
|
|
|
|
However, as Pentana has no historic timesheet data to add, the audit assignment summary now looks like this.
Audit Assignments
|
|
Before disabling |
After disabling |
|---|---|---|
|
|
Actual Time |
Actual Time |
|
Jeff |
35h |
7h |
|
Jemima |
35h |
35h |
Audit Details
|
|
Before disabling |
After disabling and ‘adding’ one day |
|---|---|---|
|
Audit |
Actual Time |
Actual Time |
|
Audit XYZ |
70h |
42h |
Important Note: Please therefore be aware that if you are wanting to stop using RetainTime and start using Pentana timesheeting it will probably be necessary to re-enter some time data for audits that are in progress, and for non-audit tasks.