Step2: Launch Active Workspace Client and define logical object root as “MS WordX” dataset as we want to fetch the properties from Document Revision to MS Word X dataset that is going to be attached to Document Revision with TC_Attaches relation

Step3: Create the Document Management Template and attach MS WordX file to it

Step4: Link “Logical Object” created in the Step1

Step5: Open the MS WordX document and define the custom properties that you want to synchronize with Teamcenter from the MS WordX file. To define custom properties, you must launch the MS application and go to the info and look for properties, and then “Advanced properties”

Step6: Embed those properties in the MSWord X file and save it

Step6: Release the “Document Management Template”

Step8: Define IRDC for custom Document Revision

Step8: Define the below business constant on Item Revision required to

Step10: Define the workflow as below (Important Note: At present, I see if you don’t fill the attribute during object creation, you have to explicitly run this workflow to synchronize the attribute)

Step11: The system is ready for usage, create the custom Item that will get created along with the MS WordX dataset (This happens through the Document management template through IRDC).
(As mentioned above, if you fill the attributes during object creation you get those synchronized automatically, else you have to run the above workflow)

When you open the document, you will see the attributes synchronized from Teamcenter to file

Benefits:
• Logical objects made attribute mappings way simpler than the traditional method
• Logical objects enable attribute mapping to apply automatically to all the document instances (unlike the old approach that required an individual document update)
• Logical objects eliminate the need for client-side deployment required in the old approach

I don't know the official standing of LCS regarding this, but what I see as advantages:

- If you modify an attribute mapping using logical objects, this applies automatically to all the document instances (using the old approach, this required an individual document update).
- Defining attribute mappings gets simpler and could be done by an end-user (maybe not define the input items, but at least add/remove attributes).

Also, in terms of strategy, I guess Teamcenter Office Online + Logical Objects would allow for deprecation of the old Office Client (which requires client-side deployment, something not really appreciated by IT departments).
And in terms of limitations, the one I see is we only can map from Teamcenter to document and not the other way around (something which was possible using the Office Client).

● They are useful for various applications w/o exposure to complex data model details
● Gather useful properties from various related objects into a single place
● Eliminate the need for the end-user to know the data model by presenting a flat list of properties
● Share specified properties without exposing others
● An additional benefit is that the Logical Objects are basically using Dynamic Compound Properties

Logical Object LinkedIn Post:

create ‘Logical Objects’ to use with MSOffice and attribute exchange

In other words, if you have a Logical Object with Root = Item Revision and you configure it to get a property from an object related to Item Revision, can you display the LO property in the Overview, for example, of the Item Revision.

Below is a simple example I created to see if/how this could work. I was expecting (hoping) that would display the Dataset last_mod_date property on the Item Revision Overview, but this didn’t work.

Hello,

Document properties with those names must be added manually, then their values are synchronized (on check-in or during the workflow execution, depending on your configuration) from Teamcenter to the file using the paths in the LO.

Of course, this is never done by “regular” users, but by document administrators that create document templates with those properties.

Then the template is instantiated by regular users (through an IRDC), so these properties are already there.

Then created DM Template with an MSExcelX dataset, add Range Names for two cells to allow the Name to go to Excel and the Desc to go back to Teamcenter.

Added the “FT4_LO_Dataset” to the MSExcelX dataset, using that one relation (for which I forgot the name just now).

Then released the DM Template Revision with “TCM Released” status.

Defined IRDC in BMIDE for this Template and attached it to the “Document Subject” property on FT4_DocumentRevision.

One the (OOTB) ItemRevision set Fnd0RelToDatasetForLOAttrExch to TC_Attached and Fnd0TriggerLOAttrExch to Enabled.

Packaged and deployed it to Teamcenter.

After that just created a new Document based on this Template, using a custom tile that creates a FT4_Document.

This results in a FT4_Document, with the correct Excel (including the FT4_LO_Dataset) attached.

Then we select the MSExcelX dataset in Active Workspace -> Open -> Open in Office Client.

The MSExcelX dataset is opened in Excel and as far as I can tell the attribute exchange is not occurring.

Step0:
How to configure logical objects?
● Install “Logical” object feature using Deployment Center or TEM
● Use the Logical Objects administrative tool in Active Workspace to

Create of modifying logical object:

Step1: Define the logical object
Step2: Define the IRDC and link the above created LO to MSWord Dataset
Step3: Define the attribute in the MSO office and add to the contents

Step4: Released the Document Template
Step5: Create a new IRDC for Document Management Template
Step6: Set the business object constant