The Functional Area Usage page provides an overall summary of the PTC Creofunctionality used in your organization.
Access Location: In the Go to page list, select Functional Area Usage.
Benefits and Description
Dan, I have a couple of questions.
1.) I see the dashboard, and all of our systems are configured to send data to PTC, but everything is showing zeros. Is there something that needs to happen to turn on this tracking? (We are running Creo 3.0 M090 & M100)
2.) You said in your video that only the owned functionality will be displayed. I'm seeing many functions that we don't own (options modeler, mold, mfg, etc.) Any idea why?
3.) I know this is a different topic, but this new capability is not nearly as useful without the ability to relate the GUID to an actual user. For those of us who are willing to upload machine and user name, please allow this information to be displayed instead.
Jim Barrett-Smith wrote:
Hopefully in the next release we will be able to tie the report of the unused apps to your license file. Feature tracking was a huge project and there was only so much we could achieve in the first release.
You can find his answer to my question here Enable Performance Advisor to show the real Login Name and Host Name of sessions instead of the mask...
I think they made the video with some beta version of PA, because in my dashboard nothing appears under Functionality area.
First off, thanks for watching the video.
1) Your builds of Creo 3.0 are certainly compatible with this functionality (Creo 2.0 M220+ / Creo 3.0 M090+) - Can you check the zip files in the quality agent sentfiles folder at "\AppData\Local\PTC\QualityAgent\SentFiles"? You are looking for files named "featureTracking.....json". If they are indeed being sent, we need a deeper investigation with a TSE, which i can help start.
2) I contacted the PM to ask about this observation; I am not sure if he misspoke in the video, or if its not working as designed.
3) Yes, I hear you. PM is investigating the best, and safest way to address this from out side. For now, I suggest looking at the workaround script documented here (How to identify a user in Performance Advisor). Pairing this collection script with a browser extension called a 'word replacer' can solve the issue. I did a POC of this, but I don't feel comfortable posting the full solution here as a PTC employee. If someone were to connect the dots, or even post the full solution, i am sure they would be very popular here ).
Thanks for the feedback, and look for further improvements as we all grow in this arena.
Here's what I see:
By the way, I just listened again and he said, "you can also review functionality that you do own but is not currently being used".
Dan, Thanks for the reply.
I was wrong about the builds. Most of our users are still on M080 and the .json file isn't present in their sent data. On the other hand, I have been running M100 since July 1st (8 days) and all of those .zip file DO include the feature tracking .json files.
Here is the "guts" of one of them (minus the UUID):
Does a certain period of time have to pass (more than 8 days) before reporting becomes available? (I'm hoping not 4 weeks...)
Tom Uminn #2 will need an SPR after discussion with Jim (PM). Can I have an engineer initiate an case and contact you? - I will post the article tracking the issue once created.