Hi Atlas,
As we discussed before, I'll post the explanation of this:
What you're seeing is resultant from modifying a template that has completed applications. The assumption in this case is that the completed applications need to continue to exist in their current form, and so a copy of the template is created silently on the back end so the changes don't apply to the completed applications.
When this happens, the new template gets a flag set to mark it as a copy, and point back to the original. If you look at the AMS_Templates table, you'll see that the template copies get the moniker '- copy (#xxxxxxx)'. In most views, WFM is smart enough to see the copies and obfuscate their existence and treat them as a part of the main template. In this case, there's a query that's included in the report that's not specific enough, and it groups by unique template, thus the appearance of copies. I have gone ahead and submitted this to be changed, though, in work order #IOA-000038883.
The way to work around this at this time (if it is truly problematic) is to delete the completed applications. A simple way of getting a list of the applications that are affected by this is to run the following query with the name of the template copy:
select * from ams_application where templateid in (select templateid from ams_templates where templatename='Name of template copy here')
Hope this helps anyone else who runs into this!
