Maintenance update 27.0.2607.550 Published February 13, 2026
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
| Description | |
|---|---|
| Sparkrock Impact inserts an incorrect link in approval notification emails that are sent to mySparkrock-only users. The link directs the approver to Sparkrock Impact instead of mySparkrock. Because mySparkrock-only users do not have access to Sparkrock Impact, the approver cannot open and approve the expense claim as expected. |
|
| When a user selects the link in an email to approve a document, such as a purchase order or an expense claim, Sparkrock Impact briefly opens an intermediate page, and then behaves unpredictably. As a result, the Requests to Approve page does not open as expected. |
|
| On the Purchase Requisition and Payment Request pages, the Upload files option is not available for limited access users in the Documents FactBox. As a result, limited access users cannot upload attachments directly from the FactBox as expected. |
|
| When a user selects the link in an email to approve a document, such as a purchase order or an expense claim, Sparkrock Impact opens the Handle Notification Email Link page, instead of opening the Requests to Approve page as expected. |
|
| Sparkrock Impact is not sharing payment request and payment request template data with mySparkrock as expected due to an API-related problem. |
|
| Sparkrock Impact is not sharing purchase requisition and purchase requisition template data with mySparkrock as expected due to an API-related problem. |
|
| Sparkrock Impact is not sharing purchase code and salesperson code data with mySparkrock as expected due to an API-related problem. |
Scheduling
| Description | |
|---|---|
| When a supervisor re-offers a previously filled vacant shift after the original employee vacates the shift, mySparkrock displays an error when another employee tries to bid on the shift. This API-related problem occurs because Sparkrock Impact does not clear the previously accepted bid records when the shift is re-offered, which prevents a new bid from being created for the same shift. |
Related information
New for Sparkrock Impact
Finance and procurement maintenance updates
Scheduling maintenance updates
Feedback
To send feedback about this page, select the following link: