Bug - Multiple bugs and improvements in 3.26.4

[PDB]

We have identified a few minor bugs and potential improvements in the latest version of Eramba.

1. We have a custom translation file. Some new fields bug out when you use a custom translation. See examples below, but this is present on a lot of different pages.

2. On the ‘Security Policies’ page, it no longer seems possible to directly use a linked document—access now requires going through the Policy Portal. However, the option ‘Only specific groups’ doesn’t appear to work when a group is assigned as the document owner or contact; it only functions when an individual is selected. As a result, there currently doesn’t seem to be a straightforward way to make a document easily accessible to everyone in Eramba.

3. It’s not really a bug, but more of a nice-to-have. The new UI has a white layout, which requires a darker logo for proper contrast. However, the banners in both the policy portal and the email notifications are still dark, which makes the logo hard to see.

[sam]

Hello,

1. Going to Settings > Clear Cache should help resolve that issue.
2. I’m not sure I fully understand this part — could you please provide some screenshots? You can still access the old UI here: https://og.cloud.eramba.org (login: admin, password: alphanumeric1).
3. Yes, this will be reworked along with the portals.

Thanks for posting!

[PDB]

Hi Sam,

1. This doesn’t work for certain fields. The screenshots we provided are taken after we cleared the cache.

• Before you could hover over the field ‘Use the URL’ (‘Gebruik de URL’ in our translation) and could immediately acces the URL. This option is not available anymore.

• If you select the item and press on 'direct link, you only get a link to the policy portal. So it requires now the activation of the Policy Portal to access the document.

• We only want to make the item available for everyone that has an account in Eramba. We have three options to select in the item (e.g. 'Back-up & recovery policy): public, private and only for specific groups. We don’t want to make it public, because then the document is available for the whole world. Select ‘private’ and the document is not published on the policy portal at all. The last option is ‘only for specific groups’ and you get two options; for the document owner and the GRC contact (we translated these names, so we don’t know the default names). If you select a user (for example: John) in one of those fields, the document appears in the policy portal for that user. If you select a group (Department where John works) in one of those fields and the user is part of that group, the document doesn’t appear in the policy portal for that user. I could make a video and e-mail it if that would make it more clear.

3. Great!

[sam]

1. If you’re using translations, you’ll need to update your translation file. The new UI introduces additional fields, and I believe that’s what’s causing the issue.
2. Yes, we’re planning to implement this feature:
   Feature - New custom field type URL
   However, it wasn’t possible in the old UI either — clicking the URL just opened the view modal for the policy, where you could then access the link. This is still possible using the “View” action.
   
   
   
   
   
3. We weren’t able to replicate this issue on our end. If possible, please record a video demonstrating the problem.
   Also, make sure the policy you’re working with is published — this refers to the status field, not the Policy Portal Permission field.

[PDB]

Hi Sam,

1. We downloaded a new empty translation file and imported the existing data. Some fields that don’t translate or bug are present in the translation file, but don’t do anything. Some are not present. Perhaps worthy to mention: We are using the on-premise version of Eramba. I could share the translation file if needed.

2. Ah great! I just didn’t see this new button.

3. Completely my fault, I’m sorry for wasting your time. I realized I made a stupid mistake.

[sam]

Yes, please, send it to support so we can take a look.