I recently spent some time exploring a basic workflow in Oracle Cloud PLM to understand how product information and change activities are connected inside the application. Instead of only reading about the process, I wanted to try a small hands-on scenario and see how the flow actually works step by step.

The activity began with creating a new item in Product Data Hub (PDH). After entering the required details, the item was successfully created and became available for further processing. While doing this setup, I understood how PDH acts as a central place for maintaining product-related information.

Once the item was available, I created an Engineering Change Order (ECO). The purpose of this step was to see how Oracle Cloud PLM manages updates or modifications related to a product record. Rather than directly changing information without control, the ECO provides a structured way to handle changes.

After creating the ECO, I linked the newly created item as an affected object. This helped me understand how the system identifies which item is associated with a particular change activity. I found this part interesting because the relationship between the item and the change order remains connected throughout the process, making tracking much easier.

I also explored the lifecycle side of the flow to see how the item moves through different stages along with the change process. Even though this was only a small demo, it gave me a practical idea of how Oracle Cloud PLM helps maintain order and visibility while handling product updates.

A few things I learned from this exercise were:

* how item records are created and managed in PDH,
* how ECOs are introduced for handling changes,
* and how affected objects participate in the overall change flow.

Apart from the technical side, this was also my another experience explaining the scenario through a demo video and documenting my understanding in a blog format. It helped me improve both my learning and the way I communicate technical concepts.

Demo Video: https://youtu.be/naJ_R-DKVN4?si=clI5UEs7Y7OTDNsB

Recently, I worked on a simple workflow requirement in Oracle Cloud PLM where the goal was to fetch the Work Order ID for all the work orders present in the system. While the requirement sounds straightforward, handling it efficiently in a workflow was the key part.

Requirement

The objective was not to process a single record, but to retrieve Work Order IDs from all available work orders. Since the data exists as a list, the challenge was to iterate through each record without creating repetitive workflow steps.

Approach I Tried

To achieve this, I started by adding a Business Object node to fetch all work orders from the system. The response from this node comes in a list format (array), which I stored in a variable called “items”.

This “items” variable contains multiple work order records, and each record has its own attributes, including the Work Order ID.

Using Loop Node

Once I had the complete list, I configured a Loop Node and passed the “items” variable as the collection. This allows the workflow to iterate over each work order one by one.

Instead of manually handling each record, the loop automatically picks one item at a time from the collection and processes it.

Extracting Work Order ID

Inside the Loop Node, I added a Code Node to extract the required value. During each iteration, the loop provides a “current item”, and from that, I fetched the Work Order ID.

So effectively:

 The loop runs for all records in “items”
 Each iteration gives one work order
 The Code Node extracts the Work Order ID from that record

Output Handling

Once the IDs are extracted, we can use them further based on the requirement — for example:

Ø Sending them via email

Ø Logging them

Ø Passing them to another step in the workflow

Key Takeaway

This approach helped me avoid creating multiple workflow steps and made the design much cleaner. Using Loop Node for such list-based operations is very useful when working with multiple records in Oracle Cloud PLM.

💬This was a focused use case, but it helped me better understand how to work with collections and loops in workflows.

Also, This was a useful learning & YouTube sharing experience for me while exploring workflow automation in Oracle Cloud PLM. I’m still learning and open to feedback or alternative approaches from the community.

Demo Video: https://youtu.be/Z2Ihja-5bag?si=_Ba34GT-BLis6F61