[LIVECOPY-290] Exclude Node being protected (added to propertiesToIgnore) from Pushing master content change. Created: 01/Sep/21  Updated: 18/Oct/21  Resolved: 22/Sep/21

Status: Closed
Project: Live Copy
Component/s: None
Affects Version/s: None
Fix Version/s: 3.2.6

Type: Improvement Priority: Neutral
Reporter: Quach Hao Thien Assignee: Quach Hao Thien
Resolution: Fixed Votes: 0
Labels: VN-Implementation, cm-team-support, maintenance
Remaining Estimate: Not Specified
Time Spent: 3d 1.75h
Original Estimate: Not Specified

Issue Links:
dependency
depends upon LIVECOPY-283 Protect MultiValueField field Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Epic Link: Live Copy maintenance
Sprint: Content Mngmt 12, Content Mngmt 13
Story Points: 8

 Description   

By introducing a new enhancement in LIVECOPY-283, for specific field like MultiValueComposite or MultiValueSwitchable, which is a node contains nodes in JCR, when the field is protected, the node name will be added to propertiesToIgnore. That means the propertiesToIgnore could be used for node name beside property name.

The current logic of pushing master content change is EXCLUDED the operation for:

  • Properties, which is protected
  • Component, which is dropped reference
  • Page, which is dropped reference

Now we will want to exclude the Node name which is protected as well.

AC:

  • Field which is store in term of Node and node's name being protected will be exclude from Master content change operation.
  • To ensure that the push master change will not affected to MultiValueSwitchable, MultiValueComposite, or any field which has ability to change the quantity or structure in JCR

 


Generated at Mon Feb 12 02:27:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.