Stream: conformance
Topic: Forge 18.6 for STU3 (Colonia 2018 Edition)
Michel Rutten (May 09 2018 at 14:05):
Forge 18.6 for STU3 (Colonia 2018 Edition) is now available for download from https://fire.ly/forge/.
This release is a major Forge update that introduces some new features and also contains a number of usability, stability, and performance improvements.
Change log: https://simplifier.net/organization/firely/news/48
If you find a new issue or would like to submit a feature request, please contact us at forge@fire.ly.
Or come and meet us in Cologne!
Simone Heckmann (May 12 2018 at 10:18):
@Michel Rutten I'm having a weird problem here: While I'm editing a profile on List, Forge keeps flipping the type from List to Resource and I have no clue why this happens or how to prevent it. (Connectathon table 3)
Michel Rutten (May 12 2018 at 10:23):
Let me take a look
Simone Heckmann (May 12 2018 at 11:35):
Steps to reproduce:
Create a new profile from base Resource X
Add an invariant (Constraint)
Save profile
-> The base type in the differential has been flipped from "X" to "Resource"
Michel Rutten (May 12 2018 at 13:47):
Indeed, I can reproduce the issue and fixed the error in Forge development branch.
As this is a critical issue, I will soon publish a hotfix.
Please let me know if you discover any other issues/regressions!
Mounika (May 16 2018 at 09:32):
Hi @Michel Rutten I am facing issues while editing a profile in forge.
Capture12.PNG
Michel Rutten (May 16 2018 at 09:35):
Hi @Mounika, the 18.6 release has a couple of regression issues. I'm planning to fix the reported issues and publish an official update next week. Commercial customers have early access to hotfix binaries.
Michel Rutten (May 16 2018 at 09:36):
If you find any other issues, please let me know and I'll try to include a fix in the upcoming update.
Mounika (May 16 2018 at 09:37):
Okay @Michel Rutten Thank you
Mounika (May 16 2018 at 09:42):
Whenever I save a profile on Forge, the format of the saved file is not .structuredefintion.xml.
Michel Rutten (May 16 2018 at 09:43):
Do you mean the saved file contents is invalid? Or are you referring to the filename?
Mounika (May 16 2018 at 09:50):
file name
Michel Rutten (May 16 2018 at 09:54):
OK, got it. For now, you can simply rename the file yourself (or use Save As and change the filename).
I will revisit this logic and make sure to include the resource type name in the proposed file name (name.structuredefinition.xml).
Mounika (May 16 2018 at 09:59):
Okay
Michel Rutten (May 16 2018 at 10:07):
BTW this is just a convention that helps you browse folders on disk with mixed content. The FHIR spec does not specify any rules about filenames.
Thomas Tveit Rosenlund (May 24 2018 at 08:25):
I am having issues with the latest version of Forge 18.6. Suddenly I can not add extensions to datatype profiles. Forge-18.6-bug.JPG
Mirjam Baltus (May 24 2018 at 08:28):
Thank you for reporting that! We'll work on fixing it.
Michel Rutten (May 28 2018 at 09:53):
Hi @Thomas Tveit Rosenlund, thank you for reporting the issue. We've received some more user feedback on the latest release. This week I will focus on fixing reported bugs. I'm planning to publish a hotfix release by the end of this week. If you find any other issues, please report them ASAP.
David McKillop (Jun 01 2018 at 01:51):
Hi @Michel Rutten , I'm not sure if you've been notified of the issue where a change in a description to a field ie just add "Blah" (refer attached):
Type-error-20180601.JPG
and then save the change, results in the labels being changed from "RelatedPerson.dataelement" to "Resource.dataelement" eg "RelatedPerson.identifier" to "Resource.identifier" - refer to the attached files "before" and "after" for the changes resulting in the change to the text and then saving in Forge.
relatedperson-dh-base-before.xml
relatedperson-dh-base-after.xml
If you need any further information, let me know.
Cheers
D. Mc
Michel Rutten (Jun 04 2018 at 09:04):
Hi @David McKillop, thank you for reporting this issue. This is a regression bug that was introduced in the 18.6 release. We've already fixed the issue in the internal dev branch. I'm planning to publish an update this week.
Last updated: Apr 12 2022 at 19:14 UTC
