Changelog 10.0
Key | Subject | Description |
|---|---|---|
ERA-9009 | Users can be excluded from participating in a process activity | As a modeler of a workflow model, I would like to be able to configure which users, groups and roles are excluded from participation in an activity, in order to implement business processes that have such requirements (for instance, processes where it has to be ensured that two different persons have to perform a certain action). Acceptance criteria:
|
ERA-9010 | Exclusions-configuration of a process activity is visible in REST-API | As an API user, I would like to know who was excluded from participation in an activity, in order to know why they did not receive a task resulting from that activity. Acceptance criteria:
|
ERA-9227 | Remove deprecated script API method "createEntry" in "History" class | BPM-Scripting API call "$.history.createEntry" was deprecated by a new method "$.history.addEntry". |
ERA-9301 | Read-only fields in scripting-API behave as such | As a modeler that writes scripts for process models, I would like to get clearer feedback from scripting-API which properties can be changed, and which are read-only, without having to check documentation for each field. Currently, the changes of all properties are possible in script, but the changes of the read-only properties are not persisted. Acceptance criteria:
|
ERA-9503 | HttpRequest object has a timeout property | As a model developer, I would like to set the timeout for an HTTP call by setting the timeout property of the HttpRequest object to the appropriate value. Acceptance criteria:
|
ERA-9530 | New objecttype right 'Share' provides control over who can share documents in a system | As a project modeler, I would like to control who can share an object type, in order to have better control over document access in a system. Currently, sharing right is bound to edit-right, thus everyone who can edit a document can also share it with other users. Acceptance criteria:
|
ERA-9576 | Additional icons are available for document and folder types | As a modeler, I would like to have more icons available for object types in a yuuvis RAD system, in order that users can better distinguish between them and associate them more easily with the designed purpose of an object type. Acceptance criteria:
|
ERA-9583 | It can be seen in which processes an object is being used | As a user, I want to see whether an object is used in an active process, in order to understand better the state of the object and processes relevant for it. Acceptance criteria:
|
ERA-9633 | Names of deadlines and delays can be localized | As a workflow user, I would like to have better understanding of process history when the process contains deadlines and delays. Currently, the history entries are technical and not translated into my language. Acceptance criteria:
|
ERA-9671 | Localized names of deadlines and delays are provided in task history | As a workflow user, I would like to have better understanding of process history when the process contains deadlines and delays. Currently, the history entries are technical and not translated into my language. Acceptance criteria:
|
ERA-9694 | Username of users that cannot be deleted is changed to unique value | As a system administrator, I would like to be able to reuse usernames that are no longer in active use, in order to be able to synchronize system with external identity providers. Currently, if a user has made changes on a document, it cannot be completely removed from a yuuvis RAD system (to preserve history of changes on objects). So, if a user X is active in system, leaves company and is deleted from company's identity provider, the username X becomes available in the identity provider system. Administrator can assign it to a new user, but then the synchronization with yuuvis RAD fails, since username is occupied and cannot be reused. Acceptance criteria:
|
ERA-9700 | The form editor shows technical names of fields and datafields | As a system modeler, I would like to see technical names of fields in form editor instead of neutral names, in order to be able to track fields over multiple user interface views more easily. For instance, in object-field overview, the technical names are shown. Acceptance criteria:
|
ERA-9742 | Users that are excluded from participating in a process activity are listed in API | As an API user, I would like to know who was excluded from participation in an activity, in order to know why they did not receive a task resulting from that activity. Acceptance criteria:
|
ERA-9772 | Users that are excluded from participating in a process activity are shown in management studio | As an administrator, I would like to know who was excluded from participation in an activity, in order to know why they did not receive a task resulting from that activity. Acceptance criteria:
|
ERA-9785 | Organization-Objects can be searched by Object-ID | As a workflow developer, I would like to find an existing organization object by its ID, in order to use it in my scripts (for instance, to set it as a performer). Acceptance criteria
|
ERA-9796 | Endpoint to set performers and exclusions | As an API user, I would like to have consistent use of HTTP methods, according to standards established by RESTful API, in order to build applications more easily. In particular, the existing endpoint to manipulate performers of a workitem uses PUT both to update an existing performer configuration (correct) and to replace the exisiting performer configuration (here, a POST would be better). Also, the PUT and POST methods should be extended to allow setting of all performer exclusion parameters that are available elsewhere in the API. Acceptance criteria:
|
ERA-9800 | Project definition with more object types than allowed cannot be deployed | As an administrator, I would like to be informed that I am attempting to deploy a project definition with more object types than allowed by licensing module, and that this is not allowed by the system. Acceptance criteria:
|
ERA-9803 | BPM scripting API has "Datafield" class | Acceptance criteria:
|
ERA-9822 | Performance of displaying of an object-field-configuration is improved | As a modeler, I would like that the view that contains field properties is loaded fast, in order to be able to switch views faster and consequently work faster. Currently, if an object type contains lots of fields, it takes several seconds to load the view. Acceptance criteria:
|
ERA-9927 | Script engine runs in strict mode | As a script developer, I would like that script engine runs in the strict mode in order to eliminate silent errors in scripts. Acceptance criteria:
|
OKTO-5953 | The setup of the rendition-plus is asking whether to activate the use of the OCR-Service for the text extraction | After the update of libraries to avoid security check issues: As an administrator, I will be able to activate the use of the OCR-Service for text extraction during the setup so that I do not have to configure it afterward. Acceptance criteria:
|
TUK-3125 | In the search dialog, the order of the object type groups can be changed | As a user, I want to be supported by a feature that prevents me every time scrolling down the search dialog to those object type groups that I can't see so that I can use their object types. Acceptance criteria:
|
TUK-3243 | The action 'Share' is only offered if the user has the new object permission 'share' but no more for the object permission 'edit'. (A-Team) | As a user with the object permission 'share', I want to get the object action 'Share' so that I can share the document with other users if necessary. Acceptance criteria:
|
TUK-3374 | It is possible to open a document file of the Microsoft Office format for viewing and editing via the O365 services | As a user, I want to be able to start the editing of a Microsoft Office based document file on the O365 platform so that I can work with other users on it. Acceptance criteria:
|
TUK-3415 | In the object details header an icon is indicating whether this object is or was part of an process | As a user, I want to see an indication of a focused object whether it is part of a process file in an active process so that I do not have to investigate with more effort. Acceptance criteria:
}
...
"processcount": 2
}
|
TUK-3496 | The Office 365 services are part of the setup | As an administrator, I want to be able to use the Office 365 services after the installation so that the users can preview Office files rendered by Microsoft Office sources, and to edit them on the Microsoft Office platform if the users possess an account for it. Acceptance criteria:
tenant:
id: Tenant-ID
secret: Tenant-Secret
provider-url: https://provider.prod.enaio.io/
host-url: https://host.prod.enaio.io/
working-dir: C:\\data\\office
recovery:
enable: true
|
TUK-3622 | A MS Office file including its versions can be previewed in the versions state including the compare mode | As a user, I want the versions view to support me with a preview of two versions containing document files of the format Microsoft Office that is based on the Microsoft O365 integration. Acceptance criteria:
|
TUK-3627 | The three labels for the list in the 'Hit list' widget can be configured | As a user, I want to be able to determine the object properties which should be shown as object title and description so that I can see this important information. Acceptance criteria:
|
TUK-3641 | The client supports the use of the O365 Dashlet without manual configuration and handles events well | As an administrator, I don't want to configure the client to use the O365 Dashlet if it is up and running so that I don't have to care about it. Acceptance criteria:
|
TUK-3662 | When the core-service the first time starts up a trial license based on a just generated GUID is created and activated | As the system responsible, I want the core-service when starting up to prepare an initial license file so that the system can be used as a trial system with a limited number of users so that the system directly can be used without contacting OS. Acceptance criteria:
|
TUK-3664 | The license management is offered by the core-service | As the system responsible, I want the core-service to offer a license service that controls the number of named and concurrent licenses as well as an expiration date so that the system can only be used as contracted. As a programmer, I want to be able to get the parameters of the activated license file, download the license file, and upload and activate a new license file via REST-WS endpoints. Acceptance:
|
TUK-3665 | A named user license can be assigned to a user via management studio | As an administrator, I will be able to assign and remove a named license to a specific user so that I can follow the requirements of my organization. Acceptance criteria:
|
The REST-WS interface offers a view that shows the license information, download the saved license file, and upload a new one | As an administrator, I will be able to get information about the activated license, download this license file to send it to my sales contact and upload and activate a new license file. Acceptance critereria:
| |
TUK-3668 | The client informs a concurrent user if no login is possible because no further concurrent license is available | As a user, I want to be informed about the situation that no more concurrent licenses are available if I cannot log in this case. Acceptance criteria:
|
TUK-3670 | The gateway login page informs a concurrent user if no login is possible because no further license is available | As an administrator, who logs into the management-studio or the REST-WS interface I want to be informed about the situation that no more concurrent licenses are available if I cannot log in in this case. Acceptance criteria:
|