============================================================= 0. Ver 9.70 Build 9703 (Ent. Pack - EPDFENT) [+] 1. [Email- Send by Gmail Web App]: (EmailSendMethod: 13) Add a new method for sending email by Gmail Web App (OWA OAuth 2.0 authorization). It will launch the Gmail composing window in the Browser for the user to review or click to send. [+] 2. [Email- Send by Gmail API]: (EmailSendMethod: 14) Add a new method for sending email by Gmail API (OWA OAuth 2.0 authorization) directly. It will not launch the Gmail composing window. It only launches the browser for requesting OAuth 2.0 authorization. When EmailNotSubmit is True, it will save the email into Drafts of the GmailAccount. [+] 3. [Email- EmailGAppID]: Add a registry setting and embedded command EmailGAppID for specifying the App ID (Client ID) for accessing the Google API resources. By default, it is automatically assigned as the registered public Application ID of eDocPrinter Cloud-Addon for Gmail. For a high security level, users may create and use their own registered Google OAuth2 App ID in their organization directory (tenant) for Gmail automation flow. [+] 4. [Email- EmailGAppSecret]: Add a registry setting and embedded command EmailGAppSecret for specifying the App secret (Client secret) for accessing the Google API resources. By default, it is not necessary for Browser based Authorization Code Grant. For a high security level, users may assign their own secret for their own registered Google OAuth2 App in their organization directory. [+] 5. [Email- EmailGPermScope]: Add a registry setting and embedded command EmailGPermScope for specifying the permission scope to request to access Google APIs for granting authorization. The default scope for requesting is https://www.googleapis.com/auth/gmail.modify to allow to compose and send emails by the account authorized. [+] 6. [Email- Send email by Gmail SMTP-TLS XOAUTH2]: (EmailSendMethod: 15) Add a new method for sending email by Gmail SMTP server using XOAUTH2 authentication. (Using the Access Token from OAuth 2.0 Authorization for SMTP authentication.) Gmail SMTP server requires a full permission scope https://mail.google.com/ (EmailGPermScope) for SMTP-TLS XOAUTH2. [+] 7. [FTP/Cloud- Upload by Google Drive]: (FTPMethod: 7) Add a new method for uploading files to Google Drive by Google Cloud API with OAuth 2.0 authentication. [+] 8. [FTP/Cloud- FTPGAppID]: Add a registry setting and embedded command FTPGAppID for specifying the App ID (Client ID) for accessing the Google resources. By default, it is automatically assigned using the registered OAuth2 App ID of eDocPrinter Cloud-Addon for Google Drive. For a high security level, users may create and use their own registered Google OAuth2 Client ID and secret in their organization directory for the uploading automation flow. [+] 9. [FTP/Cloud- FTPGAppSecret]: Add a registry setting and embedded command FTPGAppSecret for specifying the App secret (Client secret) for accessing the Google Cloud resources. For a high security level, users may assign their own secret with their own registered Google OAuth2 Client ID (App ID) in their organization directory. [+] 10. [FTP/Cloud- FTPGPermScope]: Add a registry setting and embedded command FTPGPermScope for specifying the permission scope to request to access Google APIs for granting authorization. The default scope for requesting is https://www.googleapis.com/auth/drive to allow to create folders and upload files by the account authorized. [+] 11. [FTP/Cloud- FTPOverwrite]: Add a registry setting and embedded command FTPOverwrite with default value True. When uploading to Google Drive, if the filename is existing in the upload folder path specified, it will update(overwrite) the file as a new version (google drive will automatically keep the old file by versions). When it is False, it will be uploaded as a new file using the same filename specified and a different Google FileID. In such cases, Google Drive list multiple files with the same filename. ============================================================= 0. Ver 9.64 Build 9649 (Ent. Pack - EPDFENT) [+] 1. [Digital Signature- ]: Add the UI option for selecting the certificate source [Load from the Windows certificate store], [Load from the Smart card/USB token], and [Load from the PFX file] for digitally signing the PDF file. The corresponding registry setting and command is [DestSignCertSrc] with the corresponding value 0/1/2. This option overrides the option [DestSignSmartCard] in Ver 9.54. When set it to 1, it will use the certificate in the smartcard/USB token to digitally sign the PDF file. Some smart cards/USB tokens may require installing its own Windows driver first if the devices are not compatible with Windows built-in drivers. When set to 2 (selecting [Load from the PFX file]), it will use the certificate in the PFX file specified for signing. [+] 2. [Digital Signature- ]: Add the UI option to browse to select the PFX filepath when selecting the mode [Load from the PFX file]. Its registry setting and command is [DestSignPfxPath] for specifying the path of the PFX file for loading the certificate when applying digital signature in the mode [Load from the PFX file]. [+] 3. [PDFSealer UI- ]: Add the UI option for selecting the certificate source [Load from the Windows certificate store], [Load from the Smart card/USB token], and [Load from the PFX file] for digitally signing the PDF file. This UI option replaces the checkbox [Use the certificate directly from the Smart card/USB token] in Ver 9.54. When selecting [Load from the Smart card/USB token], it will use the certificate in the smart card/USB token to digitally sign the PDF file. Some smart cards/USB tokens may require installing its own Windows driver first if the devices are not compatible with Windows built-in drivers. When selecting [Load from the PFX file], it will use the certificate in the PFX file specified for signing. [+] 4. [PDFSealer UI- ]: Add the UI option to browse to select the PFX filepath when selecting the mode [Load from the PFX file]. [+] 5. [Digital Signature- ]: Add the LTV(Long Term Validation) support when digitally signing the PDF file with timestamping by TSA(Time Stamp Authority). The corresponding registry setting and command is [DestSignLTV] with the default value True. By default, when digitally signing a PDF file with timestamping of TSA, the LTV information is included and signed with the document digest to ensure long time validation of the PDF and PDF/A standard. (LTV requires digital signatures with countersigned timestamps) The LTV(Long Term Validation) adds status of validating certificates by submitting OCSP(Online Certificate Status Protocol) requests to the issuer of certificates when signing to ensure the certificate is valid (not revoked) at the time of signing. [+] 6. [PDFSealer UI- ]: Add the LTV(Long Term Validation) support when digitally signing the PDF file with timestamping by TSA(Time Stamp Authority). The corresponding registry setting and command is [DestSignLTV] with the default value True. By default, when digitally signing a PDF file with timestamping of TSA, the LTV information is included and signed with the document digest to ensure long time validation of the PDF and PDF/A standard. (LTV requires digital signatures with countersigned timestamps) The LTV(Long Term Validation) adds status of validating certificates by submitting OCSP(Online Certificate Status Protocol) requests to the issuer of certificates when signing to ensure the certificate is valid (not revoked) at the time of signing. [+] 7. [PDFSealer UI- ]: Add a registry setting SigSaveUpdate with default value True. When it is True, the PDF is incrementally updated when stamping the digital signature for supporting to countersign by multiple people in the workflow. (DestSignUpdate) [!] 8. [Digital Signature- ]: The registry setting and command DestSignCertPasswd is also used for modes [Load from the Smart card/USB token] and [Load from the PFX file] mode for workflow automation. [+] 9. [Email- EmailBrowserProfileEmail]: Add a registry setting and embedded command EmailBrowserProfileEmail for specifying the browser profile to launch for granting authorization or showing web composing UI in sending emails by OAuth 2.0 web or API (Outlook 365 Web App). In Edge browser, the email address is usually the Microsoft personal/work account signing in the browser for syncing Microsoft 365. In Chrome browser, it is usually the Google Account email address for signing in Chrome. [+] 10. [Email- EmailBrowserProfileByFrom]: Add a registry setting and embedded command EmailBrowserProfileByFrom with the default value False. When it is True, it will use the email address specified by EmailFrom for the the browser profile to launch for granting authorization or showing web composing UI as described by the command EmailBrowserProfileByFrom. [+] 11. [Email- EmailBrowserProfileDir]: Add a registry setting and embedded command EmailBrowserProfileDir for specifying the profile directory to launch for granting authorization or showing web composing UI. For Chromium based browsers (Chrome/Edge), it is the physical directory name for storing the browser profile data. It is not the profile name(alias) showing in the browser title or toolbar. It is only effective when EmailBrowserProfileEmail is empty or not specified. EmailBrowserProfileEmail is recommended for launching browser with the profile. [+] 12. [Email- EmailBrowserSwitches]: Add a registry setting and embedded command EmailBrowserSwitches for specifying extra arguments/parameters launch the browser for granting authorization or showing web composing UI. [+] 13. [Email- EmailOAuth2Cache]: Add a registry setting and embedded command EmailOAuth2Cache with the default value True for caching and refreshing the OAuth 2.0 authorization token. [+] 14. [Email- EmailOAuth2ReAuth]: Add a registry setting and embedded command EmailOAuth2ReAuth with the default value False. When it is True, it will submit a new request to ask for granting authorization by OAuth 2.0 without using cached info. [+] 15. [FTP/Cloud- FTPBrowserProfileEmail]: Add a registry setting and embedded command FTPBrowserProfileEmail for specifying the browser profile to launch for granting authorization when uploading PDF files or related data by OAuth 2.0 API (e.g. OneDrive). In Edge browser, the email address is usually the Microsoft personal/work account signing in the browser for syncing Microsoft 365. In Chrome browser, it is usually the Google Account email address for signing in Chrome. [+] 16. [FTP/Cloud- FTPBrowserProfileByFrom]: Add a registry setting and embedded command FTPBrowserProfileByFrom with the default value False. When it is True, it will use the FTPUserName as the email address for launching the browser using the profile matching the email for granting authorization. [+] 17. [FTP/Cloud- FTPBrowserProfileDir]: Add a registry setting and embedded command FTPBrowserProfileDir for specifying the profile directory to launch for granting authorization for uploading. For Chromium based browsers (Chrome/Edge), it is the physical directory name for storing the browser profile data. It is not the profile name(alias) showing in the browser title or toolbar. It is only effective when FTPBrowserProfileEmail is empty or not specified. FTPBrowserProfileEmail is recommended for launching the browser with the profile. [+] 18. [FTP/Cloud- FTPBrowserSwitches]: Add a registry setting and embedded command FTPBrowserSwitches for specifying extra arguments/parameters launch the browser for granting authorization for uploading. [+] 19. [FTP/Cloud- FTPOAuth2Cache]: Add a registry setting and embedded command FTPOAuth2Cache with the default value True for caching and refreshing the OAuth 2.0 authorization token for cloud uploading. (e.g.OneDrive) [+] 20. [FTP/Cloud- FTPOAuth2ReAuth]: Add a registry setting and embedded command FTPOAuth2ReAuth with the default value False. When it is True, it will submit a new request to ask for granting authorization by OAuth 2.0 without using cached info. ============================================================= 0. Ver 9.59 Build 9596 (Pro. Pack - EPDFPRO) [+] 1. [Dest- SaveAs Dailog]: In Win10/11 Common Item SaveAs Dialog mode (DestSaveDlgStyle=0), DestSaveDlgTop is supported to set the SaveAs dialog prompted with TOPMOST style. Its default values is True. (When DestSaveDlgStyle=1, it uses the traditional Explorer-style SaveAs dialog). [+] 2. [Dest- SaveAs Dailog]: In Win10/11 Common Item SaveAs Dialog mode (DestSaveDlgStyle=0), DestSaveDlgFocus is supported to set the SaveAs dialog prompted with FOCUS. Its default values is True. (When DestSaveDlgStyle=1, it uses the traditional Explorer-style SaveAs dialog). 0. Ver 9.58 Build 9588 (Ent. Pack - EPDFENT) [+] 1. [PDFSealer- Signature Appearance]: Add a registry setting SigAPFontFamily for specifying the font family used signature appearance. The default is Arial. The font used is, by default, embedded. ============================================================= 0. Ver 9.54 Build 9549 (Ent. Pack - EPDFENT) [+] 1. [Digital Signature- ]: Add the UI option [Use the certificate directly from the Smart card/USB token] for digitally signing the PDF file. The corresponding registry setting and command is [DestSignSmartCard]. When it is True, it will use the certificate in the smart card/USB token to digitally sign the PDF file. Some smart cards/USB tokens may require installing its own Windows driver first if the devices are not compatible with Windows built-in drivers. [+] 2. [PDFSealer UI- ]: Add the UI option [Use the certificate directly from the Smart card/USB token] for digitally signing the PDF file. When it is turned on, it will use the certificate in the Smart card/USB token to digitally sign the PDF file. Some smart cards/USB tokens may require installing its own Windows driver first if the devices are not supported by Windows built-in drivers. [+] 3. [PDF Renderer- ]: Add a registry setting and command [PDFRenderMode] to support rendering the static annotations of the PDF file. The default is 0, the annotations will be rendered(printed) with the PDF content. When the value is 1, it will omit rendering the annotations. [+] 4. [PDF Renderer- Drag2PDF, Redirect2Print]: Support [PDFRenderMode] in the workflow when using PDF-Renderer from Drag2PDF or Redirect2Print. (Pro. Pack - EPDFPRO) [+] 1. [Email- Outlook]: Add a timeout for waiting local Outlook.exe to launch when sending by Outlook client in thunking mode. (automate 32bit Outlook in 64bit Windows) (same as DestJobTimeout) ============================================================= 0. Ver 9.47 Build 9477 (Ent. Pack - EPDFENT) - Timestamped Digital Signature by PDFSealer [+] 1. [Digital Signature- ]: Support adding a trusted timestamp when digitally signing the PDF file. The timestamp is countersigned by the public Time Stamp Authority (TSA) server. It requires an internet connection to the the public Time Stamp Authority (TSA) server when requesting the timestamp. The default timestamp server is set to http://timestamp.digicert.com. [+] 2. [Digital Signature- ]: Add UI options in the digital signature (PDFSealer) option dialog for turning on or off for adding timestamps and assigning the URL of the Time Stamp Authority (TSA) server. [+] 3. [Digital Signature- ]: The registry settings and embedded commands DestSignTimestamp and DestSignTSAServer are added for the correponding UI options for enabling adding timestamps and the URL of the Time Stamp Authority (TSA) server. [+] 4. [PDFSealer UI- ]: Support adding a trusted timestamp when digitally signing the PDF file. The timestamp is countersigned by the public Time Stamp Authority (TSA) server. It requires an internet connection to the the public Time Stamp Authority (TSA) server when requesting the timestamp. The default timestamp server is set to http://timestamp.digicert.com. [+] 5. [PDFSealer UI- ]: Support DPI awareness check for high-resolution DPI screen or custom scaling of Remote desktop sessions (SetProcessDpiAwareness). [!] 6. [PDFSealer UI- ]: Set the default resource font to Windows [MS Shell Dlg]. [!] 7. [Digital Signature- PDF internal]: Set the default Filter name to PPKLite (SHA-256, SHA-384, SHA-512) for compliance with the PDF standard. [!] 8. [Digital Signature- Resources]: Update the resources for the timestamp options. [!] 9. [Digital Signature- Certificates]: Set the attribute cryptographic service provider (CSP) of the generated self-signed certificate to Microsoft Base Cryptographic Provider. ============================================================= 0. Ver 9.36 Build 9368 (Ent. Pack - EPDFENT) - PDF-Renderer for direct rendering the job PDF to physical printers and images files [+] 1. [PDF Renderer- ]: Support rendering the current job PDF to image files (->TIF, ->TIFG3, ->JPG, ->BMP) directly from Redirect2Print by the PDF Renderer Addin. (RedirectPrintMode: 3) (Ent. Pack Licenses required) [+] 2. [PDF Renderer- ]: Support rendering the current job PDF overlaying with the PDF template to image files (->TIF, ->TIFG3, ->JPG, ->BMP) directly from Redirect2Print by the PDF Renderer Addin. (RedirectPrintMode: 3) (Ent. Pack Licenses required) [+] 3. [PDF Renderer- Drag2PDF]: Support rendering generated job PDF files or processed PDF files to image files (->TIF, ->TIFG3, ->JPG, ->BMP) directly from Redirect2Print (RedirectPrintMode: 3) of the Drag2PDF application by the PDF Renderer Addin. (Ent. Pack Licenses required) 0. Ver 9.35 Build 9355 (Ent. Pack - EPDFENT) [+] 1. [PDF Renderer- ]: Add the built-in PDF renderer addin. (Render PDF directly on Device Contexts without calling external PDF readers). [+] 2. [PDF Renderer- ]: Support rendering the current job PDF onto Printer Device Contexts (PrinterDC) directly from Redirect2Print by the PDF Renderer Addin. (RedirectPrintMode: 3) (Ent. Pack Licenses required) [+] 3. [PDF Renderer- ]: Support rendering the current job PDF overlaying with the PDF template onto Printer Device Contexts (PrinterDC) directly from Redirect2Print by the PDF Renderer Addin. (RedirectPrintMode: 3) (Ent. Pack Licenses required) [+] 4. [PDF Renderer- Drag2PDF]: Support rendering generated job PDF files or processed PDF files onto Printer Device Contexts (PrinterDC) directly from Redirect2Print (RedirectPrintMode: 3) of the Drag2PDF application by the PDF Renderer Addin. (Ent. Pack Licenses required) [+] 5. [PDF Renderer- Redirect2PDF]: Support the page scaling modes [Fit to paper size] and [Shrink to paper size] in Redirect2PDF by the PDF Renderer Addin. ============================================================= 0. Ver 9.01 Build 9017 (Ent. Pack - EPDFENT) - Cloud uploading to OneDrive with OAuth 2.0 [+] 1. [FTP/Cloud- Upload by OneDrive (Work Account)]: (FTPMethod: 5) Add a new method for uploading files by OneDrive (Work Account) (OAuth 2.0 authorization). [+] 2. [FTP/Cloud- Upload by OneDrive (Personal Account)]: (FTPMethod: 6) Add a new method for uploading files by OneDrive (Personal Account) (onedrive.live.com) (OAuth 2.0 authorization). [+] 3. [FTP/Cloud- FTPO365TenantType]: Add a registry setting and embedded command FTPO365TenantType for specifying Office 365 Account type. [0: common, 1: organizations i.e. work accounts, 2: consumers i.e. personal account]. It is determined automatically in FTPMethod 5,6. [+] 4. [FTP/Cloud- FTPO365TenantID]: Add a registry setting and embedded command FTPO365TenantID for specifying the Tenant ID (Directory ID) of the Office 365 Account for supporting custom AppID. [+] 5. [FTP/Cloud- FTPO365AppID]: Add a registry setting and embedded command FTPO365AppID for specifying the App ID (Client ID) for accessing the Office 365 resources. By default, it is automatically assigned as the registered public Application ID of eDocPrinter for Office 365 Automation. For a high security level, users may create and use their own registered Azure App ID in their organization directory (tenant) for uploading automation flow. [+] 6. [FTP/Cloud- FTPO365AppSecret]: Add a registry setting and embedded command FTPO365AppSecret for specifying the App secret (Client secret) for accessing the Office 365 resources. By default, it is not necessary for Browser based Authorization Code Grant. For a high security level, users may assign their own secret for their own registered Azure App in their organization directory (tenant). [+] 7. [FTP/Cloud- FTPOAuth2Browser]: Add a registry setting and embedded command FTPOAuth2Browser for specifying the Browser type to use for granting authorization. [0: default, 1: Edge browser, 2: Chrome browser] The default is launching the built-in Edge browser for OAuth 2.0 authorization. [!] 8. [FTP/Cloud- ]: Update resources ============================================================= 0. Ver 9.00 Build 9009 (Ent. Pack - EPDFENT) - Email by OWA (Outlook 365 Web App) with SMTP-XOAuth2/Web OAuth2 [+] 1. [Email- Send by Office 365 SMTP BASIC]: (EmailSendMethod: 7) Add a new method for sending email by Office 365 SMTP server with BASIC authentication (AUTH LOGIN). [+] 2. [Email- Send by Office 365 SMTP XOAUTH2]: (EmailSendMethod: 8) Add a new method for sending email by Office 365 SMTP server with XOAUTH2 authentication (OAuth 2.0 Access Token). [+] 3. [Email- Send by Outlook Web App (Work Account)]: (EmailSendMethod: 9) Add a new method for sending email by Office 365 Outlook Web App (OWA OAuth 2.0 authorization). It will launch the OWA composing window in the Browser for the user to review or click to send. [+] 4. [Email- Send by Outlook Graph API App (Work Account)]: (EmailSendMethod: 10) Add a new method for sending email by Outlook Graph API (OWA OAuth 2.0 authorization). [+] 5. [Email- Send by Outlook Web App (Personal Account)]: (EmailSendMethod: 11) Add a new method for sending email by Outlook Web App (outlook.live.com) (OWA OAuth 2.0 authorization). It will launch the OWA composing window in the Browser for the user to review or click to send. [+] 6. [Email- Send by Outlook Graph API App (Personal Account)]: (EmailSendMethod: 12) Add a new method for sending email by Outlook Graph API (outlook.live.com) (OWA OAuth 2.0 authorization). [+] 7. [Email- EmailO365TenantType]: Add a registry setting and embedded command EmailO365TenantType for specifying Office 365 Account type. [0: common, 1: organizations i.e. work accounts, 2: consumers i.e. personal account]. It is determined automatically in EmailSendMethod 9,10,11,12. [+] 8. [Email- EmailO365TenantID]: Add a registry setting and embedded command EmailO365TenantID for specifying the Tenant ID (Directory ID) of the Office 365 Account. [+] 9. [Email- EmailO365AppID]: Add a registry setting and embedded command EmailO365AppID for specifying the App ID (Client ID) for accessing the OWA resources. By default, it is automatically assigned as the registered public Application ID of eDocPrinter for Outlook Web App. For a high security level, users may create and use their own registered Azure App ID in their organization directory (tenant) for OWA automation flow. [+] 10. [Email- EmailO365AppSecret]: Add a registry setting and embedded command EmailO365AppSecret for specifying the App secret (Client secret) for accessing the OWA resources. By default, it is not necessary for Browser based Authorization Code Grant. For a high security level, users may assign their own secret for their own registered Azure App in their organization directory (tenant). [+] 11. [Email- EmailOAuth2Browser]: Add a registry setting and embedded command EmailOAuth2Browser for specifying the Browser type to use for granting authorization. [0: default, 1: Edge browser, 2: Chrome browser] The default is launching the built-in Edge browser for oauth2 authorization and OWA (Outlook Web App) email composing. [!] 12. [Email- ]: Update resources