dannypitt's Profile
Agile Angel
2339
points

Questions
4

Answers
128

Title Sr Oracle Agile PLM Analyst
Company Natures Sunshine Products
Agile Version 9.3.2
  • No, not without some extra process extension/validation as modify rights for attributes allow users to add to and remove from any of the “Applied to” fields. 

    As a workaround – you could split each of them into two separate attributes that use the same list (“List1” and “List2”, for example) and create a modify privilege for these users that only allows them to modify “List2″ and only IF “List1″ is already populated.

    • 60 views
    • 1 answers
    • 0 votes
  • Unfortunately change objects cannot be imported.  You can import affected items onto an existing change object, but cannot import the change object itself.

    The objects that can be imported into the PC module are:
    – Item
    – Manufacturer
    – Manufacturer Part
    – Part Group

    • 86 views
    • 1 answers
    • 0 votes
  • Agile Angel Asked on March 30, 2018 in Product Collaboration.

    Yes, for the Criteria you would use whichever object type is applicable and the Page Two.Multilist attribute that you use for “Access Control”. 

    The $USERGROUP variable should be available if the attribute selected for your criteria uses the “User Groups” list.

    • 185 views
    • 7 answers
    • 0 votes
  • Agile Angel Asked on March 28, 2018 in Product Collaboration.

    If I understand correctly – You only want members of User Group A to be able to discover certain ECOs and BOMs and User Group B to discover OTHER specific ECOs and BOMs.
    If this is the case – there needs to be some specific criteria on which to base the discovery privilege(s).

    This can be achieved using a Page Two MultiList “Access Control” attribute that uses the User Group list.  That way you can create your limited/restricted discovery criteria and privilege based on this field. 

    The idea is to only allow the logged in user to find objects that contain their User Group(s) in the access control field.  The bonus here is that you don’t have to build out separate criteria for each usergroup as you can use the $USERGROUP variable.

    Example Criteria – “ECOs for my Group” (ECOs Page Two.Access Control Contains $USERGROUP)
    Discovery Privilege – (using above criteria) “Discover ECOs for My Group”

    The same privilege can be given to both User Groups and will only give them access to the ECOs that contain their User Group(s) in the Access Control field.

    This answer accepted by sommaip. on March 29, 2018 Earned 15 points.

    • 185 views
    • 7 answers
    • 0 votes
  • Agile Angel Asked on January 22, 2018 in Agile PLM (v9).

    I think you’ll be better off pursuing a fix to why your Workflow Routings aren’t being displayed correctly in the first place.

    There isn’t a way to configure this in an advanced search dashboard to function the same as it should in Workflow Routings as evidenced by the Workflow Routings saved search “All Changes Transferred to Me”. If you execute this search and then click the top bar to show the search controls – it states “The Criteria for this search cannot be displayed”.  This indicates that it is a hard coded query rather than one created through the user accessible search criteria.

    This answer accepted by chlin2828. on January 25, 2018 Earned 15 points.

    • 97 views
    • 3 answers
    • 0 votes
  • Agile Angel Asked on January 22, 2018 in Agile PLM (v9).

    Changes – Object Search
    [ WorkflowWorkflow StatusEqual To$CURRENTSTATUS – AND
    WorkflowApprover ContainsUser who transferred authority to you – AND
    WorkflowApprover Action Equal ToAwaiting Approval ]

    • 97 views
    • 3 answers
    • 0 votes
  • Agile Angel Asked on November 28, 2017 in Engineering Collaboration.

    You could change the  ‘Allow Escalation Designation Approval’  property to “After Escalation” (instead of “Always”). 

    That way – as long as the escalation user approves the change BEFORE the escalation period has been reached – the check box would only be selected for their own account.

    If the escalation user waits until AFTER the escalation period – you’ll have the same issue, but hopefully that isn’t a regular occurrence.

    • 147 views
    • 2 answers
    • 0 votes
  • Is this happening in all browsers?  There are known issues with IE 11 – especially when the user has set the browser to remember their password.
    Might want to try using Chrome or Firefox just to confirm whether or not this is the issue.

    • 159 views
    • 3 answers
    • 0 votes
  • The ‘Signoff User Dual Identification Type’ preference (Java Client > Admin > Server Settings > Preferences) needs to be set.  It is set to “N/A” by default which disables dual identification.  This preference determines what additional identifier will be required (User ID or Login Password) if/when the ‘Dual Identification Required’ property is set to Yes on a particular workflow status.

    If set to “User ID” – the ‘Display User ID’ Preference should be set to “NO”
    If set to “Login Password” – Every User’s ‘Use Login Password for Approval’ property MUST be set to “NO”.

    • 159 views
    • 3 answers
    • 0 votes
  • You can add the attachment’s Smart URL to the EBS record as a URL attachment.
    To make sure the Smart URL directs you to the latest released version of the attachment – just delete the Rev and change number portion from the generated URL.

    Also depending on your Smart Rule settings – you may want to remove the File Folder portion of the URL as well.  It just depends whether the new rev uses the same file folder or not.

    • 237 views
    • 1 answers
    • 0 votes