[MGNLPER-5] Derive app name and workspace automatically or through configuration Created: 26/Feb/18 Updated: 27/Apr/18 Resolved: 26/Apr/18 |
|
| Status: | Closed |
| Project: | Periscope |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Ilgun Ilgun |
| Resolution: | Done | 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)
|
| Epic Link: | Periscope back-end MVP |
| Sprint: | Basel 143 |
| Story Points: | 8 |
| Description |
|
Currently we have introduced WorkspaceToAppMap to capture the information of which workspace is bound to which app and subapp by default. However, currently there is no way for users to append that map and add/configure extra workspace -> app mappings. It is useful for instance when a user has a workspace named x but it's used in app y. Then we should be informed about it and therefore our action will find the correct app. Solution: We have introduce PeriscopeConfiguration and there it's possible to configure edge case scenarios like tours vs tourCategories. That being said, most of the time the automatic generation of PeriscopeAppDetail works. |