[MGNLCAMPU-31] Make campaign workspace and nodeType configurable. Make merge split and publish action successMessage overridable. Created: 09/Jun/15 Updated: 08/Jul/15 Resolved: 08/Jul/15 |
|
| Status: | Closed |
| Project: | Campaign Publisher |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Thanh Pham | Assignee: | Evzen Fochr |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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: |
| Description |
|
SelectCampaignFieldDefinition: make workspace and nodeType as configurable fields |
| Comments |
| Comment by Jaroslav Simak [ 15/Jun/15 ] |
|
thanh.pham why do you need custom node types? What is the usecase please? |
| Comment by Thanh Pham [ 16/Jun/15 ] |
|
jsimak |
| Comment by Jan Haderka [ 16/Jun/15 ] |
|
Why can't you store those extra properties in existing node type? There are no restrictions to that. |
| Comment by Thanh Pham [ 08/Jul/15 ] |
|
@all: we use campaign app directly and move all new features of change container module to campaign app. Now, this ticket is invalid. |