T4S will not automatically create the TRIM Containers for each configured T4S Salesforce sObject or custom object, as there are too many different Salesforce sObject types, as well as custom object typesTRIM Containers for each configured T4S Salesforce sObject or custom object, as there are too many different Salesforce sObject types, as well as custom object types.
The most common business rules require a new Content Manager Container created after a new Salesforce record has been inserted.
i.e. A new Account is created in Salesforce, so a new Container for the Account should be created in Content Manager and mapped to the new Account.
To achieve this you will need to create or extend your own Salesforce Apex trigger so that the T4S API is called to create the Container automatically.
If automated Container creation is not required, the T4S Admin pages will allow a Salesforce Admin to create multiple Content Manager Containers from a button click.
When an sObject has been configured in the T4S Admin, an ordered list is displayed where records without a Container can be selected to have a Container created. Or a record with a mapped Container can be re-mapped to a different Container.
When you set up the T4S Settings for a sObject or custom object, you can select the “Enable Sub Container“ checkbox, and then use this boolean value within your custom code to decide if a new Container should be created or not when a new Salesforce record is inserted.
...
The “Trim sObject Container Uri“ field tells T4S where the new Container should be created.
This can be overridden by adding the specification property “RecordContainer“ and value, with the Container Specification Property Set.
This again can be overridden if you have requirements to create separate Container Specification Property Sets for each Salesforce Record Type for the configured sObject.
Automated Container Example codeCode:
Create a trigger for the sObject that you would like a Container created for on each insert or update.
...