Hi xman,
Thank You for your reply. Although the file name is accessible through the constructed message, the file name alone does not help me uniquely identify the drop location. How can I ensure that I can access the folder path so I can use some regular expression and parse some identity against the filepath? If the folder path is not accesible in the orchestration, can i assign some property to the receive location that i can access through the orchestration. Once again I appreciate your guidance.
Regard Ty