In my dashboard, I have several charts that I have created and would like to see them as I have rotated or have performed slice movements.
The problem is that when I get the charts looking like I want them, they return to their normal 3D un-sliced and un-rotated views once closed. Therefore, when I want to view them at a future time, "like daily" I have to once again rotate & slice it to my liking and changing percentages or numbers etc.
Is there a way to save the view of the chart within my dashboard so that I don't have to go through this every time I open a chart?
I'd love to see more robust script management. Ideally I'd like to see the ability to officially version or rev scripts. In addition to the Save button, you could add a button for Version. This would store the script in its current state with the appropriate verison number.
In addition, I'd like to review previous versions of the script and have the option of making a previous version the current version.
byAsingh511-14-201210:52 AM - edited 11-14-201210:53 AM
When using the import tool, performing a bulk import of values into a "single selection" linking picklist is possible. Unfortunately I cannot select a "Multiple Selection" linking picklist it in my import to do the same thing.
This feature is very important for our company since it would allow us to show our linked product items in one specific field, as opposed to having multiple "single selection picklists"--which doesn’t make a clean visual.
The data I have is in a excel format. With over thousands of entries, having the import tool to bulk import the linking picklist values in the multiple selection picklists would allow me to provide my tenant with the information it needs efficiently and visually appealing.
byAsingh511-06-201208:22 AM - edited 11-06-201208:25 AM
The TABS section of the preview should open up and expand when clicked on instead of redirecting to the specific item. This would allow the quick easy access to key information such as BOM items, attachments, relationships, changes ext. Also there should be the ability to click the specified print view for the item as well.
Where a Workspace requires different pieces of data to be entered at different states in the workflow , it would be good to guide the user through the specific information they are required to add by defining fields (or sections) of the item details that correspond to specific workflow states. In addition, it would be good to allow users who can change the workflow state to do this directly from the item details tab.
A good example of this is a Request for Information (RFI) workflow where one party wants to ask a question of another party and get a response.
For the given workflow below
When a user is creating the RFI, they are given a response field, which is irrelevant at this stage.
Once created. The recipient has to edit the RFI to add their response to the item details.
User then needs to update the Workflow state to say they have added a response.
Instead, it would be useful to give the user buttons to select the workflow state they want to move to based on the available states
If selecting "Reply to RFI", the user would then be taken to an edit details page just allowing the fields associated to the "RFI Reply Sent" state to be edited. This would drive user to follow the workflow required.
It would be great to have an admin permission that allows users to edit fields that are set as 'non editable' in the field definition. It is very time consuming when testing to have to navigate to the workspace manager and change the field properties. It would also be a useful feature to have as an administrator to make changes and corrections easily.
I would really love some improvements from the advanced print view
1. I need a way of having global control over all print views. eg, if I have a company footer then I want to change It once and apply to all print views however this is just an example and It would be useful for a lot more then that.
2. I have created the print view I want in HTML and I have It looking the way I need It however It looks horrible when I put It into PLM 360, It appears that the HTML code used by PLM is very old and is not able to read CSS at all, even if It is embedded into the html code itself.
I really need this to be resolved, currently I am not able to create anything near professional enough to give to a client.
Attached is a screen shot of the report straight in Chrome, the other is what It looks like coming out of PLM. It will not take you long to work out which one is out of PLM.