Details:If you put a schema composer artifact in a controlled package the schema itself is not rendered read-only. It can still be changed even without checking out the package.The same problem with the locking mechanism of user security.

Steps to Reproduce:- Create a schema composer artifact in a controlled package- Check in the package- Try to update the schema in the schema composer- Notice that you can still change the schema although it should be read-only.

I got it working from within EA, so I know it's possible, but I don't remember if I did anything special.Just keep playing with the settings until something works I guess, or import from Word as suggested earlier.

This works for me to create html export from within EA. (make sure the export path exists)It still fails on the copy statement because of the invalid sharepoint url.You have to use an UNC format to get it to copy to sharepoint.

'' Script Name: ExportHTML' Author: Geert Bellekens' Purpose: Export the model HTML format. This script is suitable to be executed as a scheduled task in order to export the model'to HTML and publish it on a webserver or sharepoint site.' Date: 09/06/2016'sub main'dim repositorydim projectInterface'set repository = CreateObject("EA.Repository")'the path to put the inital export todim exportPath exportPath = "C:\Temp\EA\html"' the path where the exported model should be copied to (sharepoint location, or webserver)' in case of a sharepoint location make sure to use the UNC path (\\sharepoint-site\location\) ' and make sure that section of sharepoint not version controlled (no check-in/checkout)dim publishPathpublishPath = "http://sharepoint/sites/documentendatabank/EnterpriseArchitecture/SparxExports"