SYMPTOM:
When a user executes a document in Strategy Web 9.4.1 in Express Mode, the correspondent document cache in the Intelligence Server previously created by a cache update subscription is not hit, even if the user is set as the recipient of the subscription. Instead, a new cache is created in the Intelligence Server.
STEP TO REPRODUCE:
1. In Strategy Web, log into Strategy Tutorial project.
2. Create a simple document (it can be an empty one) and set it to run by default in Express Mode. Call it “Test_document”.
3. In Strategy Developer, log into the project source as Administrator and create a user called “Test_user”.
4. Grant “Test_user” all privileges.
5. Create a cache update subscription for “Test_document”. Set “Test_user” as the recipient and “Express XML” as the delivery mode:
6. Execute the subscription. A document cache is created:
7. Log into Strategy Web as “Test_user” and execute “Test_document”. The existing document cache is hit:
8. In Strategy Developer, edit “Test_user” and uncheck Common Privileges -> "Execute Transaction" privilege:
9. Log into Strategy Web as “Test_user” and execute “Test_document”. The existing document cache is not hit anymore and a new document cache is created:
CAUSE:
The Strategy Web user who executes the document does not have "Common Privileges" -> "Execute Transaction" privilege.
Please also note that the issue only happens with Express Mode. Using other view modes in Strategy Web 9.4.1 does not generate the issue.
ACTION:
This is a known issue with Strategy 9.4.1 which has been fixed in Strategy 10.5.
WORKAROUND:
Granting "Common Privileges" -> "Execute Transaction" privilege to the Strategy Web user solves the issue.
