- Collapse View
- Expand View
- Mark all as New
- Mark all as Read
- Float this IdeaStation to the Top
- Subscribe
- Bookmark
- Subscribe to RSS Feed
- Invite a Friend
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.
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
Hi Guys,
It would be great if we could run validation scripts on items when they are being created or edited.
Thanks,
David.
Hi Guys,
I would be extremely benefitial if I could run a script automatically immediatley after an item has been created. It could be used to automatically create relationships after a user has created an item.
Thanks,
David.
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
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.
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.
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()
I'd love to see more robust script management. Ideally I'd like to see the ability to officially version or rev scripts. In addition to the Save button, you could add a button for Version. This would store the script in its current state with the appropriate verison number.
In addition, I'd like to review previous versions of the script and have the option of making a previous version the current version.
I'd love to have the ability within a script to determine if the script is running in response to another script, or if it's running in response to user input.
If I could have a conditional like:
if(this.CalledByScript)
{
println("I was called by another script!");
}
I'd be one happy camper. Better yet, this.CallingScript - null if not called by script, otherwise contains the name of the calling script. That would make me a happy camper with a cooler full of my favorite beverage.
The Change Log for records shows an icon for actions initiated by script. I wonder if this is something that's available and just not documented?
Adding Project Management items in the Project Management tab is tedious at times. Being able to add project items through scripting would allow an automated procedure involving less time consumption and tedious routine work.
