New Idea
2 Kudos

Increase​ Item descriptors

Status: Comments Requested
by cruzj on ‎06-04-2013 04:00 PM
When a user uses a filter, there are only 4 item descriptors available.
 
Key identifiers for product data take up at least 3 descriptors automatically 
1) Product ID
2) Product Name
3) Item status - represents different states of an item (e.g., Assigned, Orderable, Retired)

It would be useful to have additional descriptors in case addtional attributes are needed such as Release, Platform or Deployment, Effectivity dates, for example.
Status: Comments Requested
Hi cruzj, I'm not really understanding the use case for this request. Currently the descriptor pulls the information from fields in the Item Details. Some of our revision controllled workspace, have their own indicators, for Lifecylce, Revision Letter, Effective Date. The more you add to the descriptor, the longer the name of the record. Please help me understand the need for this request thank you, Trung
2 Kudos
We use BOMs to show data hierarchies.
Example hierarchy:
  • Pricing - which is a parent of
  • Offering - which is a parent of
  • Release - which is a parent of
  • Product Line Code - which is the lowest level of child
Can we do a validation from a field in a Parent item details form to a child BOM?
The Pricing form has a field to display Product name and show some derived fields that are used in a pricing calculations. Can we ensure that somewhere down the chain of BOMs, that the same Product is added as a child? 

The validation logic may possibly only be done on a workflow transition.


2 Kudos

Our team used BOMs to create data hierarchies.

For example, Pricing has a child Offering, which has a child Release, which has a child PLC (Product Line Code).

When a user selects a BOM in Pricing, can the user see the down the relationships to Offering, Release and PLC?

4 Kudos

Item Preview Enhancment

Status: Accepted
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: Accepted
Great Idea, I've seen some mockups that are very similar to this idea!
3 Kudos

Derived grid field values

Status: Accepted
by Mentor on ‎10-31-2012 02:54 PM

Hi,

 

It would be useful to be able to create derived values on new items from grid field values on other items.

 

David.

Status: Accepted
1 Kudo

Pivot value update

Status: Accepted
by Active Contributor adminplm360 on ‎06-18-2013 08:21 AM

If I change the pivot value in Work Space A is not updated in Work Space B until I actually change the derived field  into another value. The derived field will change but the pivot wont.

 

I would like that the pivot value updates as the derived value does

 

Attached is how is happening right now.

 

 

Status: Accepted
This is part of the feature spec for derived fields, that is to provide options on how changes propagate. The currently functionality is defined that updates are only performed on explicit update/edit by the user. There are plans to add additional functionality to allow updates to propagate without user action. I'll add this idea Station request to our feature requirements to make sure this behavior is covered correctly.
3 Kudos

In the relationships tab, the cross-referenced items are listed under the column: Item, Current State, Type of Relationship, and Description. It would be nice to identify which workspaces the items are originated since the items might be cross-referenced from multiple workspaces.

 

e.g. certain item in [WS]Products might be related to items from [WS]Tests and [WS]Calculations. It would be nice to identify the items are either from [WS]Tests or [WS]Calcuations by adding another column called Workspace or Category.

 

Thanks,

Frank

Status: Accepted
1 Kudo
scottmoyse

Add Item Details on the BOM tab

Status: Duplicate
by *Expert Elite* on ‎10-07-2012 01:29 PM

We should be able to add Item Detail fields to the BOM tab. I would love to see that functionality soon.

0 Kudos

Presently, I can create a picklist which can link me to an item in another (or the same workspace).  But there is no way for me to see that relationship from the other side.

 

There is some abiltiy to do this using the BoM and Relationships.  But BoM is a very specific relationship model, and Relationships are too generic.

 

I would like the ability to add a field type on the "linked" object that references the linking object.  The field could be read-only, as I mostly want it for reporting.

 

For instance, if I have an "Inspection" that has a field "Inspected Item" that references an "Item", I'd like to put a "inspections" field on the "Item" workspace that shows me all the inspections. This item has been included in.

 

Eventually, I can see this being enhance to support:

  • editing the relationship from the "linked" side
  • Showing fields other than the description (a mini-grid) for instance in this case, I'd really like to see the "status" of the inspection.

 

Status: Accepted
HI Mark, I will add this to our feature list. thanks, Trung
0 Kudos

Currently the Multiselect Picklist type is only available for the Item Details & Grid Tabs.

 

Not only would it standardize the picklist types across the tabs but give added functionality to use those tabs.

 

An Example would be for the RFQ workspace.

 

You have a list of parts that are added to the managed items tab from multiple workspaces (electrical parts, hydraulic parts etc.). You can have a multiselect picklist for each row that lists the vendors you would want to have quote on those parts. Your workflow would be:

Create Master RFQ -> Define parts & Vendors (managed Items) -> Request Quote (Spawn new RFQ's for each vendor selected in the multiselect picklist)

 

Currently this is possible in the grid tab, but the item field can only pull from one workspace whereas the managed items tab can pull from multiple based on the relationships defined.

 

BD

Status: Accepted

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