Forum Discussion
David_M
Cirrostratus
CirrostratusDevcentral email response adds the entire signature to the response!
Here's another one to the long list of goof ups.
I used the email reply feature from my work id and on checking the answer I saw it has my entire work signature along with my email and phone number.
Hope this is fixed soon.
PS: Though everyone should know this immediately hence making this post here
Hi David;
Regarding this specific feature, the SaaS rich text editor does not support this feature. It's QuillJS but feature restricted to comply withe SaaS locker service. This was also a change that was made while we were mid deployment so we really didn't have much time to figure out a workaround while staying compliant with the systems security policies.
Most of the issues you're raising the DevCentral team is raising or already was raising as we launched. We have a laundry list of things we're working on so this will take some time to get sorted out but the several SaaS vendors that now integrate to make up the new DevCentral are very aware of the shortcomings we are facing and are working with us to make their products better.
Time will tell.
- LiefZimmerman
Admin
- I don't follow the problem? Can you share a bit more detail around
* Email reply feature (what were you replying to)
* work id (do you mean your work email adress?)
and if you didn't edit/delete the answer show me that specific example?
David_MI used the option to reply by email, and it displayed my signature with my email id and phone number yes, you can try it out.
of course i deleted the answer . .jesus man!
- LiefZimmerman
I suspect you are seeing content added to your email reply by either your client or work server. This account (yours) doesn't contain any information about your Work Email or Phone.
- David_M
i pasted the image it didnt work . .
Hi David;
Regarding this specific feature, the SaaS rich text editor does not support this feature. It's QuillJS but feature restricted to comply withe SaaS locker service. This was also a change that was made while we were mid deployment so we really didn't have much time to figure out a workaround while staying compliant with the systems security policies.
Most of the issues you're raising the DevCentral team is raising or already was raising as we launched. We have a laundry list of things we're working on so this will take some time to get sorted out but the several SaaS vendors that now integrate to make up the new DevCentral are very aware of the shortcomings we are facing and are working with us to make their products better.
Time will tell.
