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.

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

Document Portability #1

Open
damacguy opened this issue Jun 14, 2024 · 1 comment
Open

Document Portability #1

damacguy opened this issue Jun 14, 2024 · 1 comment

Comments

@damacguy
Copy link

Currently it's impossible to collaborate on a work in progress with others, such as corporate security members and co-team members. The .jce document's save path is hard coded in the document making it both stationary and poorly transmittable or archivable.

If the compliance project needs to be revised and modified in, say, the next quarter or six months, then a new project has to be created, and the user only has something like the previous project's PDF to use to deselect previous unneeded rules and reapply modifications to remaining rules. The previous .jce document can't be reused by a different user, or even the same user unless it's returned to the exact same location it was previously.

Either all the required resources should be bundled inside the project file or the resources provided by the application and called on by the document should be stored in a conformed location (the computer or the user's Application Support folder).

@golbiga
Copy link
Collaborator

golbiga commented Sep 30, 2024

@damacguy apologies for not responding to this sooner. I only just noticed that issues were being sent here. So 1.4.0 was supposed to address the project portability issue, but if thats still not the case please let us know and we can see what we can do. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants