Changelog 9.12

As a system operator, I want to be able to configure the maximum number of loop executions in order to be able to prevent the faulty implemented processes from consuming all computing resources of the system (such as, creating endless loops that will never free the execution thread it is being executed on).

Acceptance criteria:

• core-service has a new property to configure the loop count limit for all processes
• once the loop count limit is reached, the process will be suspended
• if a process is suspended due to the loop-count limit and then continued, the loop instance counter is reset (actually, modulo loop-count-limit is applied to it) and the loop continues the execution until the condition for exiting from the loop is met, or until the loop-count-limit is reached again.
• property can have positive value (that defines the limit), or -1 that turns off the limitation
• the default value of the property is 1000

To prevent the storage medium from filling up, logging should be configured by default so that it automatically deletes old files as soon as a certain limit has been reached.

Current behavior in other components:

core-service: maximum 10 files (100 MB per file)
service-manager: maximum 3 GB (100 MB per file)

Hints:

configuration won't be changed with an update but only with uninstalling and reinstalling designer

Final solution:

The maximum amount of archived files was set to 10.
The maximum size of a file was set to 100 MB.

As a user, I want to be able to fully use the keyboard to download a file so that I do not have to touch the mouse.

Acceptance criteria:

• After pushing 'Enter' if the action 'Donlwod document file' is focused the sub-dialog is opened with the focus on 'Original'.
• It is possible to navigate between both actions and to call the focused one by pushing 'Enter'.
• Pushing tab is not leaving the dialog (only the action and buttons of the dialog are reached)
• A 'Cancel' button is offered that can be reached by keyboard control and that can be called by pushing 'Enter'. After this, the sub-dialog is closed.
• Clicking outside the action menu closes it.

As an administrator, I want that the core-service is able to send emails via OAuth authentication of the M365 exchange online service.

Background: Microsft does not allow to use the SMTP authentication in the near future.

Acceptance criteria:

• It is possible to configure the OAuth authentication in the management studio:
  • Instead of a checkbox a selection list is offered for 'SMTP Authorization':
    • 'None' / 'Keine' offers no fields
    • 'With basic authentication' offers the current fields
    • 'With Oauth2 authentication for Microsoft Office 365' offers these fields:
      • Tenant ID
      • Client ID 
      • Client Secret
  • The core-service is using this configuration when sending emails.

As an administrator, I will be able to delete all objects in the recycle bin even if they are contained in a process file.

Acceptance criteria:

• It is possible to force the deletion operation for the recycle bin as it is possible in the delete objects operation. 

As a user, I will be supported by an aggregation of the month of the year as it is for the year itself so that I can drill down.

As an administrator, I will be able to configure the structure tree with the methods 'monthhistogram' as well as with 'yearmonthhistogram' so that the user can drill down the months as he is supported for the years yet.

Acceptance criteria:

• The methods 'monthhistogram' and 'yearmonthhistogram' can be used for a field type date and datetime in the structure tree configuration within the designer.
  • For the method 'monthhistogram' configuration, the client offers to drill down the months which are represented with 01 ... 12
  • For the methods 'yearmonthhistogram' configuration, the client offers to drill down the year and months which are represented with e.g. 2020-01 ... 2023-12
  • The modifier MONTH is introduced so a condition can be configured like this:
    "condition": "modified(YEAR)=2016 AND modified(MONTH)=08"
• This feature is documented here: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/319620140/Structure+Service+API+-+Folder+Structure 

As a user, I want to be supported by fewer clicks to open the user documentation.

Acceptance criteria: 

• A symbol with a '?' is shown beside the profil image. A click on it opens the user documentation in the language that is chosen.
• The main menu item is removed.
• The general section in the 'Application action' offers 'User documentation' as action.

As a programmer, I want to be able to get the supported signature types so that I can offer them to the users.

Acceptance criteria:

• There is a new signing service GET endpoint ../signing/info that returns the supported signature types and the default values for the email subject and body and other parameters which are configured in the file signing-yml:
  • the 'platform' with value
  • The 'supportedPlatforms' with the list ["docusign","adobesign"]
  • the 'maxsigners' with value
  • The default 'emailsubject'
  • The default 'emailmessage'
  • the 'signatureTypesEnabled' with these values (all are optional so the list can be empty) depending on the configuration in the signing-prod-yml file as documented here:
    https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/447184897/General+Configurations+for+Signing 

  • "signatureTypesEnabled": [
      "simple",
      "advanced",
      "qualified"
    ]

As the system responsible, I want the agent to prevent a session timeout on server-side so that a problematic disconnection with the Outlook and Microsoft Office Add-in can be avoided.

Acceptance criteria:

• the auth/info endpoint of the agent is listing the timeout
• the agent is resolving this timeout and pings 20% earlier than timeout (call to state endpoint check via devmode)

As an administration, I will be able to check whether my authentication configuration for a DocuSign account is well without requesting a signature for a first document file.
As an administrator, I want to be able to get the names of the configured signing providers for that DocuSign account so that I can configure the advanced and qualified signature types if needed.

Acceptance criteria:

• There is a new signing service endpoint ../signing/status that returns the signing configurations
  • which are configured in the file signing-yml:
    • the 'platform' with value
    • The 'supportedPlatforms' with the list ["docusign,adobesign"]
    • the 'maxsigners' with value
    • The default 'emailsubject'
    • The default 'emailmessage'
    • the 'signatureTypes' with values 'simple', 'advanced', 'qualified'
    • The accountName with which the Signing-Service is connected
    • The list of available signatureProviderName requested from 
    • If the configuration in the signing-prod.yml differs from DocuSign roviders info is given.
    • If the signing platform could not be accessed a specific error message is responded.

As a user, I want to be able to collapse the dashboard footer so that I can use the complete screen.

Acceptance criteria:

• An icon for collapsing the footer is offered on the right hand-side. After clicking on it the footer is removed and the icon changes to bring the footer back. After clicking on it the footer is back and the icon for collapsing the footer as well.
  • The setting is saved in the user settings.
• The footer is shown as less prominent.
• Hovering over the icon
  • the cursor is changing to a hand
  • a tool tip is shown: 'Hide dashboard configuration'/'Dashboard-Konfiguration ausblenden' / 'Show dashboard configuration'/'Dashboard-Konfiguration anzeigen'

As an administrator, I want to be supported with a piece of information for a configured cache that shows its usage in a medium so that I may know that I have to assign it.

Acceptance criteria:

• In the header of a set configuration section information shows the media that uses this cache or that no media is using it.

As an administrator, I want the synchronization storage operation to offer the following options so that current issues are avoided.

Acceptance criteria:

• If the metadata.xml file is missing after the synchronization it is re-created
• create them generally
• remove them generally