Tricky Object Connection Transformation

​@AntonioInfoConsulting 

Hi, did you find time to review the documentation on Object Connection Transformation yet? It should explain the different cases and when you need what kind of approach. It's quite detailed and a bit technical, but it should cover it all. If it doesn't, we need to make it better/clearer, so any feedback on what's in there is useful to us.

​@Mathias Dahl 

The documentation was reviewed several times over when trying to create this rule. 

Was hoping that the Community was able to provide some insight as to why the particular rule was not working.

My feedback items in relation to the documentation are :

1.Reference to Custom fields is outdated - this is from App 10 or previous days - it needs to be revised

2.In the System Defined Rules for Object Connection Transformation section, there are references to non existent logical units e.g : HistoricalRound - best to revise this section

3.In the System Defined Rules for Object Connection Transformation section, there are no items for work tasks on the list here -best to revise this section as it seems like this is inherited from Apps 10 or previous

Here is a step by step approach of what I am trying to achieve.

1.Attach a document to an item on the Object type screen

2.Attached document should be inherited by all the Functional Objects connected to that Object type

This Object connection transformation line was defined as  :

This OCT line rule works as intended.

When I attached a document to the object type, the functional object inherits this document.

3.Attached document should be inherited by the Work Order created which are connected to that same Functional Object

This Object connection transformation line was defined as  :

The intended behavior from this line is that any new Work Order created and connected to a Functional Object should have the attachment that originated from the Object type and was inherited by the Functional Object. 

I am trying to understand :

1.Have I set up the line rule incorrectly ?

2.Is it a limitation where we cannot inherit the attachments into the Work Order because the documents on the Functional Object was inherited by the attachments on the Object type

3.Was there a background process to run etc. to update the attachment of the Work Order from the Functional Object? 

Thanks for the feedback! I'll make a note for the team to look into this. I also found that it might be helpful to have some more section headings to locate certain things easier.

One thing that seems to be missing is that it's not clearly stated that Object Connection Transformation rules ARE NOT and CANNOT be "chained." From what I understand, that's what you would have wanted here.

If you have three entities, A, B, and C, you cannot define a rule from A to B and a rule from B to C and expect a document or media item to be inherited all the way from A to C. This is not supported and probably never will, because of performance and maybe other reasons as well.

If you want a document or media item to flow from A to C, you need to define a specific rule for that, and often that will involve writing a PL/SQL method to do the work, because you might not be able to do a simpler "column-mapping rule".

Is it clearer?