Understanding Attachment Security Across Environments in ERP - Construction
Overview of Attachment Security Behaviour
In Coins, attachments are environment-specific for security reasons. This means that an attachment created in one environment (e.g., Live) cannot be accessed from another environment (e.g., Test). Attempting to open such attachments will result in a security error. This behaviour is designed to ensure data integrity and prevent unauthorized access to attachments across different environments.
Steps for Validating Attachment Functionality
To ensure that attachment viewing is functioning correctly, especially after an upgrade or environment copy, follow these steps:
Upload a New Attachment: In the target environment (e.g., the copied Live or Test environment), upload a new attachment.
Open the Attachment: Attempt to open the newly uploaded attachment from the same environment. It should open without any errors.
Understand Security Restrictions: Note that only attachments created within the current environment are viewable. Attachments created in a different environment will trigger a security block and cannot be accessed.
Common Issues and Troubleshooting Tips
Security Errors: If you encounter a security error, verify whether the attachment was created in the same environment you are trying to access it from.
Environment Copies: After copying an environment, ensure that new attachments are tested to confirm functionality.
Historic Attachments: Be aware that historic attachments from a different environment will remain inaccessible due to the security design.
FAQs About Environment-Specific Restrictions
Why does this restriction exist? This restriction ensures that attachments are only accessible within their original environment, enhancing security and data integrity.
Can I bypass this restriction? No, this is a built-in security feature of Coins and cannot be bypassed.
By understanding and following these guidelines, you can effectively manage and validate attachment functionality in Coins.