[ZendTo] [Feature Request custom string in subject per DropOff]

[Travis McDugald]

I think the original poster and I may have different use cases.

Perhaps present it to the user not as part of the subject.  Perhaps label it as “Message ID”. I would assume displaying would be a setting pref file.  So this way, 

 If (isset($messageID)) then $subject = [Zendto] . $messageID . $subject; else $subject = [Zendto] . $subject;

 I know that’s not even close to proper code, but I hope you get the gist.
 
For me, the [ZendTo] can stay or be replaced.

I’m guessing anyone else who would use the feature has another ticketing or request system they are using that generates the custom string they need to use.  For me, even the term request ID would work.

My thought behind it is to making merging these mails into another system easier to automate. It would also make it easier to display in email in a conversation view.  Anyone using the feature would have a internal custom name for the custom string.

Then again, long day and I’ll stop rambling. 

Sent from my iPad

> On Apr 29, 2019, at 10:19 AM, Jules Field <Jules at zend.to> wrote:
> 
> Folks,
> 
> I'm having a think about this one.
> 
> The idea of the prefix is pretty simple, basically I would give you the "[ZendTo]" string (as an initial default value) in a "Subject" box in the new drop-off form.
> 
> Whatever you end up putting in there gets used instead of [ZendTo] at the start of the email subject lines.
> 
> However......
> 
> If you request a drop-off, you get to supply the whole Subject line for the email to the person you want to send you their files.
> Ideally, that same Subject line would be used in all notifications etc about that drop-off.
> But they have entered the *whole* Subject line, not just the prefix to it.
> If I use their whole Subject line as a prefix, it's going to look weird.
> 
> So what do I do for the Subject prefix, when it was created as a result of a request which had the entire Subject line supplied?
> I clearly can't ask the person sending the request to supply 2 Subject entries — both the current whole Subject line *and* the prefix to use — as that would confuse the hell out of them.
> 
> Any ideas please?
> 
> Cheers,
> Jules.
> 
>> On 21/04/2019 14:29, Mailing Lists via ZendTo wrote:
>> Hi Jules,
>> 
>> yes it would be enough to allow 20 editable characters.
>> 
>> via Smartphone
>> 
>> Am 21.04.2019 um 15:13 schrieb Travis McDugald via ZendTo <zendto at zend.to>:
>> 
>>> While no one has asked for this yet, I do see it’s usefulness.
>>> I do use custom strings in email subjects for some projects as well.  Helps with sorting, searching, and filtering.
>>> 
>>> Side note: great job on everything Jules, thank you.
>>> 
>>> Sent from my iPad
>>> 
>>> On Apr 21, 2019, at 7:40 AM, Jules via ZendTo <zendto at zend.to> wrote:
>>> 
>>>> Peter,
>>>> 
>>>> You effectively just want to allow senders to customise the "[ZENDTO]" subject line tag in each drop-off, correct?
>>>> 
>>>> Does anyone else need to do this too?
>>>> 
>>>> Cheers,
>>>> Jules.
>>>> 
>>>>> On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
>>>>> Hi Jules, hi all. 
>>>>> 
>>>>> I have a strange request from our ZendTo users. They asked if it would be possible to add a custom field when sending a DropOff 
>>>>> that results in a custom text in all ZendTo email concerning this specific DropOff. 
>>>>> 
>>>>> Example current: 
>>>>> 
>>>>> [ZENDTO] One of the recipients has picked up your drop-off! 
>>>>> 
>>>>> Example requested: 
>>>>> 
>>>>> [ZENDTO] CUSTOM_STRING One of the recipients has picked up your drop-off! 
>>>>> 
>>>>> I asked a little bit about the purpose of their request and they told me that project teams sort their email by subject and 
>>>>> consequently keep the project name (CUSTOM_STRING) in every subject of their emails concerning that specific project. 
>>>>> So later they could sort by project name (CUSTOM_STRING) within Outlook to be able to verify when they sent a specific DropOff. 
>>>>> 
>>>>> Question: 
>>>>> Is it possible to implement such a feature? 
>>>>> 
>>>>> I know that I could handcraft it but I don't want to make big changes to the source and always have to keep track of them when upgrading. 
>>>>> 
>>>>> I am currently not on the latest version of ZendTo, so if such a feature is maybe already present in the latest version, feel free 
>>>>> to tell me. 
>>>>> 
>>>>> Thanks in advance. 
>>>>> 
>>>>> Peter 
>>>>> 
>>>>> 
>>>>> _______________________________________________ 
>>>>> ZendTo mailing list 
>>>>> ZendTo at zend.to 
>>>>> http://jul.es/mailman/listinfo/zendto 
>>>> 
>>>> Jules
>>>> 
>>>> -- 
>>>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>>> 
>>>> 'Once is happenstance, twice is coincidence, three times is enemy
>>>>  action.' - Ian Fleming
>>>> 
>>>> www.Zend.To
>>>> Twitter: @JulesFM
>>>> _______________________________________________
>>>> ZendTo mailing list
>>>> ZendTo at zend.to
>>>> http://jul.es/mailman/listinfo/zendto
>>> _______________________________________________
>>> ZendTo mailing list
>>> ZendTo at zend.to
>>> http://jul.es/mailman/listinfo/zendto
>> 
>> 
>> _______________________________________________
>> ZendTo mailing list
>> ZendTo at zend.to
>> http://jul.es/mailman/listinfo/zendto
> 
> Jules
> 
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> 
> 'Find a place inside where there's joy, and the joy will burn out
>  the pain.' - Joseph Campbell
> 
> www.Zend.To
> Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190429/ead34295/attachment-0001.html>