Skip to content
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.

Relationship loading with workflow enabled #19

Open
1 of 2 tasks
cmgrote opened this issue Aug 24, 2018 · 2 comments
Open
1 of 2 tasks

Relationship loading with workflow enabled #19

cmgrote opened this issue Aug 24, 2018 · 2 comments
Labels
enhancement New feature or request

Comments

@cmgrote
Copy link
Contributor

cmgrote commented Aug 24, 2018

Ensure relationship handling behaves as expected with workflow enabled:

  • asset not in dev glossary: asset is updated by glossary (overwrite), then assets assigned (REPLACE_ALL)
  • asset already in dev glossary: asset is updated by glossary (overwrite), then assets assigned (REPLACE_ALL)

(In both cases, would expect the end result to be the same: glossary asset as-defined in XML, assigned assets the complete list that was used for replacement (no more, no less).)

@cmgrote cmgrote added the bug Something isn't working label Aug 24, 2018
@cmgrote
Copy link
Contributor Author

cmgrote commented Aug 28, 2018

May actually be a bug in Information Server -- seems to behave inconsistently depending on whether workflow is enabled or not, and whether an asset is currently in the development glossary or not...

@cmgrote cmgrote added enhancement New feature or request and removed bug Something isn't working labels Oct 12, 2018
@cmgrote
Copy link
Contributor Author

cmgrote commented Oct 12, 2018

May actually be working now... Need to check on optimisation, though: are we only traversing and comparing those items that have a state in the workflow (ie. not all items that simply have a dev glossary RID)?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant