From what I l know, only change of status is considered an update, not the attribute editing. Current limits are really artificial right now as they assess the performance across many customers. If you feel you might reach that limit, best to ask CARE to raise that limit - you will need a good business reason for the PM to consider it.
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.comhttps://www.ttecDigital.comhttps://RobertWC.Blogspot.com------------------------------
Original Message:
Sent: 12-31-2024 15:29
From: Jim Mayer
Subject: Work Automation Update Limits
Our org is moving forward with the work automation and while we are waiting on the licensing for the Work Automation, we are looking ahead at a few things prepping for access and getting answers. Some of the questions that we have came from the Developer Center Limits page that we found, one this page it says there is a limit of work items created per day for an org, and a separate limit for work items updated per day per org.
- What counts as an update to a work item? Is it any of the fields associated with a work item, such as the priority or the assigned user? Are there any exclusions on what counts as an update?
- There is a field that shows configurable for both created and updated. Does this indicate that a request could be put in to increase the limit for an org?
#API/Integrations
#Implementation
------------------------------
Jim Mayer
------------------------------