Issues

API have asked if we can have the day detail ribbon, the hours / units shown only reflect those that are approved. i.e declined timesheets should not have hours included in this total value (Ticket 121972)

#106139 CTTG CO2591 Customer says CT is unusable. "CTS taking a long time to load up and often resulting in time outs or "error retrieving data" messages." Reported multiple times over the past year and just continues to get worse. Both backed (Michael) and UI (Ben K) have evaluated. This is the outcome: - There are a limited number of concurrent connections any browser can open (8 is the average. Older browsers can be as low as 5, where browsers like Opera can be as high as 10). Each lookup is added to the browser queue and processed in order of "first returned". Any concurrent calls made beyond that max is queued and will show up as "(pending)". We try to mitigate this by utilising our own JS queue manager that limits calls by throttling to 5 concurrent connections and grouping requests that have the same URL+params. This significantly reduces calls to the server made by our UI while 'spreading the load'. Our servers also have a limited number of concurrent connections they can open. The default is 10 per IIS instance. If the server has maxed out, any further requests just sit there in a holding pattern until the server has an available connection. This will also show up in the browser as "(pending)". This is how we can see service / API responses taking less than a couple seconds, but it takes many minutes in some cases for the request to complete. Response time is very poor, but actual request time is fine. There is nothing we can do about this other than (a) reduce calls by reducing rows and columns, or (b) reduce calls by combining data into larger datasets, or (c) increase our instances for our load balancers.

Be good to be able to correct data stored for prior periods WKSWKD and WKSABS via Pay Adjustment instead of doing imports which have very little audit trail.

It would be nice if we could use pay adjustments to allocate earnings for payments that we make to the period they relate to. This would be useful for NZ Hol Act remediation payments. But it doesn't apply to all payments that relate to a prior period so I would like to be able to tell which ones went into previous period earnings and which ones didn't.

Banking systems prevent duplicate amounts from the same funding account within in 6 days. It would be great if the system alerted to this and helped with correction.

Colliers are wanting to move to Dashboard but their PPT 1 Tax Invoices (a crystal report payslip) for the Contractors is blocking them from doing so. The current payslips are pulling information from the TRANS_COMMENT table (this holds the data required for the tax invoice) but we have been advised that this cannot be replicated in new payslips if they move to Dashboard. We have tried to replicate this data for Colliers in other ways, such as via a MyPA, however we have not been successful in meeting the requirements using this method. We need to find a solution for the Tax Invoices so that Colliers can move to Dashboard. Not having dashboard is stopping the delivery of new technology which will improve both the customers and our productivity. We have exhausted all of our options and would like to open up to any other suggestions on how we could deliver a compliant Tax Invoice for Colliers as well as move them onto Dashboard. Please let me know if you have any questions, or require any other information.

You need to be able to select the day the employee schedule starts but currently dashboard schedule defaults to the first day of the schedule ie if the employee starts on week 2, day 3, the dashboard allocates week 1, day 1 This functionality is currently available in MWG but obviously we want to have this in Dashboard as we're moving off MWG Often employees are on rotating rosters or schedules with more than one week.

When a user incorrectly configures the manager manages groups, check for potential issues and prevent. e.g. Managers normally manage Direct Reports and there should not be a case where managers manage All Active employees - especially if there is already anotther config.

Sealord mentioned this is critical since myWorkGroup has this functionality that their managers use extensively. i.e. Manage by Exceptions where know exceptions can be accepted leaving only those that need actions

An incorrect reporting line where a position ends up reporting to itself causes failures for both Clever Forms and Clever Timesheets. Needs to be prevented. Checks Affinity Position Controller Posts imports Clever forms - create posts