stortip's Profile
Agile User
81
Points

Questions
22

Answers
18

  • For those that are also interested in this problem here is a summary of what we have learned in the past year.

    Our problem was caused by a custom PX and manual procedures where the Declaration was incorrectly archived.  We are trying to fix errors outside of standard behavior in an administrative mode.

    First, some background.  PG&C was purchase and “shoehorned” into Agile.  It does not have the same standards or behaviors you might expect to find in “native” modules.

    Most significantly there is not an administrative role for PG&C where you can make changes outside of the business rules.  The result is that a released declaration is permanently locked within Agile.  You cannot edit: the state or workflow.  We also could not edit the Composition within the compliance tab of the part.  Even if we could do this it is unlikely to fix the problem because it would need to trigger the PG&C process to populate the declaration information (substances, etc.) on the compliance tab.

    This leaves directly changing the Oracle DB underlying Agile.  This would require reverse engineering the Tables either the WORKFLOW_PROCESS as Kevin suggests or finding the Part compliance table and changing that.  Kevin’s approach of adding a Manual Next Step is probably the safest.

    That being said, directly modifying the Oracle DB is a very risky proposition and not recommend.  You might say it voids the warranty.  We are not going down that road.

    The alternatives are:

    1. Current Declarations need to be recreated to fix the problem.
    2. We are replacing the custom PX and training users on correct procedures.
    3. Future: when creating new declarations you can use a modified worklfow that has a Manual Next Step from Release back to Review or Submitted.  This would allow for modification of the Declaration and re-release triggering the PG&C process for attaching it to the part.  [Note – have not tested this yet]

     

     

    This answer accepted by stortip. on September 18, 2019 Earned 15 points.

    • 1587 views
    • 4 answers
    • 0 votes
  • 9 months and no answer.  We have tried to add the Declaration number to the Part:Compliance:Composition:Composition attribute but have not had any success doing this.  Even if we do will Agile populate the rest of the information & Specifications from the Declaration.  Can anyone provide the logic or documentation on how the Declaration was originally added during the Supplier submission process.  Is there a way to re-release the declaration?

    • 1587 views
    • 4 answers
    • 0 votes
  • Agile User Asked on August 28, 2019 in Software Development Kit (API).

    Hi Karthik, this code does not display the message in the UI page, it writes to the log.  We need to display a notice to the user in real time on the page they are looking at.

    Any thoughts?

    • 1325 views
    • 2 answers
    • 0 votes
  • Agile User Asked on December 22, 2018 in Other APIs.

    The server had an data source error at start-up that caused the logs not to function.  The server was restarted and we were able to get log info.

    This answer accepted by stortip. on March 29, 2024 Earned 15 points.

    • 1782 views
    • 2 answers
    • 0 votes
  • Agile User Asked on December 20, 2018 in Other APIs.

    following are the screen shots for our log configuration.

     

    Step 1: Defined the logs in the PX as follows. the log statements were defined at various places in the code.

     

     

     

     

    Step 2: configuration changed in the log.xml located in the following location as follows.

     

    /u01/app/agile932/agileDomain/config/

     

     

     

     

     

     

    Step 3: still agile.log is not getting logs  defined at the PX at step1 and log file at the following location we are looking at.

     

    /u01/app/agile932/agileDomain/servers/tdev3wl201.toshibacommerce.com-AgileServer/logs/agile.log

    • 1782 views
    • 2 answers
    • 0 votes
  • I have not been able to resolve this yet.  The Declaration is automatically published by PG&C upon release.  Does anyone know how to access the code the does this publication, it is not associated with the workflow?    Is there a way to demote the declaration from release to review and then re-release it?  I tried changing the workflow Manual Next Step but this did not work for already released declarations.  The Declaration also does not have a revision so we cannot revise and re-release.  Is there something I’m missing?  Anyone have any other ideas?

    • 1512 views
    • 2 answers
    • 0 votes
  • Thanks, that explains the behavior we are seeing.  The 9.3.2 documentation does not describe it that way.

    • 1637 views
    • 2 answers
    • 0 votes
  • Agile User Asked on March 1, 2018 in Agile PLM (v9).

    This dependent on your company and industry but here are some rules of thumb
    1- How many approvers?  As few as possible: specific people should be addressed rather than groups, only those with RACE interests for the specific change and affected items should be included, approval assignment must be dynamic
    2- What functions?  Perform work, add content, review and coordinate changes, approve expenditures, resource assignments, risks.
    3- There should be different cycle times based on customer of market demand vs risk.  Provide shorter processes with more risk when approved by correct authority.

    • 1276 views
    • 2 answers
    • 0 votes
  • The issue was the Activites.Content.Autonumber attribute is include in Modify mask of Activities but not Projects.    We added a Modify Activities attrbiute in addition to the Modify Projects and it worked.

    • 1765 views
    • 2 answers
    • 0 votes
  • Correction: We added a Modify Activities PRIVILEGE in addition to the Modify Projects and it worked.

    This answer accepted by stortip. on March 29, 2024 Earned 15 points.

    • 1765 views
    • 2 answers
    • 0 votes