Attach document to entity and store in SQL repository
PlannedAs a Solution Builder
I want to be able to add documents into a repository and interact with them as any other entity.
So That documents can be added on the fly from MAE, have attributes and relationships the same as types. An additional function in MAE to download file, and in BA to open file.
Benefits
- would be to allow the inclusion of documents at the time of modeling or later by the live end user.
- Backing up the repository would included all the files related to the repository and without the modeler having to know details of the final location of the files. Also avoids security issues with user access to file drives .
- Improved modeling and end user experience
- This opens up MooD to be used in multiple more solutions.
- Makes MooD solutions more flexible
- Simple example maybe a feedback form that allows the user to attach a document/ image.
- Attaching the file to an entity type allows the inclusion of a file but with all the added benefits of the attribute fields give to Types in MooD.
Acceptance Criteria
- Having an extra attribute added to a MooD Type which is a File/document.
- The file would be stored in the SQL database.
- A solution builder can 'attach' any file without having to explain what it is.
- The end user can 'Download' the file
- The end user can 'Add a file'
- A bonus maybe being able to extract the attributes that are embedded into all files into MooD fields so they can be displayed, searched, filtered etc (like all other MooD fields) but this is I expect a lot more work.
Customer / Originator
- It is hard to add a document to mood that can be later read my the user. I haven't used the Knowledge activation for a long time as it is painful.
- Currently the Knowledge Activation is hard to use and relies on knowing the location of the files, not just on the solution builders machine but also on a customers server maintained by a contractor. A solution builder I can't control which users have access to the files as it is controlled by final server host provided and user access permissions are completely unrelated to the users in the mood solution.
- I can't (last week) drop a document on a model that can be open again (which I think was possible).
Priority High
Aware I might be solutioneering here, but I do think it is a s simple as adding a extra 'Field Type' to Types that holds a file document (a BLOB in SQL?). Then all is needed is a couple of MAE Actions, one to download the file, and second to add a file (upload button).
-
Official comment
Thank you Alex, for your feedback. We recognise that Knowledge Activation is currently a hard component to use and it is within the roadmap to redesign the capability. We will take your suggestions and needs into consideration when this is undertaken, unfortunately it is not a quick thing to do, but I will keep you updated with progress.
Please could you raise the following as an issue with our Support so that they can investigate any potential regression in the current capability?
"I can't (last week) drop a document on a model that can be open again (which I think was possible)."
Kind regards
Jessica Robinson
Product Owner
Comment actions
Please sign in to leave a comment.
Comments
3 comments