PLM 360 IdeaStation
Share your wish list directly with the Autodesk PLM 360 Development Team
New Idea
4 Kudos

We would like the ability to establish default or role-based configuration of a user's dashboard, so that pre-selected charts are displayed upon login and we don't have to provide instructions to each and every user about how they should set up their dashboard.

 

One should also be able to configure which areas are expanded or collapsed by default on a user's dashboard page.

 

Thanks,

Michael

Status: Accepted
HI Michael, This is an interesting request. I need a little bit more details. 1. The administrator will need to set all the different views. For example if there are 10 groups, 10 setups will be require. 2. Who will determine which groups require which dashboard view for the different charts. For example if sales, you will need to activate Sales Quote, Customer, RFQ, Tasks and Projects. 3. How will you handle the scalability and maintenance. If you have 200+ users, you will need to determine each time you add a new users to know which category and what groups that belong to. 4. What if there's overlapping? Or certain individuals require additional charts, do you allow access, or the administrator will need to add the requirements. This feature request sound good, but we need to understand how to manage the roles/groups and scalability for big accounts. thanks, Trung
5 Kudos
Colgan

Run Script on Editing Grid

Status: Comments Requested
by Contributor Colgan on ‎02-26-2013 09:10 AM

Hi Guys,

 

We have an action script running to sort out the row order of a workspace grid. However, the script will only run when we edit the Item details. This method of sorting the grid rows is a little tedious. It would be great if the script would run by simply editing the grid.

 

Thanks

 

Saoirse

Status: Comments Requested
I'm planning for advancements on behaviors (events for scripting), this will certainly be in the list of enhancements!
6 Kudos
DonovanJr

Scripting Access BOM & Sourcing Tab

Status: Duplicate
by Active Contributor DonovanJr on ‎12-03-2012 11:37 AM

We need access via the Server Side Sripting to both the BOM Tab & Sourcing Tab.

 

I believe there are several support threads as well as Ideastation references to this functionality but I felt we needed a clear Idea Post for this functionality.

 

Similar to the new object record item.workflowitems recently added we need to have information contained in the BOM & Sourcing tabs for use in scripting.

 

An example would be having an assembly shown on an Sakes Quote Grid and a workflow that would explode the BOM children of that assembly into the grid of an RFQ and access the default supplier to create a master RFQ for cloning quoting purposes.

 

Ideally this would be read/write access for back feed updating of costing etc.

 

Status: Duplicate

 

BOM Final implementation:

RELATED and QUANTITY are required, others are optional:
item.boms.addBOM({ RELATED: part1, QUANTITY: 1.2, CUSTOM_FIELDS: { FIELD: 'value' }, ITEM_NUMBER: 10, QUOTE: part1.sourcing[0].quote[1] })

First two arguments are required, others are optional:
item.boms.addBOM(part2, 2.3, { FIELD: 'value' }, 11, part2.sourcing[1].quote[2])

var bom = bom;

Can assign:
bom.item.ANY_CUSTOM_FIELD
bom.qty
bom.quantity - Synonym for bom.qty
bom.quote
bom.ANY_CUSTOM_FIELD

Can read:
bom.id
bom.item
bom.item.ANY_CUSTOM_FIELD
bom.itemNumber
bom.descriptor
bom.qty
bom.quantity - Synonym for bom.qty
bom.quote - See Sourcing Tab support for fields which can be read
bom.ANY_CUSTOM_FIELD

bom.remove()

NOTE: You can assign to quote, for example:
bom.quote = target.sourcing[0].quote[1];

However, you cannot change the quote through the BOM:
bom.quote.min = 10;
is not guaranteed to persist changes to the quote. To ensure that changes are persisted, change the quote via the sourcing:
target.sourcing[0].quote[1].min = 10;


Sourcing/Quote implementation:

SOURCING:

Everything but SUPPLIER is optional:
item.sourcing.addSourcing({ SUPPLIER: supplier1, SUPPLIER_PART_NUM: 'ABC-123', MANUFACTURER: 'Manufacturer Name', MANUFACTURER_PART_NUM: 'MAN-123', COMMENT: 'Comment', CUSTOM_FIELDS: { FIELD: 'value' } })

Everything but first argument is optional:
item.sourcing.addSourcing(supplier2, 'XYZ-789', 'Other Manufacturer', 'OTH-789', 'Comment', { FIELD: 'value' })

Can assign:
item.sourcing[0].supplier
item.sourcing[0].supplierPartNumber
item.sourcing[0].manufacturer
item.sourcing[0].manufacturerPartNumber
item.sourcing[0].comment
item.sourcing[0].ANY_CUSTOM_FIELD

Can read:
item.sourcing[0].supplier
item.sourcing[0].supplierPartNumber
item.sourcing[0].manufacturer
item.sourcing[0].manufacturerPartNumber
item.sourcing[0].comment
item.sourcing[0].quote
item.sourcing[0].quote.id to get quote ID
item.sourcing[0].ANY_CUSTOM_FIELD

item.sourcing[0].remove()

QUOTES:

Args are: min, max, leadTime, leadTimeType, unitCost, comment
leadTimeType can be 1, 7, 30, 365, 'Days', 'Weeks', 'Months', or 'Years':
item.sourcing[0].addQuote(100, 200, 12, 'Days', 12.34, 'Comment')

Can assign:
item.sourcing[0].quote[1].min
item.sourcing[0].quote[1].max
item.sourcing[0].quote[1].leadTime
item.sourcing[0].quote[1].leadTimeType - Can be values listed above
item.sourcing[0].quote[1].unitCost
item.sourcing[0].quote[1].comment
item.sourcing[0].quote[1].default - true or false

Can read:
item.sourcing[0].quote[1].id
item.sourcing[0].quote[1].min
item.sourcing[0].quote[1].max
item.sourcing[0].quote[1].leadTime
item.sourcing[0].quote[1].leadTimeType - Will give values above
item.sourcing[0].quote[1].unitCost
item.sourcing[0].quote[1].comment
item.sourcing[0].quote[1].default - true or false

item.sourcing[0].quote[1].remove()

 

2 Kudos

Please can you look into increasing the number of links that can be added to this area

There is a lot of wasted space that can be utilised here

Another 2 graphs each side of each row can be added, adding another 12 without changing the aspect of the dashboard.

At the moment this is just wasted space that i certainly can utilise

1 Kudo
sten

UI Improvement suggestions

Status: Future Consideration
by Active Contributor sten on ‎02-27-2014 01:14 PM

1) Allow for workspace shortcuts in the unused area of the title bar. (marked in red)

 

2) Add 'X' for closing the item window (green)

  Right now I can chose to expand the window to full size or back to the split view. There is no simple way to get back to a full screen list view. (workspace only with no item in focus.)

 

3) Be better at remembering column widths.

Untitled.png

Status: Future Consideration
Hi Sten, We appreciate your ideas and inputs. We will add this Idea to our future enhancement list. Thank you, Trung
1 Kudo

It could be very handy if condition and validation scripts could take a argument.

 

It could cut down on the number of scripts needed.

 

For example:

A GenAccept script could be reused on both an Accept and Reject action if it could take a bool argument.

 

GenAccept(true)

GenAccept(false)  (negate output)

 

Allowing it to take an integer would make it even more flexible.

Status: Comments Requested

Hello plmadmin,

 

I’m not sure I fully understand this request to have condition and validation scripts accept arguments.  Condition and Validation scripts currently get predefined parameters such as dmsID, userID, transID, and customTransID.  In addition, Library scripts can be imported into a Condition or Validation script that allows reuse functions (which include parameters) across many scripts.

 

In your example of GenAccept(true/false) for a Validation script, a Library script could be created to return an empty list or a list that could contain a canned error message:

 

Library Script:  GenAccept

 

function genAccept(hasValidationError){

                var messages = [];
                if(hasValidationError === true){
                                messages.push(Canned error message here');
                }
                return(messages);
}

 

Validation Script:  testMyValues     Import:  GenAccept

returnValue(genAccept( item.SOMEFIELD === null ));

 

In this case, the generic function (genAccept()) can be used to provide a canned message as the returnValue for one or many validation upon the condition that results in true/false.  This behavior is standard in PLM 360’s scripting engine. 

 

Is this helpful, or have I missed the point of the enhancement you’re requesting?

 

Thanks,

 

-Jared  

6 Kudos
Asingh5

Item Preview Enhancment

Status: Comments Requested
by Contributor Asingh5 ‎11-06-2012 08:22 AM - edited ‎11-06-2012 08: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.

 

Untitled.png

Status: Comments Requested
Great Idea, I've seen some mockups that are very similar to this idea!
4 Kudos
dkeeley

Item validation scripts

Status: Comments Requested
by Mentor on ‎04-13-2013 04:53 AM

Hi Guys,

 

It would be great if we could run validation scripts on items when they are being created or edited.

 

Thanks,

 

David.

Status: Comments Requested
Great idea!
6 Kudos

In the PM tab there are a predefined set of columns. I want to be able to add/remove etc. columns and have them display meta data from linked items.

 

If I can do that I wont need to switch back and forth between workspaces and tabs to get the data I need to manage my project.

 

Anytime I can keep from bouncing around the tennant is time saved and goes towards reducing the perception that using a spread is better (because of less bouncing around).

Status: Accepted
4 Kudos

When I use the create relationship tool, and choose Create New, I've already selected the destination workspace.  So the create new dialog should be set to this workspace.

Submit Your Ideas

Share and shape product ideas.

New Idea
You are not logged in.

Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register

Announcements
IdeaStation Guidelines
Review guidelines and best practices
before posting a new idea


PLM 360 Survey