Oracle Manufacturing Cloud
What's New
  1. JUNE MAINTENANCE PACK FOR 19A
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Manufacturing
        1. Search for Work Definitions Based on Item Effectivity Using ADFDI
  1. Update 19A
  1. Revision History
  2. Overview
  3. Optional Uptake of New Features (Opt In)
  4. Feature Summary
    1. User Interface
        1. Access Work Areas in Reorganized Navigator Groups and Group Icons
    2. Manufacturing
        1. Create Object Composition and Where-Used Reports for Genealogy Using OTBI
        2. Deactivate a Work Definition
        3. Integrate with External Systems Using Additional Work Definition REST Services
        4. Manually Procure Materials for Work Orders
        5. Perform Ad Hoc WIP Inspection from Dispatch List
    3. Quality Management
        1. Create Issue or Action from an Item in Product Development
        2. Search Across Product Hub Organizations to Add Items as Affected Objects on Issues and Actions
        3. Associate Resource Instances and Add Serial or Lot Numbers to Affected Items Using REST Services
        4. Use Save-As Action to Carry Forward Attachments and Affected Objects
        5. View Creator and Assignee on Security Tab

June Maintenance Pack for 19A

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
21 JUN 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.


Customer Action Required = You MUST take action before these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Customer Action Required

Manufacturing

Search for Work Definitions Based on Item Effectivity Using ADFDI

Manufacturing

Search for Work Definitions Based on Item Effectivity Using ADFDI

Today a manufacturing engineer can search for work definition operation items based on a specified work definition as of date that corresponds to a work definition version in the Application Development Framework Desktop Integration (ADFdi) spreadsheet. The search results return all of the item structure components and assigned operation items that are effective within the start and end dates of the work definition version.  As a result, it is challenging to distinguish the past, current, and future states of the work definition on a specific date.

With this update, you can search for work definition operation items and further restrict the search results based on the past, current, and future, or current, or current and future date effectivity as of the current date, or a specified work definition as of date. This search filter can expedite the identification of new or updated components that may have been implemented through a change order. You can also display past, current, and future effective components to coordinate their assignment to a work definition operation by looking at their operation sequences and material sequences within an operation.

Searching for work definitions based on the date effectivity of operation items in ADFdi helps you quickly identify the components assigned and unassigned to operations to facilitate change management scenarios, and verify work definition setups for accurate work order creation.

The new Display Effectivity search field is available in the following worksheets: Operation Items - Standard, Operation Items - ATO Model, and Operation Items- Multilevel ATO. The following is a screenshot of the Operation Items- Multilevel ATO worksheet in which a new Display Effectivity search field is available with 3 effectivity options:

Search Field Display Effectivity in ADFdi

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

If you don't specify work definition as-of date, the work definition version start date is used to determine what is past, current, and future effective. In this case, since the version start date is used to determine effectivity, you will not get past effective components.

Role Information

  • Privilege Name and Code:
    • Manage Work Definitions (WIS_MANAGE_WORK_DEFINITIONS_PRIV)
  • Job Role Name and Code:
    • Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)

Update 19A

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
27 MAR 2019 Perform Ad Hoc WIP Inspection from Dispatch List Updated document. Delivered feature in update 19A.
15 FEB 2019 Manually Procure Materials for Work Orders  Updated document. Revised feature information.
15 FEB 2019

Access Work Areas in Reorganized Navigator Groups and Group Icons

Updated document. Delivered feature in update 19A.

21 DEC 2018   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

Optional Uptake of New Features (Opt In)

We continue to add many new features to the Oracle Cloud Applications, and for some features, you can take advantage of new functionality at a pace that suits you by “opting in” to the feature when you’re ready. You can opt-in to a feature in two ways:  by using the New Features work area, or by using the Setup and Maintenance work area.

To opt-in using the New Features work area:

  1. Click the Navigator, and then click New Features (under the My Enterprise heading).
  2. On the New Features page, select the offering that includes new features you’d like to review.
  3. Click Opt-In for any feature that you want to opt-in to.
  4. On the Edit Features page, select the Enable option for the feature, and then click Done.

To opt-in using the Setup and Maintenance work area:

  1. Click the Navigator, and then click Setup and Maintenance.
  2. On the Setup page, select your offering, and then click Change Feature Opt-In.
  3. On the Opt-In page, click the Edit Features icon.
  4. On the Edit Features page, select the Enable option for any feature you want to opt-in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close
  5. Click Done.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.


Customer Action Required = You MUST take action before these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

New Features Delivered Ready to Use
(Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

New Features That Customer Must Take Action to Use (Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Customer Action Required

User Interface

Access Work Areas in Reorganized Navigator Groups and Group Icons

Manufacturing

Create Object Composition and Where-Used Reports for Genealogy Using OTBI

Deactivate a Work Definition

Integrate with External Systems Using Additional Work Definition REST Services

Manually Procure Materials for Work Orders

Perform Ad Hoc WIP Inspection from Dispatch List

Quality Management

Create Issue or Action from an Item in Product Development

Search Across Product Hub Organizations to Add Items as Affected Objects on Issues and Actions

Associate Resource Instances and Add Serial or Lot Numbers to Affected Items Using REST Services

Use Save-As Action to Carry Forward Attachments and Affected Objects

View Creator and Assignee on Security Tab

User Interface

Access Work Areas in Reorganized Navigator Groups and Group Icons

To support a more consistent and logical grouping of Oracle Supply Chain Management Cloud work areas, this update includes a reorganized Navigator, plus changes to the group icons on the home page.

In this update, a new Order Management heading in the Navigator and group icon on the home page includes the following work areas:

  • Order Management
  • Pricing Administration
  • Global Order Promising
  • Service Logistics

A new Supply Chain Execution heading and group icon includes the following work areas:

  • Work Definition
  • Work Execution
  • Maintenance Management
  • Quality Management
  • Inventory Management
  • Cost Accounting
  • Receipt Accounting
  • Fiscal Document Capture
  • Electronic Records
  • Financial Orchestration
  • Supply Orchestration

In addition, the Supply Chain Collaboration work area has moved to the Supply Chain Planning heading and group icon, and the Collaboration Messaging work area has moved to the Tools heading and group icon.

The Costing, Manufacturing, and Quality Management headings and group icons that appeared in previous updates are no longer available.

The new group icons on the home page are easy to identify:

Order Management and Supply Chain Execution Group Icons 

And so are the new headings in the Navigator:

Order Management and Supply Chain Execution Headings in the Navigator

Steps to Enable

No steps are required to enable this feature.

Manufacturing

Create Object Composition and Where-Used Reports for Genealogy Using OTBI

You can create product composition and component where used reports leveraging two new OTBI subject areas:

  • Product Genealogy - Genealogy Object Composition Real Time
  • Product Genealogy - Genealogy Where Used Real Time

Watch a Demo

Steps to Enable

You can add the new Product Genealogy - Genealogy Object Composition Real Time and Product Genealogy - Genealogy Where Used Real Time subject areas to your existing reports, or create new reports that use the new subject areas.  For details about creating and editing reports, see the Oracle SCM Cloud: Creating and Administering Analytics and Reports guide, available on the Oracle Help Center.

Key Resources

  • For details about creating and editing reports, see the Oracle SCM Cloud: Creating and Administering Analytics and Reports guide, available on the Oracle Help Center.

Watch Create Object Composition and Where Used Reports for Genealogy Using OTBI Readiness Training

Role Information

  • Duty Role Name and Code:
    • Product Genealogy Transaction Analysis Duty (FBI_PRODUCT_GENEALOGY_TRANSACTION_ANALYSIS_DUTY)
  • Job Role Names and Codes:
    • Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR)
    • Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR)

Deactivate a Work Definition

When a product or a production line becomes obsolete, it is imperative to obsolete the affected work definitions to avoid manufacturing from accidentally using the inactive work definitions in the future. Prior to this update, there was no way to obsolete a work definition. You had to introduce new work definitions as replacements for the old work definitions, and you had to swap their production and costing priorities to ensure the correct visibility in manufacturing, supply chain planning, and costing. With this update, you can immediately deactivate all versions of a specific work definition using the user interface, file-based data import process, or a REST service. If electronic records and electronic signatures are enabled for the work definition, deactivating a previously approved work definition through the user interface generates an electronic record and initiates the process of approval through a workflow.

When you deactivate a work definition, the work definition status is updated from Active to Inactive. The Inactive On date is populated with the system date when you deactivate the work definition or when the import scheduled process is completed. This prevents future usage of the work definition in supply chain planning, work execution, and cost rollup if the cost scenario effective date is greater than the Inactive On date.

Any released work orders or published cost scenarios that reference an inactive work definition version can continue to use it. In the event that a deactivated work definition has been used in an existing, unpublished cost scenario, cost rollup has to be re-run. Planning collections can be performed again to select the active work definitions.

After a work definition is deactivated, you cannot reactivate the work definition or make changes to any of its versions, and its work definition name cannot be reused for the item. As a result, you have a clear separation between the obsolete and the active work definitions to facilitate downstream supply chain activities.

The following is a screenshot of the warning message upon deactivating a work definition:

Deactivate a Work Definition

Watch a Demo

Steps to Enable

Use the Opt-In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management                         No Longer Optional From: 11.13.19.07.0

Key Resources

  • For details about creating and editing reports, see the Oracle SCM Cloud: Creating and Administering Analytics and Reports guide, available on the Oracle Help Center.

Watch Deactivate Work Definition Readiness Training

Role Information

  • Privilege Name and Code:
    • Manage Work Definitions (WIS_MANAGE_WORK_DEFINITIONS_PRIV)
  • Job Role Name and Code:
    • Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)

Integrate with External Systems Using Additional Work Definition REST Services

Oracle Manufacturing Cloud provides web services to enable integration with external systems, such as product development applications, manufacturing execution systems, shop floor devices, and mobile devices. With this update, the following services have been added:

REST SERVICE FOR MANUFACTURING WORK DEFINITION NAMES

If you want to integrate an external product development application with Oracle Manufacturing Cloud, you may want to get the details of work definition names before creating work definitions.  With this update, you can use the GET method to get one work definition name or all work definition names with the following information:

  • Work definition name
  • Work definition name details

REST SERVICE FOR MANUFACTURING WORK DEFINITION REQUESTS

If you want to integrate an external product development application with Oracle Manufacturing Cloud, you can use the POST method of the Manufacturing Work Definition Requests REST service to simultaneously create and update work definitions using a batch request. Prior to this update, you were able to use the GET method of the Manufacturing Work Definitions REST service to get one work definition or all work definitions. With this update, you can additionally use the POST method of the Manufacturing Work Definition Requests REST service to create a work definition request for the following information of standard and assemble-to-order (ATO) model items:

  • Header details
  • Operations
  • Operation materials
  • Operation resources
  • Alternate resources for a work definition operation resource
  • Descriptive flexfields of a work definition operation, operation material, and operation resource

The POST method of the Manufacturing Work Definition Requests REST service inserts the data into the interface tables, and then triggers the processing for POST and PATCH functions to create and update work definitions in the cloud.

With the additional REST services for Manufacturing Work Definition Names and Manufacturing Work Definition Requests, the initial data load from an external source system or ongoing updates to work definitions can be streamlined into Oracle Manufacturing Cloud.

Steps to Enable

If you're using REST services with your Oracle Cloud implementation for the first time, then follow the instructions in the Quick Start section of the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Key Resources

  • Refer to the REST APIs for Oracle Supply Chain Management Cloud documentation on the Oracle Help Center.

Role Information

To use the REST Service for Work Definition Names feature, the following privileges or roles are required.

  • Job Role Name and Privilege:
    • Production Supervisor (WIS_GET_WORK_DEFINITIONS_SERVICE)
    • Manufacturing Engineer (WIS_GET_WORK_DEFINITIONS_SERVICE)

To use the REST Service for Work Definition Requests feature, the following privileges or roles are required.

  • Job Role Name and Privilege:
    • Manufacturing Engineer (WIS_MANAGE_WORK_DEFINITIONS_SERVICE)

Manually Procure Materials for Work Orders

This new feature may be useful for manufacturing environments that do a lot of prototyping or engineer to order, where components are not planned in advanced and need to be purchased direct for a specific work order. It will generally not apply to companies that plan manufacturing and component purchases in advance using standard or ATO Model bills of material.

The following diagram depicts a comprehensive process flow for manual procurement of materials for a Manufacturing work order.

Process Flow for Manual Procurement of Materials for a Manufacturing Work Order

CREATING A PURCHASE REQUISITION FOR A MANUFACTURING WORK ORDER

You can create a purchase requisition for a manufacturing work order by navigating to the Self Service Procurement page, entering a requisition, and then associating it to the manufacturing work order.

You can create purchase requisitions on the Self Service Procurement page for three types of items:

  • Catalog items
  • Inventory items
  • Noncatalog items (can be amount based or quantity based)

It is important to associate your requisition items with a work order. You must make the association individually for all requisition lines. To make the work order association, on the Edit Requisition page, in the Requisition Lines section, select Work Order as the destination type.

View Requisition Page

Once the association is made and submitted, a purchase order is created for the requisition. Based on your setup, you may need approvals for both the purchase requisition document and the purchase order document.

VIEW AND TRACK PURCHASED ITEM DETAILS 

On the Purchased Item Details page, you can:

  • View a list of all purchased items for a work order
  • Use the Details icon for any purchased item to track requisition details

Purchase Item Details Page

You can also view a list of purchased items on the Edit Work Order page in the operations tab, for each work order operation.  Note that if this feature is enabled for the plant, then the work order operations tab for all work orders will have an additional column for purchased item. This is regardless of whether any items have been purchased for the work order or not.

PURCHASE ORDER RECEIPT AND CORRECTIONS

The warehouse manager receives the purchased items. All purchased items are received for their respective work orders, as the destination type is specified for all requisition lines. You can view the details on the Purchased Item Details page or the Manufacturing Transaction History page.

On the Purchased Item Details page, you can configure a receipt for the following:

  • Correct quantity
  • Return to supplier
  • Return to receiving

VIEW PRODUCTION TRANSACTION HISTORY 

You can view all transactions performed for a manufacturing work order on the Production Transaction History page. Regarding purchased items for a work order, you can view the following transactions:

  • Purchased item receipt
  • Purchased item receipt correction
  • Purchased item return correction
  • Purchased item return to receiving
  • Purchased item return to supplier

Production Transaction History Page

WORK ORDER COSTS 

A cost accountant can view the total cost on the Review Work Order Costs page. The total cost comprises of cost for resources and materials. Material cost includes both transacted operation items and received purchased items.  Note that at this time, noncatalog items (amount or quantity) are not considered for calculating work order costs.

REPORTS 

You can view purchased items in the Work Order Traveler Report.

Watch a Demo

Steps to Enable

The availability of this feature is controlled by a plant parameter attribute called Allow direct purchases for work order in the respective manufacturing organizations.

Tips And Considerations

In manufacturing, there is no navigation from the work order to the Self Service Procurement Page.  However, once you are in Self Service Procurement requisition, you can associate a manufacturing work order to each requisition line manually.

Non-catalog items (amount/quantity) are not considered for calculating work order costs.

Key Resources

Role Information

  • Job Role Name and Code: 
    • Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
  • Privilege Name and Code:
    • Manage Requisition of Items with Work Order Destination Type (WIP_MANAGE_ITEM_PURCHASES_FOR_WORK_ORDER)

Perform Ad Hoc WIP Inspection from Dispatch List

Prior to this update, you could create an ad-hoc WIP inspection by navigating to the Create Inspection task and entering the inspection details and results. However, this navigation path requires that the context of the point of inspection such as work order, operation, and item be specified again before inspection results can be entered.

With this feature, a new icon to enter inspection details appears on the dispatch list, similar to the icons for reporting material and resource transactions. By clicking on the inspection icon for a specific row in the dispatch list, you can create an ad hoc WIP inspection in the context of a work order operation to inspect work in process at an intermediate operation or the product at the final operation. You can also specify the quantity to inspect and select the appropriate inspection plan in order to enter inspection results.

Compared to inline WIP inspection, ad hoc WIP inspection does not drive the completion of the operation or product. Consequently, you can decide how to proceed with work order processing by implementing inspection actions, such as create a nonconformance, display a message, or send a notification. Saved inspections can be viewed later through the work order history.

With quick access to ad hoc WIP inspection from the dispatch list, you have the flexibility to enter inspection results at the appropriate time during work in process or after the product has been produced.

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

The "Enter Inspection Details" column is displayed by default and can be hidden by navigating to the View menu on the dispatch list, if it is not applicable to your business process.

For more information about the setup of inspection characteristics and inspection plans for ad hoc WIP inspection, refer to the Quality Management Cloud documentation, available on the Oracle Help Center.

Role Information

  • Users provisioned with the Production Operator role will automatically be able to initiate inspection from the dispatch list.
  • Privilege Name and Code: No special privilege required.   
  • Job Role Name and Code:
    • Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB).

Quality Management

Create Issue or Action from an Item in Product Development

Create a quality issue or action directly from the item page in Product Development. After you create the issue or action, it's automatically related to the item.  This enables a more seamless flow between a problematic item and quality-related actions.

To create a quality issue or action, open the Actions menu on the item page and select Create Quality Issue or Create Quality Action.

Create Quality Issue from Item Page

Enter the key attributes of the issue or action in the Create dialog. Upon confirmation, an issue or action is created and the item is automatically added as an affected object.

Create Quality Issue Dialog

Watch a Demo

Steps to Enable

No steps are required to enable this feature.

Key Resources

Watch Better Usability and Integration in Quality Issue and Action Management Readiness Training

Search Across Product Hub Organizations to Add Items as Affected Objects on Issues and Actions

Use extended search capabilities when assigning items as affected objects. In the past, search was limited to the default master organization; you can now search and relate items across organizations.

Click Select and Add on the Affected Objects tab to open a search page where you can search for items. The search results now show the organization the items are associated with. The search also returns items from organizations other than the default master organization.

Search Retrieves All Item Organizations

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

The default master organization must be set up during Product Development configuration.

Key Resources

Watch Better Usability and Integration in Quality Issue and Action Management Readiness Training

Role Information

To use this feature, the following privilege or role is required:

  • Job Role Name and Code:
    • Quality Design Engineer 
    • Quality Analyst 

Associate Resource Instances and Add Serial or Lot Numbers to Affected Items Using REST Services

Quality processes often require the capture of data across multiple external applications.  Manual data entry increases the risk of inaccurate, incomplete data.  Use the enhanced Quality Issues and Quality Actions REST APIs to log quality issues or actions from external applications. You can associate the resource instance for an affected manufacturing resource and add the serial or lot numbers of affected items. You can also capture additional data on specific resource instances and serial or lot numbers, improve analytical insights, understand trends, and initiate targeted audit or corrective action to drive faster resolution.

Capture Resource Instance Details

Steps to Enable

Review the changes to the Quality Issues and Quality Actions services, and update your REST client as desired.

Key Resources

  • Refer to the REST APIs for Oracle Supply Chain Management Cloud documentation, available on the Oracle Help Center.

Watch Better Usability and Integration in Quality Issue and Action Management Readiness Training

Use Save-As Action to Carry Forward Attachments and Affected Objects

For certain business processes, you need to create a new quality issue from another quality issue, or a quality action from another quality action. This results in redundant manual data entry.  

Similar to the functionality provided for the creation of a quality action from a quality issue, the new Save-As functionality for a quality action automatically copies attribution, attachments, and affected objects, and relates it to the original source.  The Save-As functionality of a quality issue is also extended, and now lets you modify the type, select a new workflow, and copy over any attachments and affected objects in Draft status.

Reduce time and effort spent on manual data entry and resulting errors with this new functionality.

Change Type and Workflow in Save As Dialog

Steps to Enable

No steps are required to enable this feature.

Key Resources

Watch Better Usability and Integration in Quality Issue and Action Management Readiness Training

View Creator and Assignee on Security Tab

While working on a quality issue or quality action, you now have full visibility into the restricted list of users and roles who have access to the object.  New enhancements extend the Security tab to include object creator and assignee information. You can now view the list of users and roles, as well as the creator and assignee in the Security tab, and make sure you have the right user assignments for the object.

View Creator and Assignee in Security Tab

Steps to Enable

No steps are required to enable this feature.

Key Resources

Watch Better Usability and Integration in Quality Issue and Action Management Readiness Training