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
In old IGAMT, the co-constraints used to be exported with the segment (the OBX segment) but now, because it’s part of the message, not the segment, it comes out with the message and then context information. I think the context will confuse people. It would be nice if there was an export option to place the constraints table in the section of the associated segment.
As well, I don’t see an option for the alternate presentation of the co-constraints table. The narrow columns are hard to read. I like the alternate we came up with in old IGAMT
I like this better:
User Account
n/a
URL
n/a
To Reproduce
n/a
Expected behavior
n/a
Screenshots
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered:
Describe the bug
Email from Craig:
In old IGAMT, the co-constraints used to be exported with the segment (the OBX segment) but now, because it’s part of the message, not the segment, it comes out with the message and then context information. I think the context will confuse people. It would be nice if there was an export option to place the constraints table in the section of the associated segment.
As well, I don’t see an option for the alternate presentation of the co-constraints table. The narrow columns are hard to read. I like the alternate we came up with in old IGAMT
I like this better:
User Account
n/a
URL
n/a
To Reproduce
n/a
Expected behavior
n/a
Screenshots
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered: