cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Make Esoteric Values Available to Item Details and by Extension Computed Fields

Make Esoteric Values Available to Item Details and by Extension Computed Fields

I would find computed fields more useful if I could access more fields than just what are available on the Item Details tab.  Pretty much if it is available to a workspace view then it should be available to a computed field as well.  This would allow for contextual formatting and dynamic text entry in the Item Details based on information not currently available.  At present doing more complicated scripting is the only way to access this information.

 

1. Lifecycle information values such as "Is Latest Version", "Version Number", "Release Letter", "Lifecycle", etc.

 

2. Values from the Owner and Change Summary section such as "Owner", "Created on", "Last Modified by", etc.

 

3. Record identification information like DMS ID and Workspace ID.

 

4. User and group information of logged in user which could allow for highlighting and formatting based on this.

 

Referencing could be done the same as from the scripting side of things, like "item.descriptor.createdBy", "item.descriptor.descriptor", "item.master.workspaceID", etc.

 

Alternatively, all of this information could be held in pre-populated, dynamically updated reserved fields that are available just as any user-defined field is, but not editable.  If this were the case the computed fields functionality wouldn't need to change as it would then have these fields to choose from.  In addition, these values could be displayed as needed amongst the Item Details.

 

Thanks!

 

Joe Hendrickson

5 Comments
gasevsm
Alumni
Hi Joe, Thanks for your submission. Kindly share how you intend to go about contextual formatting if this is provided in the product, be it by computed fields or otherwise. I'm also curious about your use cases around dynamic text entries. What do you mean by this precisely? Thanks in advance,
Anonymous
Not applicable

Dynamic Text Entry:

What I meant by this was having fields on the Item Details tab automatically update as things about the record change, which is basically the definition of computed fields.  I'm looking for the ability to have fields that update as the lifecycle changes or as a revisioning workflow advances.  But I think I captured my real request at the end which is to have all of these values available in fields on the Item Details tab, hence dynamic values as they would automatically update as lifecycles change, workflows advance, owners change, etc, without need for transition-based or on demand scripting.

 

 

Contextual Formatting:

a. If the user was not the last person to modify a record then show a yellow indicator

b. If a revision is Superseded then show a red indicator towards the top of the record.

c. If a revision is Released then show a green indicator; yellow for Obsolete, etc

d. If various fields are blank and the user is a member of an indicated group then show a red indicator

 

 

Joe Hendrickson

 

nguyentru
Alumni
Status changed to: Future Consideration

Hi Joe,

 

We appreciate you taking time to submit this idea and help provide additional information.

 

While we can't promise that your ideas will be implemented, we will be sure that our product development team receives your submission.  

 

We will add this to our future enhancement list.

 

Thank you,

 

Trung

benderk
Autodesk
Thank you for submitting your idea. Have you tried the Modern Interface lately? We request that you review your idea in the context of the Modern interface. If your idea is not addressed, we invite you to create a new Idea in the context of Modern so that it can be addressed accordingly. Sincerely, Keri Bender | Global GTM Business Strategy Manager, Product Lifecycle Management
benderk
Autodesk
Status changed to: Archived
 

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea