Sharing content across configurations
This table lists the caveats for working with multiple configurations in your Contenta S1000D CSDB where you share content between configurations.
| Regarding... | Note... |
|---|---|
| Data access | Users are only able to access data that is in configurations to which they have access on their desktop in the CSDB. |
| Unique names | DM, PM, SCPM, graphic/ICN, Word, Excel, PowerPoint, CSS, JS, and ZIP object names must be unique across configurations. Graphics names must also be unique per type; graphics with the same name but a different type (file format) are not permitted in any configuration. |
| Modules/graphics used by multiple projects or programs | Any modules, graphics, Word, Excel, PowerPoint, CSS, JS, and ZIP objects that are shared across projects/programs need to be stored in a shared configuration that is on all users' desktops in your CSDB. Each shared object may only exist in one place in the database, and users may only access data in the configurations that are on their desktops. Data that is frequently shared includes Business Rules (BREX), Applicability (ACT, PCT, CCT) and Common Information Repository (CIR) data modules, as well as some graphics. |
| References | DMs, PMs, and SCPMs may reference items in other configurations. The S1000D Validate tool checks references across configurations, and reports an error message if validating a reference to which the user does not have access. For instance, this can happen if the user does not have access to the configuration in which the reference is located. The S1000D Clip Reference tool works on any object in any configuration to which the user has access. |
| Upload Content | The S1000D Upload Content tool checks the uniqueness of object names across configurations and uploads content to the configuration from which it was launched. Note, codes (model identification codes, system codes, DMC, ICN, etc.) that are created with Upload Codes, Define and Manage MNS, Define and Manage Programs, and Define DMRL and IRL are not associated with a particular configuration. |
| Publish | The S1000D Publish tool resolves references across configurations, and reports an error message if there is a reference to which the user does not have access. For instance, this can happen if the user does not have access to the configuration in which the reference is located. |
| DDN Export | Users may export any content to which they have access. Typically, a DDN is created from content that is only in one configuration. Users only have access to exported DDN zip files if they have access to the Dispatcher object in the CSDB. See Viewing DDN History and Downloading DDNs. |
| Manage DMRL/IRL | The Manage DMRL/IRL tool is launched from a configuration. It shows codes across configurations because it reads a database table that contains all codes. Note however:
|