Quality

Get Involved. Join the Conversation.

Comments

  • Ringo Shakya

    Rule based approval is currently not supported in Quality. It is in the future roadmap.

     

    Thanks,

    Ringo

  • Sachi Mohanty

    Please see uploaded screenshot

  • Sachi Mohanty
  • Gayle Hayes

    Hi Gru2017

    These subject areas can be located by searching for Quality or scrolling to "Enterprise Quality Actions Real Time" and "Enterprise Quality Issues Real Time". 

    Custom attributes are supported. 

    Please note that in 19B we have extended the definition of quality issues and quality actions with additional date, text, and number extensible attributes in Application Composer.  OTBI coverage for these additional extensible attributes  will be available in 19C.  This enhancement brings the total count of extensible attributes to: 

    –350 Text, Checkbox, Choice list fields
    –200 Number, Currency, % fields
    –50 Date, Datetime fields
    –25 Longtext fields
     
    best regards,
    Gayle
     
  • Melanie Grosser

    Hi Shylaja,

    Unfortunately, there is nothing that can be done at this time from a software/setup perspective to segregate the create and approval responsibilities.  The same privilege secures both the create and update (including approval) functions.  For now, it will have to be a user procedure.

    There is a future enhancement to enable E-Signatures and E-Records for Inspection Plans, which will be provide the ability that you are looking for.

    Regards,

    Melanie

  • Elaine Wan

    In addition to Gayle's response, generating a Device History Record (DHR) based on a manufacturing work order and its transactions is planned for future roadmap. If you have any further questions, please let us know.

    Best regards,
    Elaine
    elaine.wan@oracle.com

  • Gayle Hayes

    Hi Sachi,

    Thank you for your inquiry.   Traditionally we have had multiple partners provide solutions to customers for eMDR.  Inspirage has advised that they could assist with your request.  If you require contact info, please reach out to me at gayle.hayes@oracle.com and I'll make the introduction.

    best regards,

    Gayle

     

     

  • Andre Guldi

    This is how it works; you can get the oldValue in an attribute trigger, but not object trigger, see here:

    https://docs.oracle.com/en/cloud/saas/engagement/19a/cgsac/groovy-tips-and-techniques.html#to_referencing_original_values_of_changed_fields

  • Shylaja Shetty

    Thankyou.


    The fact we can't get oldValue in pre-update trigger is wanted or is it a bug?
    Is there a way to get oldValue and newValue in pre-update trigger (without using field validation rules)?
    Is possible to get oldValue and newValue in other Application Composer functionalities (for example triggers, functions, ...)?

  • Andre Guldi

    Hi Shylaja

    doSomething could be an Object Function. Go to Apps Composer -> Standard Objects -> Quality Issue -> Server Scripts -> Object Functions.

    oldValue and newValue could be parameters (of that Function) of type String.

    Regards
    André

     

  • Shylaja Shetty

    Hello Andre,

     

     

    Thankyou for the update.

    thank you, now we'll try to use oldValue and newValue and I'll let you know

    where can I insert/write doSomething function/procedure?

     

     

    Regards,

    Shylaja

  • Andre Guldi

    Using an object level pre-update trigger does not get you the old value, it only gets the new value.

    You can create a field validation rule, which provides both. oldValue and newValue are keywords there.
    From there you can call another function e.g.

    if (oldValue != newValue)
      doSomething(oldValue, newValue);
    println ("old : "+oldValue+" new : "+newValue);
    return true;

     

  • Shylaja Shetty

    Hello Team,

     

    Can we have an update on this.

     

    Regards,

    Shylaja

  • Elaine Wan

    Hi Marc,

    The REST service to manage inspection plans is available in 18C, so it should be able to help with this requirement to update the inspection plan status.

    Regards,
    Elaine

  • Elaine Wan

    Hi Vishal,

    Oracle Quality Management Cloud is designed to work with the rest of the Oracle Supply Chain Management Cloud applications, specifically complementing the product design and execution processes.  In order to integrate with Quality Management Cloud, you would need to synchronize master data, such as organizations, items, suppliers, customers, and possibly subinventories/locators, before defining inspection plans that map to the different types of inspection.  There are REST services to create/update inspection plans and enter inspection results.  See the REST API documentation for more information: https://docs.oracle.com/en/cloud/saas/supply-chain-management/19a/fasrp/index.html.