💦 CREATE AND FUCK YOUR OWN AI CUMSLUT 🔥 TRY NOW ♥
Create AI Cumsluts 💦
Fill_Sign_Document_Creator-Updated.xlsm 209.0 KB
UPDATED PDF CODEBOOK - FILL SIGN DOCUMENTS.pdf 3.0 MB
November 22, 2021

Fill & Sign Document Creator Update [Gold & Silver]


Hello Members!

In this week’s Feature, Fix or Focus, we take last week’s Fill & Sign Document Creator training, and the features I added are saving & exporting via portrait/ landscape, PDF -open after export & various bug fixes.

Please don’t forget to add your requests for your own Feature, Fix or Focus each week when I post a new video, right here on Patreon. Each week I will either add a new feature, fix a bug or an issue, or create another training with a special focus on any part, all based on your feedback and comments.

Make sure to view the brand new and updated training and download the updated workbook in the attachments below.   As always, great to have you here, and thanks so much for your support.

Fill_Sign_Document_Creator-Updated (Vimeo)

Comments (2)

R
Richard Whitaker · November 27, 2021

Hi Randy, RE: Fill and Sign Document Creator Meets Document Workflow. In our Manufacturing community we serve there is often the requirement of generating a fillable document ( now paper [ yuk ] ) with some of the information required, but not all. Additional information may be added, existing information changed or deleted by another collaborator in the Workflow chain. The use case for this is iterative design criteria document exchanged between an engineer and other internal staff or customers. The idea is the document is created and workflowed to the next collaborator who adds, changes, deletes information on the form. It would be a killer feature to track each document revision by collaborator and highlight information on the document that was changed as well as comments of the collaborator, saving the original document ( Like Rev 1, 2, 3 ...) so that the entire chain of events can be replayed by simply reviewing Rev 1 with Rev 2 and so on. Your thoughts?

E
Excel For Freelancers · November 27, 2021

Hi Richard, thanks so much for the comment and idea. I think it makes a ton of sense and it could be a really powerful application when you can track changes on a per-employee basis as the document makes its way through the flow. This would require a separate database with an employee id, name, change date, document ID, change details such as the text, change type and then location of those changes. You could then have a history and filter changes by user. These changes can also be approved on an individual basis. I have written the idea down for a possible future training. Thanks so much.