🕑 Inbound configuration
Certain object types and file types can be stored differently. Customize default storage types for specific ERP objects (e.g. SERVICECALL) and/or file types (e.g. PDF).
If an inbound attachment matches the entered patterns (ERP object ID and/or file type), it will be stored as defined in ‘Inbound configuration’. If no ERP object ID is entered, an entry will be relevant for all objects of a given file type (similarly, if only file type is entered, it will be relevant for all ERP objects).
Company-dependent inbound configuration
Company-dependent inbound configuration has priority over the default Inbound Configuration and will be searched for first. Only if no matching pattern is found, other configurations will be searched.
Storage type priority rules
Storage type determination for inbound attachments follows certain priority rules.
- 1. Storage type for inbound attachments is always first searched for in the company-dependent Inbound configuration - based on company ID and ERP object ID and/or file type.
- 2. If the attachment’s company, object type and file type won’t match any pattern found in the configuration, customizing will be searched for in the default Inbound configuration - based on ERP object ID and/or file type.
- 3. If no relevant entry is found, it will be searched for in the company-dependent General attachment configuration - based on company ID.
- 4. If not found, a storage type would be taken from the default General attachment configuration.
Inbound configuration example
The following configuration is maintained:
📁 Default configuration
🕒 General attachment configuration
Max Att size | Allow atta deletion | Storage type | Block in | Block out |
|---|---|---|---|---|
52428800 | x | G |
🕒 Inbound configuration
ERP Object ID | File Type | Storage type |
|---|---|---|
ACTIVITY | G |
📁 Company-dependent configuration
🕒 0001 - General attachment configuration
Max Att size | Allow atta deletion | Storage type | Block in | Block out |
|---|---|---|---|---|
52428800 | x | B |
🕒 Inbound configuration
ERP Object ID | File Type | Storage type |
|---|---|---|
SERVICECALL | B | |
SERVICECALL | D | |
EQUIPMENT | D |
🕒 DMS configuration
DMS configuration for company 1 | |||||
|---|---|---|---|---|---|
ERP object ID | Document Type | Document status | Cumulated | DefStorageCat DMS | Folder path |
ZPK | MU | DMS_C1_ST | /tmp/ | ||
SERVICE CALL | ZXK | MS | DMS_C1_ST | /tmp/ | |
Service call attachments created in FSM company 1
According to the inbound configuration for company 1 (which is used first):
Service call attachments of file type other than PDF will be stored as BDS attachments.
Service call attachments of file type PDF, will be stored as DMS attachments.
According to the DMS configuration for company 1:
Service call attachments stored as DMS will use document type ‘ZXK’, status ‘MS’ and default storage category ‘DMS_C1_ST’.
Equipment attachments created in FSM company 1
According to the inbound configuration for company 1:
Equipment attachments will be stored as DMS attachments, regardless of their file type.
According to the DMS configuration for company 1:
Equipment attachments stored as DMS will use document type ‘ZPK’, status ‘MU’ and default storage category ‘DMS_C1_ST’ (this setting is relevant for all objects other than service calls).
Activity attachments created in FSM company 1
Since no company-specific inbound configuration is maintained for Activities, the Default inbound configuration is used:
Activity attachments will be stored as GOS.
Item attachments created in FSM company 1
Since no company-specific and default inbound configuration is maintained for object ‘ITEM’, the General attachment configuration for company 1 will be used:
Item attachments will be stored as BDS.
Item attachments created in FSM company 2
Since no company 2-specific and default inbound configuration is maintained for object ‘ITEM’, and the General attachment configuration is only maintained for company 1, the default General attachment configuration will be used:
Item attachments will be stored as GOS.