...
You would like to update your primedocs version? Our support team will be happy to assist you.
...
4.0.20130.0 (2024-02-06)
Client
- Outlook: In the "Organization" tab, the "Signature" button now takes you to a dialog where you can add signature rules.
- Global configurations: The width of the second column can now be customized by users and is saved.
- Client & Server: The new document function "Data" can now be used to integrate data from external systems in primedocs templates (primedocs Connect).
- Generating a template of the type "External file for distribution" resulted in an error message.
- Outlook: Templates of the type "Signature" were displayed even outside of the administration view.
- Outlook classic: Various template types for classic Outlook were labeled as such.
- Template distribution in connection with MailThemes has been optimized.
- If the "All users" button was selected in an authorization dialog, "Authenticated users" is now always displayed afterwards.
- Signature profiles that have been approved with the option "May use me as co-signer, but without signature image" are now correctly only available for selection in the additional profiles, but not in the profile selection/profile change in the client or in the AddIn.
- Diagram templates (*.crtx) for "Doughnuts" can now be imported correctly in templates of type "Diagram".
- Creating a mail with the "XmlSpy" program now works again.
- When opening the Word editor of a template multiple times, new changes to the template were no longer applied after saving in Word.
- The "Microsoft.WindowsDesktop.App" framework is now required on the server side.
AddIns
- Connect: Updating a document generated with Connect displayed an error message if ObjectCollections via Fields were in the document.
- The snippet dialog now allows 256 instead of 32 characters to define a key.
- Snippets of the type "FormattedText" could no longer be inserted by double-clicking after creating the snippet.
- An exception has been corrected in PowerPoint/Excel 2016 Pro when creating a new file.
- In the profile selection dropdown, up to 10 third-party profiles are now displayed next to pinned profiles.
Word AddIn
- If the header in a template contained a table and the last element in a table cell was a content control, a profile change in the open document resulted in an error message.
- If a WordContent snippets contained a table in the first position, updating the open document failed and resulted in an error message.
- Content controls no longer lose their style when the document is updated and no longer receive an additional paragraph.
- If a WordContent snippets contained a style in the last paragraph, an additional paragraph was inserted when inserting the WordContent into a document. This has been fixed.
- If a former primedocs document (a primedocs document that has been finalized) is linked to primedocs again, the appearing error message now no longer contains any old information.
PowerPoint AddIn
- Inserting a SmartArt object into a PowerPoint and then changing the fill color, resulted in an error message.
- Displaying a PowerPoint in a slide show and then clicking on the display settings, resulted in an error message.
- The "Template editing" group in the ribbon has been better organized because the button names were too long.
- The template of type "Table of Contents" can now be built better.
Outlook-AddIn
- It is now possible to create signature templates, manage multiple signatures depending on the organizational unit (via the "Signatures" button in the "Organizational unit" tab) and then use them in the new Outlook version.
App
- Outlook: An error message in connection with Connect has been fixed.
- Templates were no longer displayed when switching to a different database and could therefore no longer be generated.
Engine
- In fields, it is now possible to access the result of another WordContent or FormattedText field via
$.getWordContent or $.getFormattedText respectively, in the same way as $.getText. - For various built-in styles in Word, e.g. "header" and "footer", various problems in connection with WordContent and FormattedText have been solved. Among other things, all snippets are now "de-localized" (same process as for style templates).
- When validating the Fields document function during document generation now recognizes whether two fields with the same name are configured.
In Fields, dates are now handled differently:
- Using
$.formateDate(myFormsDate, "dd.MM.yyyy"), you can now alternatively format date objects from Forms. - The date value of a date is now accessed using
Value (e.g., $("Forms.Date").Value) Together with the functions $.getDate() and$.setDate(), this now allows you to calculate with dates.
Admin Dashboard
- Importing packages caused a problem when sorting template groups.
- Importing databases created with a version lower than 4.0.20121 via Smuggler did not work. This has been fixed.
Other
- WebAPI/AdminUser: The URL for organizational units was incorrect.
- Authorizing an organizational unit and removing these authorizations again, resulted in an error message. This also happened via JobHost.
- Service: The synchronization from the client to the database failed if a snippets was overwritten.
Dev: Updated to new version of AvalonEdit and Azure.Identity
4.0.20113.0 (2023-12-17)
Client
- Word: Two error messages appeared when dealing with mail merges, which have now been corrected.
- Outlook:
If an e-mail template was generated using the client, primedocs and Outlook crashed.
E-mail templates could no longer be generated using the client.
Opening the recipient dialog from an e-mail led to errors.
- If a global translation was created as FormattedText and the entry contained a lot of text, performance problems occurred.
- Forms: the
ValidationMessage attribute has been updated in the technical documentation.. - Forms: If the
Info element was configured without text and TranslateKey, an unclear error message was displayed. This has been improved. - The new template type "PowerPoint table of contents" is now displayed correctly in clients with German UI language.
AddIns
- Word: The data that had been entered in an
Object in Forms was no longer loaded in the open document after a profile change. - Word: WordContent snippets with more complex style applications could not be created.
- Word: Additional properties can now be used in WordContent (br; Break, multiLine; SdtContentText, SpacingBetweenLines, rStyle, hanging und ind; Indentation, tblPrEx; TablePropertyExceptions).
- Excel: The "+ Sheet" button to create a new Excel sheet threw an error if a cell was edited at the same time.
- Excel & PowerPoint: The error with the message "An element with the same key has already been added" has been fixed.
- PowerPoint: The feature for creating PowerPoint templates for tables of contents has been enhanced.
- PowerPoint: The "Change layout" button could not be used in the ribbon.
- PowerPoint: If a PowerPoint template is adjusted to the CI/CD by means of design conversion, the dialog now fills recognized properties into the correct form fields.
App
- On iOS, the upload button extended to the edge and thus overlapped text fields.
- Messages for information and errors are now highlighted in color.
Admin Dashboard
- In the Policy Editor, the back button no longer took you to the previous page.
- The database import via Smuggler did not import changes of permanently deleted objects.
- The package import did not import the metadata for modification times (ModifiedBy and ModifiedOnUtc) of templates. As a result, imported templates still had the old timestamp.
...
- The IdentityServer license key is integrated by default, but can now be explicitly overwritten via the configuration.
- The installation script has been changed.
4.0.20101.0 (2023-11-17)
Client
- Outlook: There is now the new template type "Email template" (the classic version is now called "Email (classic)"). This means that it is now possible to implement e-mail templates on the web and via Outlook in the new design.
- Forms: With the new
AdditionalProfile element, it is now possible to store signatures and signatures from external profiles in a template in the profile. User-defined names can be used (e.g. "Signer" and "CoSigner"). - If you go to the advanced search dialog by clicking on the arrow to the right of the search field, you can now search all document functions in all templates in the new "Configuration" text field (e.g. the search with the search term "Forms.MyTextField" shows all templates that contain this text in any document function).
- Word-Ribbon:
Preview images can now be generated when testing a document by clicking on "Generate preview" or "Generate multilanguage previews" for language-dependent preview images in the primedocs ribbon in the "Templating" group.
In the ribbon Developer tools, group "Templating" you get to the dialog "Developer tools". There is now a new tab "DocData - WordStyles", which lists all StyleIds and StyleNames. This is useful for using FormattedText and FormattedText translations to look up the correct StyleId.
- Forms:
If you created an Info element without text and without translation, an exception was thrown in the editor and the document could not be generated. Now at least one of the two must be filled out in Info.
If you created an AdditionalProfile without a label, an exception was thrown in the editor and the document could not be generated.
The dialog ignored different screen resolutions for display. Now it is scaled correctly.
In the Group, the Translate-Title attribute now shows the available translations.
- UI: In the dialog for managing third-party profiles, it is now better displayed whether a third-party profile is pinned or not.
- The address provider "Nest" has been renamed to "innosolv" in the UI.
- PowerPoint: If an empty placeholder for text was placed in a master template, it lost its formatting when the presentation was generated.
- Templates of the type "PowerPoint slide set template" could not be opened in the editor without mapping. This has been fixed.
- PowerPoint: Performance has been improved when typing and switching slides.
AddIns
- PowerPoint: The button for generating a table of contents is now only displayed if the corresponding PowerPoint table of contents template exists.
- Word: If the Word template is open and you create a new field in the Fields document function and save this, this new field is now automatically visible in the field list of the template - without having to close and reopen the template!
- PowerPoint: The "Check slide" and "Design Conversion" functions are now displayed in the same group in the UI.
- PowerPoint: Users can now have tables of contents created automatically in PowerPoint, with primedocs searching for the slide headings and specifying the corresponding number of slides.
- Word (classic): If you clicked on "Change signature", nothing happened. This function now works again.
- Word Ribbon-UI: The buttons for switching back and forth between recipients now have clearer icons.
- Word: More properties can now be used in WordContent (rsidRPr; TableRow, ascii/hAnsi; RunFonts).
- Word/FormattedText: If the document was updated, new paragraphs were inserted in FormattedText fields.
- Word/FormattedText: If the document was updated (e.g. via confirming the properties dialog or changing the profile), some styles were lost.
- Word: If a Forms field of type
AdditionalProfile was in a group, it was not possible to access the properties dialog again in the generated document.
...
- Forms fields of type
AdditionalProfile can now be queried in Fields via let profile = ("Forms.MeinAdditionalProfile");. In this way, it is now possible to find out whether the user has selected a profile in the Forms dropdown or not (("Forms.MyAdditionalProfileMyAdditionalProfile) !== null). - As soon as a FormattedText field was in a table, the specified style no longer applied correctly.
- If a FormattedText field was in a table cell and its content was a string "", Word could no longer handle it and the document could not be generated.
- A FieldBuilderStep timeout error has been fixed.
FormattedText translations
- Error messages for FormattedText translations (handlebars) are now displayed in as many cases as possible with a concrete reference to the corresponding field.
- Handlebars in the form of "{{{" may not be used.
- The attribute
word-style-id did not work with built-in styles. - Builder API: with the
hasContent property in FormattedText translations, the content in the handlebar control structure ({{ if meineVariable.hasContent }}) is only inserted if the parameter in the JavaScript code is a FormattedText and not empty ("").
JavaScript:
- JS error messages are now output in as many cases as possible with a concrete reference to the corresponding field.
- The function
$.wordContent.fromFormattedText() only accepted string literals and no references to variables. This has been corrected. - The function
$.formattedText.fromText("MeinText") no longer generates too many paragraphs. - With the new Builder API, different fields or field types (Text, FormattedText and WordContent) can now be strung together. Example in a FormattedText field:
$.formattedText.getBuilder().append($.formattedText.fromText("MeinText")).append($.translations.getFormattedText("MeineFormattedTextÜbersetzung")).build(); - If a
Key was specified for a WordContent or FormattedText snippet, this must now be a string literal in the code.
- FormattedText Troubleshooting
Breaks in a string were ignored in FormattedText. The function $.formattedText.fromText("Oben\nUnten"), which converts Text to FormattedText , now ensures that breaks are still retained in FormattedText.
JavaScript: A call to a function that can optionally be given parameters was still invalid without parameters.
Depending on the HTML in the FormattedText translation, the Word file was then incorrect.
Word: in HTML, the nesting of underline, italic and bold was not recognized correctly.
PowerPoint: in HTML, nesting, e.g. of italics and bold, was not converted correctly.
The attributes of shared profiles (AdditionalProfiles) could not be used in fields.
Control elements of type SdtContent in continuous text are now supported.
- Steuerelemente vom Typ
SdtContent im Fliesstext werden nun unterstützt.
App
- Shared profiles (
AddionalProfiles) are now also available in primedocs basic. This means that the user can now generate a document in the name of another person via the app. - The signature profiles are now displayed under "Additional profiles" in the profile settings.
- Forms: Unfilled mandatory fields were still invalid despite being filled in, which is why documents could not be generated.
- The UI of the Windows update page ignored that an update was available. This has been fixed.
Admin Dashboard
- Different UI languages were used for the template statistics and the template data. Now both files are in the standard UI language.
- The package export threw an error when navigating/exporting snippets.
...
- The
HttpSync threw an error when the synchronization was already running.
4.0.20082.0 (2023-10-24)
Client
- AssetGallery: File extensions are now also allowed in upper case; ".PNG" now works.
- Editing a global translation entry of type Formatted Text became very slow for longer content. This has been corrected.
- The user experience to the “Search signature profiles” dialog has been improved as the window could move to the background.
- In the “Select Organizational Unit” dialog, all organizational units were displayed twice.
- In all XML editors, if the editor was zoomed in other than 100%, an input of "0" incorrectly reset the zoom level. This has been fixed.
- French translations have been improved.
- Deleting a layout when other editor windows were open caused the application to crash.
- AddIn: The message that an update is available is now no longer displayed in the client in a terminal server environment.
- Forms: If an
Object/ObjectCollection was in a Group, there were problems when generating the document.
Admin Dashboard
- The irrevocable deletion of organization fields (hard deletion) threw an exception if there were fields based on this field containing binary data.
- The migration step
20230831090235_AddVarcharListTableType could cause errors. - Package import: Template groups are now not sorted differently after import than in the source.
...
- There were various bug fixes in the Global Configurations.
- FormattedText: The feature has been extended.
FormattedText is now supported as a parameter as well as handlebars ({{object}}), parameters are validated and illegal HTML characters are automatically corrected. - Fields: In JavaScript, the correct use of API objects under "$" is now ensured.
- Global configurations are now also possible in primedocs templates for all document functions: Forms, Fields, Placeholder Assignment, Placeholder Definition.
- Forms: The use of the
Info element caused an error during generation.
App
- The OnPrem version now ships with the correct files, so client download can be easily enabled via primedocs.config.
- Client installers can now also be found in the App and downloaded there. Previously, the packages were only available in the Dashboard.
AddIns
- Performance improvements have been implemented when starting the primedocs client from the add-in.
- List styles are now supported in the WordContent. In addition, an error was corrected in which a WordContent could not be created if a list style was in the document.
- When clicking checkboxes, an error message occurred in Word.
...
- The creation of snippets with invalid FormattedText.elements led to an "exception" in the log.
- When inserting a snippet via double-click or drag 'n' drop into a document, an additional empty paragraph was inserted. This has been fixed.
- An exception file is now no longer saved under "C:\".
- The client can now better handle opening the same window several times.
- Forms: The document function now offers the creation of one Forms element depending on another with
ElementsIf. This is offered in YesNo & Choice and is currently only supported in primedocs pro.
Admin Dashboard
- User Onboarding: Multiple users can now be created by entering their SID via Security → New User; Create button → Bulk User Setup.
- More logging is now done during a SID migration.
- When importing a database, there was sometimes an error due to snippet migrations.
App
- The profile picture is now displayed in the top right corner of the app.
- Forms: Creating one Forms element to depend on another is currently being tested for implementation in the app.
- UI: When generating a document whose Forms contains an object, the "Delete" button was not displayed in the intended section.
...
- An individual table row height is now supported in a WordContent snippet.
- There is now a new text module type "Word Open XML" text modules. This type is similar in principle to the conventional text modules and is used to compose a generated document dynamically, according to selections in Forms.
- Using WordContent snippet via Fields has been implemented.
- The
DefaultDocumentLanguage attribute is now used in the Java Script Field Engine in the SnippetsObject. - There is now a new snippet type called "FormattedText". This way, a global translation of the type "Formatted Text" can be created and used in Fields. HTML can be used to format a text accordingly (e.g., bold). On the other hand, an already formatted text can be created in the open document like an ordinary snippet and then referenced in the fields. This snippet type is mainly used for short texts. The corresponding documentation follows.
Client
- The client crashed when the client tried to add a template to the "recently used templates".
- Foreign templates (e.g. imported PDF) could no longer be created.
- In the client UI, the icon showing the connection status was changed.
- The word read by the screen reader to go back to the client from the primedocs menu was changed to improve accessibility.
- TemplatePicker now displays thumbnails in the specific language.
- Word: When creating text modules, the dialog now displays more information for choosing the correct text module type.
- Word, Snippet groups: in the Snippet properties, the text field "Keyword search" was not saved and synchronized. This has been fixed.
AddIns
- Word, PowerPoint & Excel ribbon position can now be determined via
AddinCommonWordRibbonPosition, AddinCommonPowerPointRibbonPosition as well as AddinCommonExcelRibbonPosition. - Unexpected/invalid values in Word document cause client to crash.
- SendEmail: In a signature, the profile and document language were incorrectly tightened.
- There were errors when creating comments in Word documents.
-
WordContent snippets were extended by tables.
App
- The button to upload a profile picture had too small a clickable area for its size.
- OpenAI Integration:
Look & feel adjustments were made for the "Stop generating" option.
Outlook's prefix space is ignored due to a Microsoft issue.
Query generation did not work in PowerPoint Online.
- In case of a validation error, the "Create" button for generating a document is now inactive.
...
- The template type "External document" was not visible in the client.
- An entry larger than 30MB was not possible in Kestrel operation. This has been resolved.
Admin Dashboard
- User Onboarding: If a user was created via Dashboard, the automatic assignment of the organizational unit was not done.
- The value
0 in ClientSyncMaxDelayAfterStart caused client crash. This value can no longer be set this way in the dashboard and the client validates as well. - Snippets: The UI was fixed because a white ID was hiding the snippet name.
...
- The option
LazyLoadingCache was missing in ADMX. Therefore, new ADMX primedocs templates were added in the docs.
4.0.20053.0 (2023-08-22)
Client
- Manually changed data fields at the profile were reset when there was a change of organisation.
Admin Dashboard
- Save User Data in the SID-Migrator resulted in an error when anything was adjusted among the user fields
App
- When hovering the mouse over "Upload image", no effect was visible.
- The focus at "Reset to default" and "Remove image" was not visible when moving the mouse over it.
...
4.0.20052.0 (2023-08-17)
Client
- Language correction FR and IT: If the template name of a template is not defined in the main UI language, the placeholder "[template name not defined]" now appears instead of "[template name not translated]".
- Export image using arrow key was not available and has now been fixed.
- Template editor: Language check boxes could not be selected and deselected via keyboard.
Admin Dashboard
- Word-style usage evaluation: The Excel formula was supplemented for German Excel.
- 20230421105231_ProfileShareCleanup was deleting permissions for the signature image, which has now been corrected.
...
4.0.20051.0 (2023-08-11)
Client
- With the Lazy Loading Cache feature, snippet and template data can only be loaded when they are used. To activate this, the following switch can be set via the registry or the settings:
| Code Block |
|---|
|
<appSettings>
...
<add key="UseLazyLoadingCache" value="true" />
</appSettings> |
- In the global settings, when editing the configuration of a document function, the selection of an attribute with the integrated XML help crashed.
- Global configurations: Entries of the type "Text"/"FormattedText" can now only be created in the global translations.
- The accessibility has been improved.
- The email accounts set in the signature document function are now filtered better.
- If the user was offline, the document generation failed.
- If Forms consists of a DataProvider, the Simple View now shows that DataProviders can only be edited in the expanded view.
- When logging in with the client for the first time, the message "primedocs cannot be used [...]" was displayed incorrectly, although there was no error.
- If the template name of a template is not defined in the main UI language, the placeholder "[Template name not defined]" now appears instead of "[Template name not translated]".
- AddIn: An "Object" could no longer be removed via the properties dialogue in the primedocs ribbon.
- AddIn: Excel: The button "Convert design" no longer leads to an error.
...
- Fields, JavaScript: The validation of fields used in JavaScript has been improved.
- Fields: An object that is not set is now defined as
null. - If a picture content control was not inserted in Word in a Word layout, primedocs prevented document generation.
Admin Dashboard
- The organisation fields Org.Theme.Color and Org.Theme.Font caused errors when saving any new field in Row 0.
- The SID-Migrator could no longer be accessed
- Smuggler import: If the migration status in the package was different from the one in the database, the import failed.
- The execution of hashing blobs no longer worked.
- In the explanation text of the new Style Usage (Word Style Usage), an explanation text has been improved.
- An old migration step "2018121400003_LibraryItems2Snippets" has been fixed.
...
- The Health Monitor for customers with an OnPrem installation but Cloud Authentication now no longer shows an error for 401.
App
- The app now supports single objects.
- The scaling of the signature image has been improved.
...
- When customizing user or organization fields, synchronization did not always work.
4.0.20031.0 (2023-06-27)
Client
- Word Add-In: for Classic templates, the buttons for "Indent text"/"Indent text" no longer worked for text with standard formatting.
- The Help button in the top right corner of the client as well as in the Word Add-In now leads to help.primedocs.io.
- In the template editor, deleting the name of the template in the default UI language caused a crash.
- In Forms, the "Encrypt" button for encrypting texts was missing in the toolbar.
- The Global Configurations could no longer be loaded: if they were opened via button, only the loading indicator was displayed.
App
- If a profile was not assigned to an organizational unit, a link to that profile led to an error page.
- When hovering over the preview image, it was not adjusted.
- UI: The DatePicker icon that is displayed when selecting a date in Forms got a different color.
- The checkbox to set the default profile is now only displayed for profiles that are not the default profile.
- In Profile Settings, the button to delete a profile is now disabled once the user has only one profile.
- CMI Integration
...
- The path to the JobHost now also supports spaces.
...
4.0.20020.0 (2023-05-30)
Client
- The client backend was significantly improved in terms of color contrasts.
- The DataProvider could not be reached because the URL had been composed incorrectly.
- The new DataProvider can now also be used in Forms in the client.
- If no elements were configured, Forms displayed an error.
App
There was an error when trying to generate documents via the addin.
- In the primedocs app, access from CMI is now also possible.
- In the "Delete Proile" dialog, the text colors of the description were not correct in dark mode.
- Accessibility: The date selection could no longer be exited via tabulator, despite the disappearance of the dialog.
- The new DataProvider can now also be used in Forms of the app.
- Even if there was only one profile, the UI showed a dropdown, just with one entry.
...