Thought of sharing the following upon some recent questions received from a project regarding task attachments. Could be helpful if anyone has the same doubts, also to please contribute to the discussion as there are still few doubts unconfirmed as mentioned in latter.

The situation was that customer have had around seven attachments attached to a task with INTERNAL_TYPE = ‘SIGNATURE’ and there was a doubt why they could not see those seven attachments in the device and how the INTERNAL_TYPE gets fetched. And whether they can manually add attachments which has INTERNAL_TYPE = SIGNATURE. See inputs below,

1. It is correct the customer signature attachments should not be visible in mobile for the technician. The reason is technician should not have the authority to edit/remove the customer signature. The customer/technician signatures will be stored in attachments having value as ‘SIGNATURE’ in INTERNAL_TYPE column in database (not visible in UI). This is not controlled in sync rules but from the code. Therefore, users cannot manually insert signature attachments.
    
2. Customer signature happens in DebriefCustomerSignature (‘Customer Review’) screen. And if user have enabled for technician signature, it will be seen on DebriefSignature (‘Summary’) screen. Once customer signs > save, the signing block will be frozen. Once technician signs, the task should be completed > then gets deleted from device. Hence,  users will not be able to add these signs again for the same task.
    
3. Thus, INTERNAL_TYPE value is not something users can control or insert manually. However, was not able to confirm the remaining values that may exist in the ATTACHMENT.ITERNAL_TYPE column (apart from signature). I could see an entity ATTACHMENT_INTERNAL_TYPE which resides under FSM codes, that has only SIGNATURE as a code value. Could this be it though the column names slightly differ, any thoughts please?