Hi Guys,

I would be extremely benefitial if I could run a script automatically immediatley after an item has been created. It could be used to automatically create relationships after a user has created an item.

Thanks,

David.

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 VERY useful to allow a tenant to be divided into secure "Projects" so that access to information relating to different projects could be controlled centrally.  This should allow workspaces to be managed centrally, but used optionally on each project.  Similarly, roles should be managed centrally, but users are given a role on each project allowing them to have differing levels of access.  This model is already used to good effect in Buzzsaw.

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

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.

As mentioned earlier during a telephone survey I would to see/get help configuring a basic employee management workspace for the sole reason: to be able to use the TCO for an employee to calculate TCO's for (E)CO's and more accurate project cost estimations up front.

This workspace can be:

- basic, because most smaller companies already have a program running to manage employees. So you would need a script accessing/reading a datafile from that specific program's db

- extended, if you would want to create a workspace that makes 3rd party programs managing employees obsolete. A small nudge to move more & more company assets into the cloud/PLM.

Furthermore (maybe for a later date) I believe there was an intention to create a share/marketplace for AutodeskPLM360 scripts/workflows/workspaces to share or buy best practice addons to your existing PLM config.

I would like to know how that is coming along; wouldn't want to struggle on a script when an expert in that field has already created something similar.

Hi,

The script time limit is currently set to 500ms. It would be great if you could set a higher scirpt time limit if required in the script set up.

Thanks,

David.

It would be useful to allow users to directly export a Workspace Item listing to Excel.  You can set-up a report to do this, but for basic users it would help to directly export from the listing screen.