- Collapse View
- Expand View
- Mark all as New
- Mark all as Read
- Float this IdeaStation to the Top
- Subscribe
- Bookmark
- Subscribe to RSS Feed
- Invite a Friend
When your cursor is on top of a field, display the field description as a tool tip
Description
After much persistance, the Advanced Print View is proving to be practically impossible to use with the current HTML editor method. It also has a number of bugs which I have noticed surrounding working with Tables and Font Size.
Impact
The current method takes too long to achieve anything, if at all, in regards to getting it to look how you want it to.
Severity
High
Solution
Would it be possible to provide PLM with an MS Word file which already has all the formatting done. In the Word doc we could then place the PLM Artifacts so that we can get awesomely good looking and formatted prints with minimal effort?
I would expect that the doc would have to be rendered to a PDF on the server side before providing it to the user for viewing/download.
A method such as this would provide the user with the means to correctly define formatting options such as;
- Tables (including borders - line types, colours and weights)
- Proper Headers and Footers
- User a Table of Contents
- Page Numbers
- Text Styles
Description
Working through the creation of an Advanced Print View is a tedious process. It's nice to have the Advanced Print View open on one page, and then the actual Print page open in another. Typically this requires a constant refresh of the Print page to see the affects of changed settings on the Advanced Print View.
Impact
Currently, on the Advanced Print View when you press the Save button it takes you back to the print views list. Then you need to press Edit for the print view to go back into the view for editing. Then the cycle happens again, ...
This is very tedious.
Severity
Medium
Solution
On the Advanced Print View, it would be nice to have an extra button Save & Close. This would save the view and then close back to the views list.
The existing Save button should be repurposed so that it simply saves the view and leaves the users in the edit mode.
Description
The Advanced Print View has a number of issues with the formatting on the print.
Refer image below;
Green - Using the default format ${workspace.metadata.grid.title.value} shows the original tab name which is Grid. In this workspace the Grid tab name had been renamed. This is not showing the changed tab name.
Blue - Between grid rows, it is quite common to get gaps between grid lines.
Red - Grid rows are split between pages. The split row should be starting as a full row on the next page. Having these rows split across pages makes it harder to read.
Impact
Looks messy. Not professional enough to give to clients.
Severity
High
Solution
See if these issues can be improved for neatness.
Maybe rendering the Advanced Prints as HTML isn't the correct answer to this. Maybe the print should be converted to a PDF on the server-side in order to obtain correct formatting on the print, and then served to the client as a download, and/or the PDF displayed to the browser ready for viewing and then printing.
Description
The Header/Footer artifact is ok, but it lacks the ability to have a header/footer on each and every page.
Impact
This does not act like a true header and footer which you expect to see when working in other applications like MS Word. Currently if feels as though it is printed from a web page, rather than a document.
Severity
High
Solution
I understand this could be a different issue to solve, but it would be good if the prints could be made a little more neater and professional by allowing a header and footer on each page to make it look more like a proper document.
Is it possible to get extended info on your browser tabs for admin purposes?
Elaboration:
Multi tab browser panes allow for quick switching to the user-groups-roles & setup pages.
The problem is all these tabs are called: "PLM"
If you are in the project management ws, the browser tab staets: "PLM - Project Management".
Can the frequently used admin pages (for multi tab users) be extended like below:
(with a choice button wether or not you might want it or not).
"PLM - Users Groups Roles" with "PLM - Users", "PLM - Groups" & "PLM - Roles"
"PLM - Setup" with "PLM - Workspaces", "PLM - General" & "PLM - Scripts"
"PLM - System Log"
Of course this could be done for Tools & Reports aswell.
Regards, a multi tab geek
Description
I would like to have an 'Attachment' field so I can add it to the Item Details tab or in the Grid tab.
On the Grid tab for example, this would allow the attachment of files to very specific row entries.
Impact
At the moment by putting a file on the Attachments tab, it has no relationship back to any data entered elsewhere in the Workspace.
Severity
Medium
Solution
Allow us to place an 'Attachment' field.
Description
Despite the Advanced Print View being customisable with being able to design a unique layout and place fields specifically as you want them, it isn't as customisable when it comes to the graphics. It looks like PLM has a number of CSS files which is driving how the print looks, specifically when it comes to HTML Tables (I can't remove the lines).
Impact
There isn't any flexibility in changing how the HTML is rendered to screen. Because of this, it is impossible to get a decent looking print which would be suitable to give to clients.
Severity
High - I consider this to be one of my highest wishes. A lot of what I would like to use PLM for is to create reports which I can give to my clients. They have to look professional.
Solution
We need the ability to override any CSS definitions which PLM is forcing on us. It would be nice to be able to define our own CSS files so that we can not only override the defaults, but to also provide a level of consistency across all Workspace Advanced Prints.
Workspace Field - Required *
Status: AcceptedDescription
When browsing the field list in a workspace or on the grid view it is hard to determine whether a field is a 'required' field. I personally find this particular parameter for a field as an important one to identify quickly.
Impact
Not having this simple enhancement, makes the checking process of required fields a little longer by then having to enter the field editing view to determine it's required state.
Severity
Low
Solution
Simply add * to the fields in the field list in the same way as they are seen to the end user.

