It would be great to have the ability to have reports run on a certain time interval and then emailed automatically. The time interval and recipients could be chosen when setting up the report. Either having the report printed in html in the body of the email or have an excel file attached to the email would work.
For example: I would like a report to run every Friday and be sent to certain people.
Both for Service Requests and Sales Meetings planning would be usefull to have a kid of report called
something like Planning report showing Dates on columns(for visits, meeting, events, etc) and being able to select another field for rows and cell contents.
It would be something like what MS Excel calls Pivot Tables. I understand it may be not trivial to develop but, from the management point of view, the applications would be many. Time management is an high priority issue for all.
For instance, think about a report with dates in columns titles, technicians names on rows titles and the the scheduled customer's name, with contact's phone number and Service Request descriptions inside the cells.
I would like the ability to export the data from a workspace view rather than having to create a report first. Second best would be to be able to create reports that mirror workspace views (maybe even keep them linked so that a linked report always matches a particular view).
I need to be able to create reports detailing outstanding PLM tasks for all of my team-members. It would be greatly benefitial to be able to generate a report detailing my own and other people's outstanding work.
In PLM360, the history of an item is available through a change log, however, the change log is not available through the API for each record in order to enable historical reporting on the actions for an item.
Use Case: changes to Product Name as it moves from temporary to legal versions.
Previously we had problems with product name changes over time because we were communicating to customers about products they didn’t buy.
We could write on every transaction into the ODS
For Ad hoc we could clone records into another workspace and store them for a historical view