Maintenance update 22.6.48654.0 Published June 17, 2024
Periodically, Sparkrock may publish maintenance updates between releases. This maintenance update replaces previously released updates. All maintenance updates are cumulative.
Problems that are resolved in this maintenance update
The following problems are resolved in this maintenance update.
Finance and Procurement
| Case Number | Description |
|---|---|
| In preparation for a future mySparkrock release, Sparkrock 365 requires changes to an API that shares vendor item number data for posted purchase invoice lines. |
|
| In preparation for a future mySparkrock release, Sparkrock 365 requires changes to an API that shares approval and rejection data for purchase invoices. |
|
| In preparation for a future mySparkrock release, Sparkrock 365 requires changes to an API that shares contact and vendor data for purchase requisitions. |
|
| In preparation for a future mySparkrock release, Sparkrock 365 requires changes to an API that shares approval and rejection data for purchase orders. |
|
| Sparkrock 365 requires the capability for finance department managers to be able to view, and then approve or reject expense claims that are associated with vendors that the manager is not authorized to view according to mySparkrock user or mySparkrock user profile security filters. When viewing the expense claim, Sparkrock 365 must restrict the finance department manager from viewing any vendor information other than vendor number and vendor name. |
|
| On the Deposit page, when you perform an import from Excel, Sparkrock 365 is not loading the values for Description that appear in the import file. Instead, Sparkrock 365 is automatically populating the description from the respective general ledger (G/L) account. |
HR Management
| Case Number | Description |
|---|---|
| In preparation for a future mySparkrock release, Sparkrock 365 requires changes to an API that shares location data. |
|
| On an HR request, when you choose Home > Process Individual Steps, Sparkrock 365 automatically changes the Status of the HR request to Approved, even though you have not chosen to process any steps yet. |
|
| The Ontario College of Teachers (OCT) integration requires changes so that Sparkrock 365 can communicate with the OCT service using Microsoft Azure. For more information, see Microsoft Azure support for the Ontario College of Teachers (OCT) integration. |
|
| When you change the value for HR Emp. Assignment Entry No. on an HR request, Sparkrock 365 is automatically updating the value of Benefit Annual Salary. Sparkrock 365 must only update the value of Benefit Annual Salary when the HR request involves changes to payroll related fields, such as Pay Grid, Pay Grade, Pay Step, Amount, Active FTE, and Pay Type. |
Payroll Administration
| Case Number | Description |
|---|---|
| Sparkrock 365 requires new payroll procedure event codes. For more information, see New payroll procedure event codes 009-1, 010-1, and 014. |
Scheduling
| Case Number | Description |
|---|---|
| On the Shift Card page, when you add an activity, Sparkrock 365 does not automatically populate values for Shift Work Date and No.. |
See also
New for Sparkrock 365
Finance and procurement maintenance updates
HR management maintenance updates
Payroll administration maintenance updates
Scheduling
Feedback
To send feedback about this page, select the following link: