d.velop cloud. Here you will find all the news about d.velop cloud, such as new product features, announcements and more.

d.velop cloud.

Find the latest news for d.velop cloud like new features and announcements about upcoming events.

  • "Share batch" functions extended
    admin user
    CategoryIncoming mail
    Published

     


    If you share batches in Inbound, you can now share the batches directly with several people or groups. You can also remove the batch sharing again.

    Please note the following: 

    • Only your administrators can edit standard permissions that are automatically defined by import profile.
    • Neither regular users nor your administrators can remove the user who created the batch from the share.
    • Users can only delete the permissions that they have granted by themselves.
    • You cannot change the permissions for older batches.

    2024-02-13
  • "New operating concept" will be enabled in tasks in the d.velop cloud on 01/26/2024
    admin user


    CategoryTasks and processes
    Publication

    01/26/2024



    New functions available soon

    "New operating concept" will be enabled in tasks in the d.velop cloud on 01/26/2024

    As we announced some time ago in this blog article, we will activate the "New operating concept" in the tasks in the d.velop cloud for all tenants on the afternoon of January 26, 2024.

    As soon as the new version of the tasks is released, the new operating concept is automatically enabled for all tenants in the d.velop cloud.

    You can temporarily disable the new operating concept again. You can find all information on this topic in the blog article.



    All information is supplied without guarantee. Specified functions or dates are subject to change. We reserve the right not to publish certain features if they do not meet our quality standards.

    2024-01-19
  • New features in the Shell app
    admin user

    The new year will also bring exciting changes to the user interface of the Shell app.

    The upcoming changes are the result of a extensive analysis based on valuable feedback from our customers and employees. With these adjustments, we want to meet the needs of our users in the best possible way.

    We are pleased to present the upcoming changes to you. And we still look forward to your valuable feedback in the future.

    We would like to use this blog post to introduce you to three new features that will be rolled out in the cloud in January. The new features will also be available for our on-premises customers with the Current 2024.Q1 version.

    New position for the central menu (nine squares)

    Up until now, you could open the overview of features via a central menu in a dialog. To put the focus on the overview of features, the central menu is now located in a side area.

    Before:

    After:


    New position for the side area of features

    Some features have a side area that you previously opened with the three horizontal lines. To create a stronger connection to the main area of the view, the menu is now located in the top bar. The icon has also changed.

    Before

    After:

    Menu entries combined in one menu

    The entries of the help menu (question mark) and the menu for further information (three vertical dots) have been combined into one menu. This is to create more space for the title.

    2023-12-27
  • Manual process start and using start forms
    admin user


    CategoryTasks and processes
    Publication

    December 2023 / January 2024


    Support of start forms in process modeling

    In the future, you will be able to add a start form to a start element of a process in the process modelling. Using this start form allows you to start the process.

    The following options are available:

    • No form
      • This is the default setting. No start form is used.
    • d.velop forms
      • You can choose a d.velop forms form. The process can be started using the d.velop forms form.
    • External form
      • You can enter the (relative) URI of an external form. The process can be started using the external form.

    When using a start form, the form is provided via a long-term stable URI in the form <base address>/process/processes/<process key>/startForm, which can be integrated into the intranet, for example. Even if the form would change in future process versions, the URI remains the same.


    In order to configure a start form in the process, first select the start form and then select the corresponding form in the section Start form

    Starting processes manually

    Starting a process from d.velop process studio

    In the future, a button for starting a process manually will be available in the process modelling:

    Using the button Start process starts the most recently provided version of the process. If the process uses a start form, the form will be displayed and can be used. If no start form is available, the process will be started immediately, as long as no start variables are configured.

    The button Start process is only enabled if at least one version of the process is provided and the current user is permitted to start the process.

    Starting a process with the context action "Manage processes for the document" in d.velop documents

    In the future, you will be able to configure for a start event if a process can be started with the context action Manage processes for the document in d.velop documents.

    You can easily enable this setting in the configuration section Advanced properties of the start event:


    After the process has been provided, it is available for all documents in d.velop documents with the context action Manage processes for the document:

     


    If the process should not be available for all users, you can limit the usage permissions to certain people or groups. You can use the button Permissions in the process modelling for the limitation. Only the specified people can start the process with the context action.



    All information is supplied without guarantee. Specified functions or dates are subject to change. We reserve the right not to publish certain features if they do not meet our quality standards.

    2023-12-20
  • "New operating concept" for tasks is now enabled by default for all clients
    admin user


    CategoryTasks and processes
    Publication

    January 2024


    New functions available soon

    "New operating concept" for tasks is now enabled by default for all clients

    We have been working for some time on converting the task management to the "new operating concept". For more details, see the following blog articles:

    You could already enable and test the new operating concept for around two years using a preview function. We received a lot of feedback during this time and constantly improved the operating concept.


    With the next cloud release and the next Current version for on-premises, we now want to take the next step and enable the new operating concept for all clients by default. This also removes the corresponding preview function.


    However, you can also disable the new operating concept in the configuration if required.

    This is how it works

    1. Open the configuration of your d.velop documents client.
    2. Navigate to the Tasks and processes area and open the Operating concept entry under Tasks.
    3. Disable Activate new operating concept.
    4. Click on Save.


    Disabling the new operating concept is not a permanent option. The previous operating concept will be completely replaced in a subsequent version.



    All information is supplied without guarantee. Specified functions or dates are subject to change. We reserve the right not to publish certain features if they do not meet our quality standards.

    2023-12-19
  • Introducing permissions in d.velop process studio
    admin user
    Categoryd.velop process studio
    Publication

    December 2023/January 2024



    New global role: Editor

    In addition to the previous global role Administrator, the global role Editor will soon be introduced. You manage the global role Editor, similar to the global role Administrator, for each discipline (processes, business rules, scripts or forms).


    global role: Administratorglobal role: Editor
    Processes/business rulesThe global administrator can model, start, monitor and configure processes, e.g. change the database settings.The global editor can create and import new processes and business rules as part of the modeling process. In addition, as part of process monitoring, the global processor can see the instances of the processes, for which explicit permissions have been granted, and intervene to control the processes. Find more information in the Editing permission for individual processes, business rules, scripts and forms section. 
    ScriptsThe global administrator can create, edit, delete and test scripts and change database settings.The global editor can create scripts and edit, delete and test scripts for which explicit permissions have been granted.
    FormsThe global administrator can create, edit and delete forms and change database settings.The global editor can create forms and edit and delete forms for which explicit permissions have been granted.


    Editing permission for individual processes, business rules, scripts and forms

    When users with the global role Editor create new processes, business rules, scripts and forms, they are automatically added as valid editors. You can also specify for processes, business rules, scripts and forms who may also edit this item. Users with the global role Administrator can configure each item, as the global role Administrator generally has access to all processes, business rules, scripts and forms. Users with the global role Editor can only configure items if they have been granted explicit permissions for the respective item (process, business rule, script and form).

    You can select any person or group as an editor for an explicit process, a business rule, a script or a form.


    Editing
    Processes/business rulesThis person (or any member of the selected group) can edit and deploy the process (or business rule). However, only people with the global roles Process editor or Process administrator are responsible for monitoring a process. 
    ScriptsThis person (or any member of the selected group) can edit, test and execute the script.
    FormsThis person (or any member of the selected group) can edit and access the form.

    When opening the overview of processes, business rules, scripts or forms, users (exception: global role Administrator) only see the items for which they have been explicitly granted permission. 

    If you change the editing permissions, the change takes effect immediately after saving. You do not need to provide the process (or the business rule) again.

    Right of use for individual processes, business rules, scripts and forms

    Currently, processes, business rules, scripts and forms can be used by any logged-in user. From now on, you can define who can use these items for each process, each business rule, each script and each form. By default, every logged-in user can access these processes, business rules, scripts and forms. You can now restrict the right of use to a certain group of people. Define a group of people (individuals or groups). Processes, business rules, scripts and forms can only be used by this group of people.


    Usage
    Processes/business rulesThis person (or any member of the selected group) can start the process.
    ScriptsThis person (or any member of the selected group) can execute the script.
    FormsThis person (or any member of the selected group) can access the form.

    An exception to this is the global role Administrator, which can always start any process, execute any script and access any form.

    External access to forms without authentication

    In addition to managing editing and usage rights, you can also make forms available to external persons without authentication. People who are not part of the organization can therefore access the explicit form.

    2023-12-05
  • Authorizing user accounts for support and consulting now possible
    admin user

    You can now give d.velop employees (later also employees of affiliates) access to your tenant.

    Current status

    Support

    If you report a problem, support staff usually need access to your tenant via Microsoft Teams etc. in order to identify the error.

    Consultants

    User accounts are created for consultants so that they can configure your tenant properly. The consultants can use the user accounts to log in.

    Future status

    You can now make a user account available for support for a limited period of time. You can create, authorize and time-limit technical user accounts for consultants. This ensures that only d.velop employees can use the user account for the planned period of time. A regular login with a technical user account is not possible.

    Logging out a user account causes all user sessions to be logged out. The support staff is logged out when someone logs out of the tenant's shared user account and vice versa. If this happens, you can simply log in again.

    Below you will find an overview of the functions and a FAQ section.

    For employees

    Start

    Open the configuration and search for “Support access". 

    Account access

    Click on Account access to determine who has access to your tenant. You can either give all support employees access to your tenant, or you can select certain d.velop employees (e.g. consultants). You can also specify the duration of access.

    For administrators

    Start

    Open the configuration and search for “Support access".

    Account access

    Click on Account access to determine who has access to your system.

    As an administrator, you can also grant access to other employees. This means you can also grant access to technical user accounts. With technical user accounts, a regular login via login dialog is not possible. Employees of d.velop can only log in via jump host. The technical user accounts should only be used for consulting services, as the technical user accounts are not billed. The login of d.velop employees via e-mail addresses of d.velop will be deactivated in the tenant temporarily.

    Manage support tenants

    Click on Manage support tenants to determine who can grant access. You can also add d.velop affiliates with their own support tenants so they can use the tenant.

    As an administrator, you can define support clients. The default setting is d-velop. You cannot remove the entry. In the future, you will also be able to select clients of the supporting d.velop affiliates.

    Overview of accesses

    Every external access to the tenant is logged. As an administrator, you can view the logged data under Overview of accesses.

    Additional information on the topic

    FAQ

    How long can I grant access to a tenant?

    You can give support staff access to a tenant for up to seven days. If you grant access to specific persons (consultants), access is limited to up to twelve months.

    When does an authorization become invalid?

    As long as the authorization is active in the tenant and the end date has not been reached, the respective persons can log in with the granted access. If you delete the authorization in your tenant, the persons will still have access to the tenant until you log them out or they log out themselves.

    Why does my session sometimes suddenly become invalid so that I have to log in again?

    When you gain access to a tenant, you are using the technical user account with another person at the same time. If someone logs out of the user account, all instances are logged out. This means that your session becomes invalid if the other person logs out of the same user account and vice versa. But you can simply log back in to the tenant directly via jump host.

    Can employees of affiliates also access customer systems?

    Affiliates can request a jump host from d.velop. The jump host is then added to the proposal list and can be activated by you see Manage support tenants).

    What data is logged from the accesses to the tenant?

    Only external access to the tenant is logged. You can use the standard logging mechanisms (Cloudwatch etc.) to track the actions carried out by someone from support or consultants.

    Is it guaranteed that access can only be granted by the customer?

    Yes. If someone logs in to the tenant via jump host, they cannot generate their own authorizations.

    2023-11-30
  • Update: New PDF view in d.velop documents now standard
    admin user

    New features in the PDF view

    The new PDF view is now delivered by default in d.velop documents in the cloud. In addition to several improvements in performance and design, all features of the old PDF view have been adopted. You will also benefit from new features:

    • Drawing arrows
    • Automated saving
    • Selecting and deleting multiple items

    This is how the new PDF view looks like:

    Note: The screenshot has been reduced to the PDF view.

    When will the new PDF view be available?

    The new PDF view is now part of the standard in d.velop documents in the cloud.

    2023-10-27
  • Using actions in process modeling
    user admin
    CategoryTasks and processes
    Published

    October 2023


    New functions available soon

    Using actions in process modeling

    You have been benefiting from the Using scripts as an action feature for some time now. In the future, you can also use these actions in process modeling.

    Why should I use actions?

    Actions represent a standardized interface description of a function or a discipline. The action is centrally provided by an application, so the action can be used by all applications if they support actions.

    In the future, d.velop platform apps will provide various actions that will enable you as a process creator to easily connect e.g. third-party systems. 

    How can I use actions in the process?

    There is a new item for modeling to use actions in process modeling.

    You'll find the new item for performing an action soon in the palette when you model a process.


    You can easily add this item to the process.


    Select the step in the model to configure an action step.


    First choose an action. All actions provided within the environment (e.g. by scripts) are available.

    After choosing an action, the mandatory input parameters are automatically added in the Input parameters area. You can map the parameters to process variables or static values.

    Add optional input parameters manually via Add parameter (as before also for Services).

    If the action returns output parameters, you can access these parameters in the Output parameters area and map the values to a process variable respectively.



    All information is supplied without guarantee. Specified functions or dates are subject to change. We reserve the right not to publish certain features if they do not meet our quality standards.

    2023-10-16
  • Extension of the feature preview for the new operating concept
    user admin
    CategoryTasks and processes
    Publication

     


    New functions available soon

    Extension of document display for tasks with attachments in d.velop documents

    Soon you will be able to work more with the attachment of a task from d.velop documents (documents or dossiers) without losing the focus of the task. So that you can use the function, the feature preview for the new operating concept for the task management must be activated.

    For task attachments out of d.velop documents, the context actions for the associated item are displayed on the right side.

    When you select a context action or switch to the document properties, for example, you now navigate within the preview. So the actual task remains in focus. 

    But you can still fully navigate to the item in d.velop documents by using the arrow ().

    If the attachment of the task is a dossier out of d.velop documents, the dossier content will be displayed. You can work with the dossier content without leaving the task.

    In addition to navigating within the dossier, you can also directly save new items in the dossier using drag & drop.

    You can also work with the sidebar. For dossiers in d.velop documents, you will find the dossier structure in the sidebar, for example. 

    This allows you to easily navigate through the dossier structure until you have gathered the necessary information to complete the task.


    All information is supplied without guarantee. Specified functions or dates are subject to change. We reserve the right not to publish certain features if they do not meet our quality standards.

    2023-10-16