Great idea

Not sure which Workflow you're trying to export, but if it's GL Journals or AP Invoices, you can export these from BPM to Excel using the 'Manage Workflow Rules in Spreadsheet'. That makes it even easier to maintain than a BIP/OTBI report, as you can make the changes to the rules in the spreadsheet and upload it back…

Agreed - this is a key gap in auditing options - would particularly want to be able to audit changes to the domain names that BI Publisher reports can be sent to.

It is noted that functionality in BI Publisher differs from OTBI, as in the OTBI there is no equivalent of the 'Allowed Email Recipient Domains' control exists at the time of raising this Idea. Please support the Ideas raised by others around controlling the domains that OTBI reports can be emailed to.

Agreed, though this is just one access controls issue that organisations will face when using seeded Roles. The solution is to customise the Roles, including reducing BI access.

Agreed, this would be very useful to be able to easily export.

I agree that PII will likely be the same company by company, but there may be exceptions. For example, I know of organisations in the UK that would count supplier names as PII as some of their suppliers are sole traders/partnerships and whether customer details are PII will depend on whether they sell directly to…

I agree that it should be possible to mask PII data. However, I'm unclear on what the request is - is it to: a) have an option to automatically mask out certain data in fields specified by Oracle themselves (such as already exists for bank accounts), which is dependent on Oracle identifying the fields, but easy for…

I would also completely agree with this idea. Without these reports it is difficult to provide assurance over the reports that are used for key controls. At the moment it is not possible to know what the change to the report was, nor the history of changes to the report - this means that each report that is used for a key…

Thank you for sharing this.

Agreed - this is exactly what I do every time I create a bespoke BI Publisher Data Model.