Questions & Answers:
Q: In 6.8 is there a workaround to not having dynamic chart markers? This becomes critical in the case of key risk indicators where we need to dynamically set the threshold line in graph based on the threshold value that is available at individual KRI level.
A: Average markers are anchored on the data and the only 'dynamic' option we have is the average line that moves according to the data.
Follow Up Q: Is it not possible with any other new chart option? I tried combination chart but since the primary and secondary y axis scales will be mostly different it doesn't really help.
Follow Up A: I would like to understand this better. Can we connect offline on this?
Q: Can reports embedded in a record, be exported via Mail merge?
A: No, not at this time. There are no new changes to Mail Merge with RSA Archer 6.8.
Q: Is this Internal References feature only applicable to Leveled Applications?
A: No, it is intended to replace leveled applications. It is only available on applications which contain one or more relationships to themselves.
Q: Is the inherited record permissions feature through an established parent/child relationship a default feature of establishing that relationship or what is required to enable that?
A: This requires an Inherited Record Permission field, setup as Restricted, and with fields selected through an internal reference.
Q: Is there a way to limit the number of child references?
A: Can you explain this further? (No follow up received.)
Q: Why does the internal reference use reduce the DF or API uses? Can you elaborate it?
A: In the past, you could not inherit permissions in this way and so alternative approaches had to be used to manage permissions and Data Feed and API were the common choices. Now you can build the configuration directly.
Q: How does this search ability benefit an RSA Archer user?
A: These enhancements provide much more flexibility and control to the reporting user. More details are available on the blogs published earlier this week on the Community as well.
Follow Up Q: Great! Thank you. Is this blog on the RSA Archer site? Where can I find the link?
Q: In case when self relationships are being viewed, can we add another relationship to other applications as well?
A: Yes! You can add a relationship from an app to itself, as well as include references to additional applications.
Q: What does it look like when also including other xref’d records? E.g. when you would also include control procedures that can potentially be related to different levels of the business processes application?
A: The additional relationships show up in line with the same level of data to which they relate, in a visually separate section/outline of the report.
Q: What happens if there's a circular reference creating a never-ending loop?
A: That is detected by the search, and the hierarchy build out is stopped at that point. When trying to expand past that level in Column - Hierarchical view, you get a message that says, "Circular reference found.".
Q: By adding a new user does it only add it to the level 1 record or to all records?
For example: If I were to have a new employee starting to the finance department and they need access to the Finance Policies and Procedures. If I add them there will they be able to see all procedures and policies or just the finance procedures and policies record 1 or all records?
A: If you are leveraging an inherited permissions field through an internal reference, a user added to a Level 1 record would be accumulated down to all child records.
Q: Does sort order impact which records are returned when limiting to a specific number of records to be returned?
A: YES! I forgot to mention that, thank you! The Results Limit is applied to the primary sort criteria.
Q: How does the user specify the desired results in a top n report? For example, how does the system know what the top values are? Is this done through sorting?
A: Yes, I failed to mention that. The Top N is applied to the primary sorting criteria.
Q: Does the targeted search allow you to do the lowest X % or records?
A: Yes! The Top N is applied to the primary sorting criteria. If you sorted something ascending (i.e. smallest to largest), the Top N would return your lowest values and ties.
Q: How does system determines the top # and % of records? Is there any way I can specify the fields as per my requirement?
A: This is based on the primary sorting criteria.
Q: We have a scenario, where we have 2 Xref fields to the same app - one as primary ref and other as secondary ref. In 6.7, we need to bring in some fields from primary ref alone into the referring app. We use and A2A datafeed. Unfortunately, in the source report, we can only have one relationship selected, and it returns fields from both the references, and we are forced to configure XSLT for selecting only the primary ref records. There is no option to filter the primary ref alone, as filters on XRef fields are not dynamic. What could help is - a) option to filter on XRef fields dynamically - only pull up the relevant reference records where the XRef app records = Records linked in primary ref field. OR b) option to have a true column-flat format report, where there's a single row for each XRef record - so, we can have a filter in the datafeed based on other conditions.
A: Let's have a call/email. Reach me at: <email removed>
Q: I think I missed something. Is that 'top' value assessing a filter that is set? The sort that is defined?
A: Yes, the primary sorting criteria is used.
Q: How can the x and y axis values be configurable? ie: high risk was presented on the demo on the right... what if i want high to be the far left?
A: The position cannot be configured, although you can use the sorting options on the search configuration page.
Q: In drill down reporting can we change the color of the chart on the second level of the report? Currently it takes the color from the parent level.
A: Currently, there is no way to do that.
Q: In drill down report (3 levels) down, on clicking on the third level and then opening the record, the records shown don’t consider the second level filter and only considers the final level (3rd level) that was chosen. Is this the expected behavior?
A: Yes, it is. You can use the sunburst chart to drill through into second level. To clarify further, when you are on the lowest level the behavior of the click is to Drill Through, irrespective of the chart type.
Q: What happens if you had two Sorts selected?
A: In 6.8, only the primary sort is considered. Please add an RSA Ideas record for expansion to other sorts.
Q: What about apply the filtering on risk rating that used qualitative approach?
A: Results Limits work against the common field types: Date, Numeric, Text, Values List, etc.
Q: We are new to RSA Archer where can I look for more content on how to use this tool for IT Risk and Compliance?
A: Leverage your account management and sales engineering teams, as well as the RSA Link Community.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.