You have to deal with context indexing if you change the item number. Like Keith says, just give yourself Modify privilege and change it through the client.

You are going to have to use code or upgrade. Starting with 9.3.5 (?) you can clear values with Import.

Archive the old templates.

In short, you are getting into a deeper part of the pond. Be careful.

Integration usually starts with an xml publish from PLM. This is the “Agile Content Service” (ACS) in the administrator. This service is also documented in the PLM documentation set.

NODETABLE

select * from item where item_number = ‘134433-14’;

select item_number, p2.* from page_two p2, item i where i.id = p2.id and i.item_number = ‘134433-14′;

There is a lot more but this gets you started.

As far as I know it is magic that the database is told to enable an attribute. But the attribute and its properties are kept in two main tables: NODETABLE and PROPERTYTABLE. Most everything is stored as number codes so it will be a bit difficult without a code sheet, which Oracle does not provide. For instance, non-page-three part attributes:

select description from nodetable where objtype = 1 and parentid = 10005;

Yeah, 9.3.7. Last half of 2021. We can start a rumor mill of what it should have. I “heard” it will have:

• An integration to Slack or build-out of Discussion capability.
• Digital Thread/Twin for in-field management.
• A SIMPLE pdf redline tool.
• pdf watermarking of old and new revisions.
• Publish and Notifications to external email addresses with return receipt.
• A change impact assessment feature.
• Updated html editor and larger html fields.
• Checkbox and To-Do fields.
• Rejection codes.

I am afraid not. The old workflow name changes everywhere it was used. Choose a nice name like, “Workflow 1 (obsolete)”