[MKTAUT-42] Salesforce form fields remains selected in twin col select field Created: 21/Oct/19  Updated: 18/Nov/19  Resolved: 18/Nov/19

Status: Closed
Project: Marketing Automation
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Improvement Priority: Neutral
Reporter: Antonín Juran Assignee: Oanh Thai Hoang
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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: Forms export
Sprint: Add-Ons 25
Story Points: 2

 Description   

Steps to reproduce:

  1. Save salesforce connector and AcceptedEventRelation form on the Marketing form dialog 
  2. Select and save CreatedById, CreatedDate, EventId fields in the next step (twin column field)
  3. Open again the Marketing form dialog and save another form
  4. Open again the Marketing form dialog and select salesforce connector and AcceptedEventRelation form => fields CreatedById, CreatedDate, EventId are preselected on the twin col field

 

AC:

Try to create 2 components in one pages and see if both components always get the same value fields from twin column.

  • If 2 components get different value, that's we can close ticket as won't fix
  • If not, that's a bug. you need to create another ticket to fix it


 Comments   
Comment by Oanh Thai Hoang [ 15/Nov/19 ]

Hi ajuran, chuong.doan, nguyen.phung. I tried create 2 components and select different twin column value for salesforce. I don't see they have the same value when rendering 2 components inside 1 page. Please help me to check and I can close as won't fix

Comment by Antonín Juran [ 18/Nov/19 ]

oanh.thai I confirm the behaviour as you described, the ticket could be closed as won't fix.

Generated at Mon Feb 12 10:11:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.