dannypitt's Profile
Agile Angel
2404
points

Questions
4

Answers
133

Title Sr Oracle Agile PLM Analyst
Company Natures Sunshine Products
Agile Version 9.3.2
  • An admin could also just enable the relationships tab for the object type.

    – Java Client > Admin > Data Settings > Classes 
    – open appropriate object type (ECO or Discussions)
    – under “User Interface Tabs” Tab – open “Relationships”
    – set “Visible” to ‘Yes’

    • 54 views
    • 2 answers
    • 0 votes
  • Agile Angel Asked on June 20, 2018 in Product Collaboration.

    Hold and Cancel are special status types that are not visible unless you have the appropriate Change Status privilege(s).

    • 61 views
    • 2 answers
    • 0 votes
  • Agile Angel Asked on June 20, 2018 in Product Collaboration.

    This is configured in the Java Client under Admin > Server Settings > Database

    Notification Enabled: Yes (if set to ‘No’ all other email notification properties are ignored.)
    Mail From Domain: [domain for email notification] ex. yourdomain.com
    Mail From User: [the “from” email address for Agile email notifications] this needs to be a valid email address. ex. Agile@yourdomain.com
    Mail Server External: [name of computer running external email server]
    Mail Server Internal: [name of computer running internal email server]

    • 90 views
    • 2 answers
    • 0 votes
  • Agile Angel Asked on June 8, 2018 in Product Collaboration.

    I would recommend just modifying your discovery privileges/criteria to not include the obsolete parts that the users don’t want to see.  That way you don’t have to worry about unreleasing anything (which can be risky itself) in order to soft-delete nor would you be in risk of breaking any associations to workflows, change objects, etc…

    If there are some Obsolete parts they do want to see and some they don’t – you could just create some new page2 attribute that could be used to differentiate the two situations.  This could be used in your discovery criteria.  Something like Discover Valid Parts (Part Objects where Page 2 “Valid” is not “NO”).

    Once you have all of the invalid parts marked (which can be done via import if you leave it not change controlled) you can simply hide this attribute to avoid confusion and/or anyone marking items invalid that shouldn’t be.

    • 140 views
    • 4 answers
    • 0 votes
  • Agile Angel Asked on May 17, 2018 in Product Collaboration.

    You can import BOM and AML data at the same time by using the “Level Template” option after you select your source file in the import wizard.  The Import/Export User Guide lists required columns that your source file must contain in order for this to work and they do need to be exact.  You also need to make sure that all of the Manufacturer Objects already exist in the system (this can also be done through a separate import).

    Note – If you are trying to add AML data to existing RELEASED Items – you will need to create an ECO or MCO first and specify the change number as part of the import.  If the existing items aren’t yet released – you shouldn’t need a change to import the AMLs.

    Take a look at the “Using Templates to Import Data” section in Chapter 2 of the Import/Export User Guide.  It is pretty straight forward, but if you have any questions – just let us know.

    • 131 views
    • 2 answers
    • 0 votes
  • 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.

    • 147 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

    • 158 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.

    • 225 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.

    • 225 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.

    • 119 views
    • 3 answers
    • 0 votes