Fabasoft Cloud 2020 June Release
Find out more about new features and improvements in the Fabasoft Cloud 2020 June Release.
As end user you can expect the following new features.
To digitally sign documents, the following options are available (Enterprise and higher only).
- If your cloud organization does not have its own organization certificates or no certificate has been released for you to use, you can use a certificate provided by Fabasoft for signing. This enables you to confirm that the document has not been changed since it was signed.
- If your cloud organization has organization certificates that have been released for you to use, you can use them for signing. This enables you to confirm that the document has been signed by an authorized person and has not been changed since then.
- To apply a digital signature to a PDF document, click “Sign Digitally” in the context menu of the PDF document. In the workflow the corresponding activity “Sign Digitally” is available.
- In addition to the digital signature, you can apply a visual signature to the PDF document.
- Your visual signatures can be found under “account menu (your user name)” > “Advanced Settings” > “My Signatures”. You can also add or remove signatures here. You will see the organization certificates that have been released for you to use.
- To digitally sign the PDF documents of a folder, click “Sign Digitally Documents” in the context menu of the folder. In the workflow the corresponding activity “Sign Digitally Documents” is available.
- When a new window should be opened (e.g. via the “Open in New Window” context menu command), the web browser setting is considered whether a tab or a window should preferably be opened.
- Drag and drop import of multiple files and folders is now possible in all supported web browsers.
Administrators, Process and Form Designers
As administrator, process or form designer you can expect the following new features.
You can adapt the Fabasoft Cloud to your requirements by means of model-based customizing (Enterprise and higher only).
Note: The former “Template Management” is now part of the “Customizing”. The “Template Management” dashboard has been renamed to “Templates and Presettings”.
Here you will find a brief overview of the customization options available to you.
Nearly all objects and especially documents can be defined as templates. In this way new objects or documents based on a template can be created.
- Text Modules
You can use text modules to insert predefined standard texts into Microsoft Word documents.
User-defined forms can be used to add fields to objects for storing application-specific data. To apply logic or specific behaviors to the fields, Fabasoft app.ducx expressions can be used.
Categories can be assigned to objects and thus influence the behavior of the objects.
Processes can be individually defined reflecting your business and organizational structure. BPMN process diagrams are used to design executable business processes. Beside predefined BPMN processes, ad hoc processes can be started as needed.
- Display Settings
Predefined display settings can be provided to users who need special views on lists.
- Search Forms
Predefined search forms can be provided to users who need an overview of currently existing objects based on defined search criteria.
Customizations are managed at different levels:
Organization-wide customization is done by defining customizing collections in the “Templates and Presettings” dashboard.
Note: Organization-wide BPMN process diagrams, forms and categories are not available in an app context by default. If these customizing objects have to be available in an app context, they must be explicitly referenced in the app configuration or in the app room.
In apps, such as the contract manager, you can make customizations in the app configuration that are only valid within the app configuration context.
In rooms (e.g. app rooms or Teamrooms), customizations can be made that are only valid within the room context. You can access the customizing objects via the “Templates and Presettings” action.
Personal customizations can only be used by the users themselves. The following customizing objects can be managed at the personal level: templates, ad hoc process templates, display settings and search forms.
Release of Customizing Objects
In order to use customizing objects, they must be released for usage depending on the context.
- Customizing objects must be released if they are assigned to a customizing collection or an app configuration.
- Forms and BPMN process diagrams must also be released if they are assigned to a room.
- Personal customizing objects do not have to be released.
Actions and Context Menu Commands
The actions are available to administrators and processors of a customizing collection (organization level) or app administrators (app level).
- Release for Usage
You can create a release version using the “Release for Usage” action.
Changes can be released using the “Re-Release” action.
- Withdraw Release
You can use the “Withdraw Release” action to withdraw the release.
In app configurations or customizing collections, you can define a release process in the settings, on the “Default Values” tab, in the Release Process for Templates and Presettings field. Release processes must contain the “Release for Usage” activity.
If a release process is defined, the following actions or context menu commands are offered:
- Start Release Process
Starts the defined release process.
- Open Current Release Process
Opens the release process that is not yet completed.
- Start Release Process Again
Restarts the release process (is only displayed when the current release process is completed).
To ensure that the existing templates and presettings continue to work as expected, they are migrated automatically. Further information can be found in the white paper “Release and Migration of Customizing Objects”:
As administrator you can expect the following new features.
Configuration of Digital Signatures
To enable the digital signing of documents with own certificates, you must store the corresponding certificates in your organization (“Advanced Settings” > “Configure Digital Signatures” action). In addition, you can specify which organization members are allowed to sign digitally with the certificates.
Note: If the use of X.509 certificates is restricted, one of the following usage types (“Key Usage”) is required: “Digital Signature” or “Non Repudiation”.
Configuration of the Login via Active Directory or SAML 2.0
Now you can configure the login via Active Directory or SAML 2.0 by yourself.
To do this, you need to configure your login server on the one hand and make settings in your cloud organization on the other. You can find a detailed description in the administration help: