stevend17's Profile
Agile Professional
319
Points

Questions
8

Answers
42

  • Agile Professional Asked 5 days ago in ERP integration.

    I see you never got a response to this. We moved to a product called DocState by ZeroWaitState.  They had to make a customized solution for us, but by now they should have plenty of practice getting it right.

    Steve L.

    • 153 views
    • 1 answers
    • 0 votes
  • Agile Professional Asked on January 4, 2022 in Product Collaboration.

    Here’s something else that may interest you.  While I’m not sure about your particular version of Agile, you should be able to configure such that common files open in their native apps (xlsx in Excel, docx in Word, etc.  In the Java client Admin screen, navigate to System Settings | Viewers and File. Then click on the File Association tab.  For each file type that you want the user to open in the native desktop app, simply uncheck the 2 boxes.  You can actually delete the file type entry if you wish.

    Clicking on the attachment link on an object will now force a copy of the file to be downloaded to the user’s PC and open in an app they have associated with that file type.

    Hope that helps,

    Steve

    • 172 views
    • 2 answers
    • 0 votes
  • Agile Professional Asked on January 4, 2022 in Product Collaboration.

    See Oracle’s article on this topic:
    AutoVue for Agile 21.0.1 (JNLP) Not Working Behind Proxy Server Using SSL (Doc ID 2262454.1)

    • 172 views
    • 2 answers
    • 0 votes
  • Agile Professional Asked on January 4, 2022 in Product Collaboration.

    I’m not sure what your end goal is, but if you use Sites, rather than just one Common BOM, then an item can have multiple BOMs. Within our company we have multiple organizations. Each is represented by a site.  Typically, we keep the BOMs in sync between the orgs, but that is not to say that they couldn’t be different.  Do you already take advantage of site-specific BOMs?

    • 196 views
    • 2 answers
    • 0 votes
  • Agile Professional Asked on October 4, 2021 in Agile PLM (v9).

    Sabarish,

    If you want the user experience to feel more automatic, you might try trigger on status change, such as Pending to Submitted. It would likely have to be a “Pre” event rather than “Post”, depending on what types of redline changes are allowed in Submitted. If it had to be Post, you may have to give the PX permissions to make the changes.

    Steve

    • 576 views
    • 2 answers
    • 0 votes
  • Agile Professional Asked on October 4, 2021 in Agile PLM (v9).

    You may need something like this…

    IEventInfo req = obj.getPXEventInfo();

    IObjectEventInfo info=(IObjectEventInfo)req;
    IDataObject changeObj = info.getDataObject();
    IChange change=(IChange)changeObj;

    Hope that helps,

    Steve

    • 311 views
    • 1 answers
    • 0 votes
  • Agile Professional Asked on October 4, 2021 in Agile PLM (v9).

    Sabarish, I can’t speak for 9.3.6 because we’re still on 9.3.2. However, I suspect the behavior is similar.  Here’s what I observed…

    • I found a subclass that had a page 2 attribute with visible set to No.
    • I then went to parts page two and set visibility for that attribute to Yes.
    • I went back to the subclass and refreshed to see the attribute was now set to visible = Yes, which is what you were expecting.
    • Here’s the exception… If I now set visibility to No for that attribute on the subclass, and start the process again, it will NOT reset to Yes.
    • Meaning… I went back to the Page 2 settings on Parts, set visibility to No, Save it, then set to Yes again. It no longer sets to visible Yes on the subclass.

    The implication is that the visibility for the attribute at the subclass level must have been locked to No at one time in the past.  You might try another attribute or possibly check another subclass to see if you observe the same thing.

    Steve L.

    • 315 views
    • 1 answers
    • 0 votes
  • Agile Professional Asked on May 3, 2021 in Agile PLM (v9).

    Dear Agile PLM User,

    Here’s a query you may be able to use directly, or may be able to modify for your purposes.  Try running this query against a test part you just created, then again after placing the item onto an ECO.  Then release that ECO, and then place the item once more onto a new ECO that is not yet released. Check out the differences in the records. I hope this is helpful.

    SELECT I.ID ITEM_ID, I.Item_Number,
    r.old_revnumber,
    R.rev_number ,
    NVL(N1.Description, ‘Preliminary’) Lifecycle ,
    NVL(C.Change_Number,’N/A’) Change_Order ,
    NVL(N2.Description,’No ECO’) Co_Status,
    C.ID CHANGE_ID,
    C.RELEASE_DATE,
    R.Latest_Flag
    FROM Agile.Item I
    LEFT JOIN Agile.Rev R ON R.Item = I.Id AND r.site = 0
    LEFT JOIN Agile.Nodetable N1 ON R.Release_Type = N1.Id
    LEFT JOIN AGILE.CHANGE C ON R.CHANGE = C.ID
    LEFT JOIN AGILE.NODETABLE N2 ON C.STATUS = N2.ID
    WHERE i.item_number = ‘TEST-PART-NUMBER’;

    • 715 views
    • 1 answers
    • 0 votes
  • Agile Professional Asked on April 1, 2021 in Agile PLM (v9).

    Hi Alex,

    We’re still on 9.3.2 and our notification table currently hosts 4 different object types.

    ID            PARENTID     DESCRIPTION
    6000     5002                  Change Orders
    7000     5002                  Change Requests
    18022  5002                  Activities
    18451  5002                  discussions

    Steve

    • 561 views
    • 2 answers
    • 0 votes
  • Agile Professional Asked on April 1, 2021 in Product Collaboration.

    Madhu,

    My first thought is that I’m not sure you can make such a restriction based solely on permissions. It seems to me that you would need a process extension, possibly one triggered when the affected items table is updated, that would look for the criteria in question and provide validation to the user or simply remove the invalid item.  I realize that’s not a big help, but not sure how you can do this without customization. At our company, we created a configurable validation PX, which is used to validate many situations. In a case like this, it would initially allow the user to add the affected items, but would validate upon workflow change, and then return the workflow to a status of Error.   I’m hoping someone can provide a simpler solution for you.

    Steve

    • 687 views
    • 2 answers
    • 0 votes