Key takeaways
Here is a list of key takeaways:
-
There is a limited computing bandwidth for each customer to (re)create project charges.
-
Three variables driving charge (re)creation process performance:
-
For example, every small project update (time tracked, project task edit, project's date edit, etc.) is a trigger.
-
Scripts or workflows tied to the charge record may slow down the creation speed
-
# of total charges to be created – how many charges are to be (re)created?
-
# of charge (re)creation triggers – how often are charges (re)created?
-
How long does it take for system to create a single charge – how long individual charge record needs to be created?
-
-
Forecast charges are being recreated often and are usually the bottleneck.
-
Audit your system to see how often your project forecast charges get recalculated – is that needed?
-
Explore 'Forecast Charges on Demand' project preference and use it whenever possible.
-
-
Midnight charge run consumes by default 'In Progress' projects and other statuses further defined by customer.
-
Keep your project status up-to-date.
-
Manage project statuses and select those that are relevant for the midnight charge run.
-