I’ve reported a similar issue in September (which is still not fixed), and it seems SailPoint doesn’t want to check that all document scopes can be selected in the UI. We have to create for each missing scope a ticket and wait a couple of months.
I thought solving a class of problems at once would be more efficient than solving the same problem over and over again, with all the overhead of detecting the issue, reporting it, creating an internal ticket, discussing about the priority, planning it over months, working on the issue, testing the issue, deploying the issue, informing the customers that the issue is resolved, the customer testing the issue themselves.
Well… I guess we won’t be informed when the issue is resolved.