Hi. I have a mail-in db that people post a question to. There is an agent that runs every 5 mins to check the inbox, and for new documents posted, it creates a new document using the subject and body of the original question, and mails a new memo out to a group. The agent is set to save message on send and to delete the original one. The idea is that the message is saved in the db and mailed out to the group, so that when the group responds to the email, their response goes back into the mail-in db as a response to the message that was sent out. But this is not happening… the message that is saved has a different UNID than that one that the people receive, so their responses are not actual responses and so don’t keep the heirarchy. However, whenever I’m testing this myself and not sending to the group, it works for me, so it’s perplexing. Does anyone have any idea how I can get this to work, or maybe give me some insight as to why it’s not working now? If it is saving the document on send, and sending the same document out to a group, where is it losing the UNID and how can I make sure that the group’s responses will be child documents? Thanks.
Subject: Need help keeping document heirarchy
Although there are a lot of different ways to achieve this, I am wondering why you are taking the complicated way?
Say your users are emailing a question in your mail-in database. The agent then parse the received email and creates a new “question” document in the database, and delete the original message. So far so good.
However, why proceed the same way for the responses?
Ideally, you would rather send a simple notification to the response group. The email would then include a doc link. The user who is responding isn’t responding in his email! He must click the link and get straight into the database, then click a “response” buton.
Using this method, you will have no trouble cerating your hierarchy.
Hoping this helped,
Nicolas Abesdris
Subject: RE: Need help keeping document heirarchy
Thanks Nicolas, that would be the ideal solution but unfortunately the client is adament that this is not what they want. Sending a doclink is usually what we do, but in this case they want to respond to the automated email and have their response go back to the db as a child doc of the original one posted. This is where I’m having the trouble. I have reworked the code about 10 different ways and each time my results are inconsistent, sometimes it works and sometimes it doesn’t. I’m about to give up.