Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feedback F23 CAN (issue 4, TM): Section V Heading through LotAwardOutcome describesLot #375

Closed
valexande opened this issue May 2, 2023 · 2 comments
Closed

Feedback F23 CAN (issue 4, TM): Section V Heading through LotAwardOutcome describesLot #375

valexande opened this issue May 2, 2023 · 2 comments
Assignees
@csnyulas
Labels
type: feature request something requested to be implemented in a future release
Milestone
2023-05

Comments

@valexande
Copy link
Collaborator

Section V: The section heading shows the section going through LotAwardOutcome describesLot however some of the fields seem to go through Contract which is a bit strange as there is no sign of signature in this notice.
@csnyulas csnyulas self-assigned this May 3, 2023
@csnyulas csnyulas added this to the 2023-05 milestone May 3, 2023
@csnyulas
Copy link
Contributor

csnyulas commented Jun 6, 2023

Related to #408

@valexande valexande added the type: feature request something requested to be implemented in a future release label Jun 7, 2023
@valexande
Copy link
Collaborator Author

Currently the Contract concept was removed from F23 and F25 and will be mapped in next version of ePO (probably v4.0).

But even if the Contract would still exist, the TM and CM did not seem to have an actual problem, it was that in some cases the Property and Class path in the CM would start from epo:Contract and in others from epo:LotAwardOutcome.

We have harmonized the CM and this will be tackled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@csnyulas csnyulas

Labels
type: feature request something requested to be implemented in a future release
Projects
None yet
Milestone
2023-05
Development

No branches or pull requests
2 participants
@csnyulas @valexande