[MGNLPN-311] Reimplement new availability rules to work in browser or detail Created: 08/Aug/16  Updated: 22/Aug/16  Resolved: 12/Aug/16

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3

Type: Story Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLPN-322 Configuration of action availability ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Component P13N
Sprint: Kromeriz 56
Story Points: 5

 Description   

New Availability rules might work with item id's instead of elements so we don't need to have special rules for page editor and others for the browser.



 Comments   
Comment by Milan Divilek [ 12/Aug/16 ]

Deprecated info.magnolia.personalization.action.IsNoVariantRule is still used in config.modules.pages.apps.pages.subApps.browser.actions.previewAsVisitor.xml this causing migration test to fail
https://jenkins.magnolia-cms.com/view/Migration/job/int_migration-tests_5.4.x-to-5.5.x-branch/10/
https://jenkins.magnolia-cms.com/view/Migration/job/int_migration-tests_5.4-to-5.5.x-branch/177/

Generated at Mon Feb 12 06:36:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.