Cisco Cisco Unified Contact Center Enterprise 9.0(2) Technical References

Page of 112
C-7
Template Design Guide Using InfoMaker for Cisco Unified ICM/Contact Center Enterprise & Hosted Editions, Release 8.0(1)
Appendix C      Considerations and Tips for Working with Custom Reports
Errors Opening and Saving Templates
Does the Template Name have Multiple Underscores?
When a custom template name has more than two underscores, the name that displays on the WebView 
report page is truncated to the second underscore.
That is, if you save three templates as:
olds_custom_templatename1 
olds_custom_templatename2 
olds_custom_templatename3
Then all three appear in WebView as:
olds_custom 
olds_custom 
olds_custom
To avoid this, append the prefix (
ipcc_
olds_
, or
 both_
) and type the template name without using 
underscores. (You can use hyphens.) Then add
 _custom
 at the end. For example,
olds-templatename1_custom 
olds-templatename2_custom 
olds-templatename3_custom
Note
Use this naming convention when creating new templates.
 
 
Do not change the names of existing templates, as doing so would affect Job Scheduler, Favorites, and 
Saved Reports.
Tempates That are Moved or Deleted
No templates were deleted, replaced, or moved in Release 7.0(0).
However, in WebView 5.0, new templates were added and several existing templates were deleted. The 
deleted templates were either replaced by templates in the same reporting category, replaced by 
templates in different reporting categories, or not replaced at all. 
  •
If a deleted template was replaced by a new template in the same reporting category, saved reports 
use the replacement template and work correctly. This is the case, for example, with 
agteam01
which was replaced by 
agteam20
 in Release 5.0. 
  •
If a deleted template was replaced by a new template in a different reporting category, saved reports 
using the deleted template are not migrated and will not open. You need to create a new report using 
the replacement template.
  •
If a deleted template was not replaced, saved reports using that template are not moved to the 
WebView database and cannot be accessed through WebView.