You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.
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).)
The text was updated successfully, but these errors were encountered:
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...
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ensure relationship handling behaves as expected with workflow enabled:
overwrite
), then assets assigned (REPLACE_ALL
)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).)
The text was updated successfully, but these errors were encountered: