on 02-04-2014 4:37 PM
After giving a user Data Insight Analyst level access, if that user opens a rule they did not author, they see a "view only" version of the rule, (see below), with only "Validate", "Test", and "Close" options.
However, in the documentation, the high-level definition of the Data Insight Analyst group suggests that they should be able to edit rules, with no mention that they must "own" them.
I also verified that the Data Insight Analyst group has the "Manage Rule" right in the CMC, which seems like it should allow a DIA member to edit any rule.
When I test the same situation (rule created by another user), it can be edited under version 4.1. I could not find anywhere in the 4.2 release notes that security changed. Is this intended functionality, that users can only edit rules they create? When I give the "Admin rule" right to the Data Insight Analyst group, I am able to edit rules from any other user, but it doesn't seem like a user should have to be a Data Insight Administrator to edit an unapproved rule authored by another user.
Additionally, when I import a rule (from a project in version 4.2 to a project in version 4.2) it comes in without an approver listed and an error (see below), even though it was fully validated and had an approver listed in the original project.
Hi Hillary,
In 4.2 we added this behavior that you can only edit the rules that you have authored (or are part of a group that is authoring this rule). This is to make sure only specific intended users are editing specific rules. Otherwise users may edit each others rules without having permission to do so.
You are right that documentation needs to be clarified to add this "restriction".
I am not clear about the second part of your question regarding rule approver. Did you import a rule from project in version 4.2 to a project in version 4.2 in the same IS instance or different IS42 instances? Or did you mean source of the rule was project in IS4.1 instane?
Thanks,
Abhiram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that clarification, just from a usability perspective, I think users will be frustrated not being to edit others' rules (or not having any access level below system administrator that allows a power user to make edits), but I guess the solution is to customize the access level.
Regarding the approver error--this happens when I export a rule that validates and has an approve specified (from a version 4.2 project) into either a 4.2 project the same IS instance (so it is in "locked" status because it already exists in another project) but different project or in a different version 4.2 IS instance (same revision/service pack). It also happens when I export a rule, delete it, and then import it back into the same project that it was in previously.
I get that importing a version 4.1 rule into 4.2 might not have an approver, but it seems like an oversight that the approver does not export with 4.2 rules.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.