Business Object Performance
An example of poor Business Object performance is a page of Business Objects that takes some time to load. Alternatively, there might be a noticeable time difference when loading Business Object records of the same type.
Performance might be different when comparing the Browser Client and Desktop Client.
To ensure optimal Business Object performance:
- Close any open calendars. Calendars can use a large amount of memory when open.
- Review configuration for the individual One-Step™ Action which changes the Owned By property and handles the re-assignment of the Incident. Data may be loading in the back end, or a Relationship may be reloaded based on constraints.
Verify memory or CPU use.
You can address high memory/CPU usage by ending some processes or purchasing additional memory.
If you are a hosted customer, check with Cherwell Support before trying either of these solutions.
Review any automatic actions. These are set in the Business Object Actions window (for more information, see Define Automatic Actions for a Business Object).
For example, selecting the Execute before saving record check box may be the cause of a time lag. In this situation, you could optionally clear the check box and set an Expression to run this action based on a true/false condition.
For more information on other simple action/event automation processes, see Define Actions for a Simple Action/Event Automation Process.
Review relevant Relationship properties. These are set in the Relationship Properties window (for more information, see Define Advanced Properties for a Relationship).
For example, you can set your Incident Relationships to load keys only if the Relationship is one to many instead of loading everything. For more information on this specific scenario, see Run the System Analyzer to Evaluate Business Object Structure.