Matt Paulhus's Profile
Agile Expert
637
points

Questions
21

Answers
93

Item Master, Scripting events, Agile Administration Also used 9.3.4. at Crane Aerospace & Electronics, Redmond, WA
Title Configuration Analyst
Company FujiFilm Sonosite
Agile Version 9.3.3.
  • Agile Expert Asked 20 hours ago in Other APIs.

    You won’t be able to at this point.  When a user Creates a new Change Order (or Save As), the values in that pop up window are transient data – the new Change Order is not created yet and the information has not been sent to the database until the user clicks ‘Create’.  Therefore, no Pre-event script will get any data because there’s no ECO created yet.  

    You’ll have to work around this.  What I’ve done is create Post/Synchronous Script PX that defaults certain values on the Change Order based off of the user input.  You can also set up those same validation checks to trigger when someone submits their Change Order instead.

    Hope that helps.

    • 25 views
    • 2 answers
    • 0 votes
  • Agile Expert Asked 2 days ago in Product Collaboration.

    Two ways:

    1) see my own question from last year about it and create a simple SQL query using the User Usage History table.  Search for my “Auto-Inactivate Users” question on this site.

    2) run a User Usage Report and compare with a list of your active Agile users.  It’s one of the Admin reports.  

    Try that.

    • 49 views
    • 3 answers
    • 0 votes
  • Agile Expert Asked 3 days ago in Product Portfolio Management.

    I’ve used these two lines to calculate date difference:
    ROUND((LAST_UPD – CREATED),2) as DateDiff
    ROUND((select sysdate – interval ‘8’ hour – s.created from DUAL), 0) as elapsed

    I’ve ran into the same thing and I know what you’re talking about, so I used the second line to get the most accurate (I have to subtract 7 or 8 hours for Pacific Standard Time). 

    Make sure you check your server preferences to see if it’s counting weekends or not.

    • 30 views
    • 4 answers
    • 0 votes
  • Agile Expert Asked 3 days ago in Product Portfolio Management.

    I’d imagine it’s the sign SIGNOFF table and the same SQL as you would pull with other changes, though I don’t have PPM to confirm this.  Try it by: <select * from SIGNOFF s, ACTIVITY a where a.id = s.change_id> and go from there.

    • 30 views
    • 4 answers
    • 0 votes
  • I’m fairly confident you could at least read critiera.  There’s some info about that in the API SDK Agile Guide 

    INode criteriaLibrary = admin.getNode(NodeConstants.NODE_CRITERIA_LIBRARY); // Load the Criteria relevant to the query class (For example it is Items base class)
    ICriteria criteria = (ICriteria) criteriaLibrary.getChild(“All Released Items”);

    or this (both from the API user guide)

    IListLibrary library = m_admin.getListLibrary();
    INode lib = m_admin.getNode(NodeConstants.NODE_CRITERIA_LIBRARY);
    ICriteria criteria = (ICriteria)lib.getChild(“All Change Orders”);

    But there I’m not 100% sure you can fully flush out and read the query itself.

    • 35 views
    • 2 answers
    • 0 votes
  • Agile Expert Asked 5 days ago in Product Collaboration.

    Another suggestion is a PX/Script to do this – I’ve done something similar with User Groups.  Use an Extend Actions Menu script (drop down button on the Actions menu) to launch a query script that finds and returns all parts related to that supplier.

    • 39 views
    • 2 answers
    • 0 votes
  • Agile Expert Asked on April 11, 2018 in Product Collaboration.

    I did just get this to work with two Page 2 fields:  
     – first, add the applicable role in an active “Enforce Field Level Read” privilege.  This will hide any field that users do not have specific read access to read.  Your default settings will probably hide any newly created flex field as users probably have read access right now to everything else.  Make sure you test this as any field this role had read access to to ensure Agile didn’t hide any needed fields. 
     – go through your read accesses and strip read access on your Page 3 field.  Make sure you do this on all Class levels (like Items, Documents, subclass, etc.)
     – create a criteria where Page Two field = “yes” or not null or whatever you need it to be
     – create a new Read access with the new Criteria.  In the Applied To field, add your Page 3 field.  
     – enable this new Read access to the specific User Role (add the role from step 1 to the Privilege’s where-used tab)

    And done – I got this to work so that as soon as I updated a Page 2 field to Yes and hit ‘Save’, Agile revealed the fields.  Once I edited for “No”, Agile hid those fields and saved any data stored.  Pretty cool.  Biggest thing was how powerful “Enforce Field Level Read” privilege can be – make sure you do lots of testing to ensure Agile didn’t hide any necessary fields.

    • 130 views
    • 3 answers
    • 0 votes
  • Agile Expert Asked on April 11, 2018 in Other APIs.

    So you need the available list values, correct (and i.e., not the specific value on a particular Part or Document)?  You need the IListLibrary and IAdminList dataobjects and set of methods.  I’ve never done a Cascade List specifically, but there’s a section about it in the Agile 9.3.X SDK Developer Guide – User APIs.

    • 41 views
    • 3 answers
    • 0 votes
  • Agile Expert Asked on April 11, 2018 in Other APIs.

    Did the obj.getValuebyAttId() not work for you?  Instead of ItemConstants, try the Base ID value instead or even the IItem.getValue() method instead.  I’ve had trouble with Page Three fields before too, so I tend to use the Base ID instead.  
    Try CommonConstants as well too.

    • 41 views
    • 3 answers
    • 0 votes
  • Agile Expert Asked on April 10, 2018 in Other APIs.

    Thanks – yes, I found that scripts in Queued status end up working their way out after application refreshes (and I currently have no scripts in “Queued” status).

    • 83 views
    • 2 answers
    • 0 votes