Table of Contents

Search

  1. Preface
  2. Introduction to Business Entity Services
  3. Enterprise Java Bean Business Entity Service Calls
  4. Representational State Transfer Business Entity Service Calls
  5. Simple Object Access Protocol Business Entity Service Calls
  6. Services for Cross-reference Records and BVT Calculations
  7. Supporting Corporate Linkage Service
  8. External Calls to Cleanse, Analyze, and Transform Data
  9. Appendix A: Using REST APIs to Add Records
  10. Appendix B: Using REST APIs to Upload Files
  11. Appendix C: Using REST APIs to Manage Reports

Storage Types

Storage Types

Upload and store files in a supported storage implementation. The storage type that you use depends on whether you want to localize the
Data Director
user interface or attach files to records or tasks.
The following list describes the supported storage types:
BPM
Stores files attached to tasks together with the task data. When you attach a file to a task, the process stores the file to a BPM storage from the TEMP storage.
Files stored in the BPM storage use the following file ID format:
taskId::filename
.
To attach a file to triggered tasks or existing tasks, in the Provisioning tool, enable attachments for task triggers, task types, and task actions. For more information, see the
Multidomain MDM Provisioning Tool Guide
.
BUNDLE
Stores resource bundle files that localize the
Data Director
user interface.
Files stored in the BUNDLE storage use the following file ID format:
besMetadata
.
DB
Stores file attachments for records in the C_REPOS_ATTACHMENTS table. When you attach a file to a record, the process stores the file to a DB storage from the TEMP storage.
Files stored in the DB storage use the following file ID format:
DB_<RowID>
.
To attach a file to a record, in the Provisioning tool, configure a field with
FileAttachment
as the data type. For more information about configuring the data type, see the
Multidomain MDM Provisioning Tool Guide
.
TEMP
Temporarily stores files in the C_REPOS_ATTACHMENTS table and marks the files as TEMP. Files are deleted from the TEMP storage after they are successfully uploaded to the BPM or DB storage or after a preconfigured expiration time.
Files stored in the TEMP storage use the following file ID format:
TEMP_<ROWID_ATTACHMENT>
.
For more information about configuring the expiration time, see the
Multidomain MDM Configuration Guide
.

0 COMMENTS

We’d like to hear from you!