Improve Scripting List functionality

[AstroRossD]

Currently the Scripting list has only four headings:

• Unique Name
• Description
• Action (Edit/Delete)
• Where Used

Following on from existing requests for version control on scripts, it would be beneficial to have the ability to sort and filter the list using these, plus some additional columns:

• Last Edited (date and time)
• Last Edited by (User)
• Where Used (list presented on screen rather than a link, complete with transition number where applicable)
• Where Used Type (creation/transition/on demand/on edit)
• Where Used Transitions (clicking on or hovering over this could display a preview of the relevant workflow map/s)
• Where Used Workspace
• Script Type (Action, Condition, Validation, Library)
• Error Log

This could be done in the same way as Views within the workspaces, then views could be created and customised according to need.

Additionally, it would be useful to prevent edit access to a script if it is already being edited by another user - version control would go some way to solving this...

[Anonymous]

Agree with these suggestions would make the script view more functional for the Admins here is one for the users:

With the introduction of on demand scripts adding an additional field in the script definition - User Display Name would make that function more user friendly. Having the message to confirm the on demand script only have the script name makes it confusing to the user. But nameing a script so the user understands what action they are about to perform makes if hard to use standard script naming conventions for the programmers.

BD

[gasevsm]

Yes will be making investment this year towards improving this area to standardize and improve the user experience. Cheers for logging the idea.

[nguyentru]

Hi AstroRossD,

Congratulations!!!

You idea had been accpeted.

We will add this to our feature list and work on getting this idea in our future release.

Thank you,

Trung

[giliar.defriesperez]

Thank you for submitting your idea. The timing isn't quite right for this to be a priority for development consideration. As such, we will put this on the back-burner to revisit at a later date in the context of Modern. Please continue to comment and add your support.

Giliar Perez
Product Owner - Fusion Lifecycle
Autodesk Canada Inc.

[AstroRossD]

Hi @giliar.defriesperez

I'm sure we beaten down admins can survive on scraps a little longer 

Thanks for the update!

[benderk]

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]

Hello -

Thank you for your input on this issue. You are correct that this should be considered in the Modern Interface. We will move it to Future Consideration to review.

Your input and feedback is very appreciated.

Sincerely,
Keri Bender | Global GTM Business Strategy Manager, Product Lifecycle Management

[loic_guilloux_GE]

Hi,

I have similar and/or addional requests....

https://forums.autodesk.com/t5/fusion-360-manage-ideas/improve-scripting-environment/idi-p/10977222