Skip to Main Content
ARIS - SHARE YOUR IDEAS
How can we make ARIS better?
ADD A NEW IDEA

FILTER BY CATEGORY

ARIS Extension: Risk & Compliance

Showing 49 of 1319

Extend ARIS report API to collect info from several ARCM objects

Current ARIS report API can collect info just from one ARCM object types (e.g. from risk). If you need to collect info from several object types e.g. from test cases and related risks, controls and test definition you have to iterate test case and...
Radek Docekal 22 days ago in ARIS Extension: Risk & Compliance 0 Future consideration

Button "Add screenshot" as evidence document

Very often, a simple screenshot is completely sufficient as an evidence document. An "add screenshot" button that easily allows to take and add a screenshot as evidence documentation would be a great improvement to usability. Embeddable code is re...
Jörg Neves Bliesener 5 months ago in ARIS Extension: Risk & Compliance 3 Future consideration

Request for Enhancement - Comment History in ARCM

Dear R&D Department, We have recently discovered a limitation in the ARCM systems related to comment history. Currently, it is possible for users to override comments written by other people on task notes, and there is no history of the previo...
Rakan Omar 6 months ago in ARIS Extension: Risk & Compliance 2 Future consideration

ARCM Reporting

Standard Reports for Stakeholders/Authorities should be available with all attributes (List Risk, Controls, Tests, Audits ... - sorting/deleting/config the report/columnes should be possible by user. Export to Excel as is.
Thomas Berner about 2 months ago in ARIS Extension: Risk & Compliance 1 Future consideration

GDPR requires all systems to be able to delete record when requested to do so by the customer

It is required by law (GDPR) that when a customer wants their data to be deleted from a system it should be possible to do so (deletion by design). Currently this is not possible in ARCM. We, as xxx, want this functionality to be implemented.
Sylvia Groenbos over 1 year ago in ARIS Extension: Risk & Compliance 3 Future consideration

Design Risk Report based on Risk Tree

Currently the closest thing to a Risk report is the weak point analysis. This report uses the activity/ function objects as a starting point. To get insight in the Risk framework it would be usefull to have a report that uses the Risk framework as...
Hanneke Loefs 6 months ago in ARIS Extension: Risk & Compliance 0 Future consideration

Testing Risk Workflows

When a risk is added and all controls and controltasks are set up it needs to be tested, wether the workflows are running the right way - and wether the right persons get the right tasks. Same on Auditworkflows necessary.
Thomas Berner 2 months ago in ARIS Extension: Risk & Compliance 1 Future consideration

Risk Sync and deactivation of objects

Risk administration can be done wether on single risks or on full sync with Architect. As riskmanagers adminstrate there risks and are no ARIS administrator they should be capable of deactivate attributs or objekcts via single sync.
Thomas Berner 2 months ago in ARIS Extension: Risk & Compliance 0 Future consideration

Risk Administration

The administration of risk, control and controltask should be more userfriendly like the ARIS satelite modelling. Add new controll opens column to describe the control, add new controltask adds new CT and so on. In background the BCD is createtd (...
Thomas Berner 2 months ago in ARIS Extension: Risk & Compliance 0 Future consideration

Simple interface for risk assessment by the Risk Owner.

The current risk assessment interface has too many tabs with excessive information when evaluating each risk assessment by the Risk Owner. We propose simplifying the interface while still having the option to expand the information. The data that ...
Ariel Carrizo 7 months ago in ARIS Extension: Risk & Compliance 1 Future consideration