New Idea
11 Kudos
piggeej

More robust editor for Advance Print View

Status: Accepted
by Product Support on ‎04-17-2014 09:53 AM

It would be great and useful to have a more robust Advance Print view edtior, that included Tabs for full html editing, along with an attached CSS editor.

 

Example:

Tab one: current editor with ablity to add elements 

Tab two: Full html editor

Tab three: CSS editor

Tab four: Preview of edits not based on dmsID for layout views (color background etc...)

Status: Accepted
Hi piggeej, We appreciate you submitting your ideas and suggestions to us. We will add this to our feature list. Thank you, Trung
6 Kudos

We need the ability to import and export javascripts (condition, validation, library etc.) directly from a PLM tenant instead of copying it manually into a notepad.

 

This is a good feature and will be helpful in deploying codes in multiple environments.

 

Also a revision control (software configuration management) on these javascript will be a great addition.

 

Thanks,

 

Deepak

Status: Accepted
22 Kudos
obourne

Run Script by Push Button

Status: Accepted
by Distinguished Contributor obourne on ‎02-21-2013 01:55 PM

I'd like the ability to run a script by pushing abutton in the workspace item and not have to rely upon a state transition to do so. There are times where I want to create an item but use data from an existing item (the one I'm in at that time) and then link them together via the relationships tab. I want to do this without a state change (because state change would not be needed to simply link to items). I realize I can change behaviors to run a script upon creation that could do much of the same. It just makes sense to NOT to have to navigate away from where I'm at and then remeber what I want to link to. I'm all about automation.

Status: Accepted
2 Kudos

I feel we need a lookup function in the scripting functions

 

The basic Idea would be to duplicate the current function for linked picklists and leverage the benifits of derived fields and filtered picklists.

 

The script function would simply return a dmsid's or null and be able to search a specified workspace for records that match specified field/values. The return could be an array of the dmsid that could be utilized to then load the found dmsid for use in scripting access to that record for adding or extracting information.

 

Example:

 

Workspace A = tasks with two fields to identify that record: Project# (Linked Picklist) and Task ID, A third field Task Type, UDP of values (type a, type b etc.)

 

On Workspace B you have two filtered picklists based on Workspace A (you could use Pre-Filter on the Picklist to restrict by Type).

 

Use the values selected in the filtered picklist fields in a script lookup function that returns all matching dmsID from WS-A.

 

Using looping & load item you can then process those id's to add or extract info.

 

There have been several support forum discussions on this subject and thought it needed to be added to the Idea Station. Help this along by giving Kudos.

 

Support forum discussions:

 

http://forums.autodesk.com/t5/PLM-360-General/Script-for-iterating-through-all-items-in-a-workspace/...

http://forums.autodesk.com/t5/PLM-360-General/Getting-Source-Record-info-from-Filtered-Picklist-fiel...

http://forums.autodesk.com/t5/PLM-360-General/Filtered-Picklist-Scripting-Access-No-longer-available...

 

 

Thanks

 

Bob Donovan

Bigge Power Contructors

 

 

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

Hi,

 

because of lack abilities in REST API it would be nice to execute script through REST API.

 

Algorithm:

1. Administrator creates actions script.

2. User logins to PLM360 with REST API.

3. Code of integration tool sends command to PLM360. For example, "ExecuteScript". Additionally can be defined ItemID, WorkspaceID, etc as arguments of function.

 

Currently, the workaround I will use is execution of script on create or update events of item.

 

Best regards, Vladimir

Status: Future Consideration
Hi Vladimir, We appreciate you submitting this request. We will add this to our future enhancement list. Thank you, Trung
7 Kudos
jonas.andersson

Desktop folders

Status: Future Consideration
by Contributor jonas.andersson on ‎02-13-2013 03:45 AM

A function where a "desktop folder" can be added inorder to add/view documents from the desktop/finder directly into PLM360. The folder to be added should be connected to a certain workspace, where the user can chose which workspaces should be able to "share" information. 

 

The folder should be a direct connection through the username and password from the user, where permissions should be added depending on what role the user has.

 

Similar to dropbox, but with the added finess of PLM360.

 

Kind regards,

Jonas

 

Status: Future Consideration
Jonas, interest idea. I don't think is something we'll address right away, but let's come back to this in the future
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  

4 Kudos
cruzj

​ Default filters in a picklist

Status: Duplicate
by cruzj on ‎06-05-2013 10:43 AM
We would like to be able to narrow down a linked picklist for a certain criteria.

Example: We use Product ID as a unique identifier for products. In other workflows, we will link a picklist of Product IDs to a form so that we can assign more attributes to the product. Product ID  can have a status of "Assigned," "Orderable" or "Retired." We would like to pre-filter a picklist of products to show only those that are in status "Assigned" but not "Orderable" state. There is no current client-side scripting available today.

Only possible by "chaining" workspaces. Create a new picklist when the item changes status, e.g., when a Product ID is first released, spawn record in another workspace with the narrowed-down population of "Assigned." .

Status: Duplicate
4 Kudos
cruzj

Checkboxes in form - Select All

Status: Accepted
by cruzj on ‎06-03-2013 04:46 PM

We would like the ability to create a series of checkboxes and Select All and deselect all with a single click.

Status: Accepted
This is an interesting request. The only place I can see using this feature is the grid tab or BOM Tab In the item details tab, each fields are individually separate and form through the use of the matrix. Please provide more information and details. thanks
9 Kudos
pmaxted1

Scripting Access to Relationships Tab

Status: Duplicate
by pmaxted1 ‎08-02-2012 12:23 PM - edited ‎08-02-2012 12:25 PM

It is often both difficult and tedious to manually create relationships between different workspace items (as the picture below illustrates). It would save a lot of time to be able to write scripts to automatically add relationships between workspace items. 

 

Even tying the ability to add relationships into the function createItem('WS_WORKSPACE_ID') would be a huge time saver.

 

 

 

Item Relationships

Status: Duplicate

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