cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Thin Client Markup - Save to Vault

Thin Client Markup - Save to Vault

The markup save to vault is only available in the thick client, not the thin client. It would be extremly benefical if this was also available in the thin client. 

6 Comments
ihayesjr
Community Manager
Status changed to: Archived

Thank you for posting the idea. As the Thin Client is meant to be only a Read-only client that doesn't require a license, it will not be able to save any data back into Vault.

smilinger
Advisor

As I know, in the thin client we can update the visualization attachment of a file, isn't it already some type of saving-data-back-into-Vault? Unless submitting a job to the vault server does not require a license, because as far as I know this DO require a vault license. Is it some type of exception that you made specifically for this feature?

 

If you can make an exception for that then I strongly suggest that we also make an exception for saving markup in thin client either. Because I strongly agree with @graham.harrison7M6HM that it would be extremely beneficial if this was also available in the thin client.

ihayesjr
Community Manager

@smilinger 

The Thin Client isn't performing the operation to create the visualization file. It is triggering it for the Job Queue so a Job Processor will pick it up, create the visualization file, and check it in.

ihayesjr
Community Manager
Status changed to: Under Review
 
smilinger
Advisor

@ihayesjr 

I think triggering a job needs a vault license, at least from a vault API perspective, which kind of violates the assumption that thin client only need a read-only license that disallows saving data back into Vault. And technically it is saving data back into vault, as a result.

ihayesjr
Community Manager
Status changed to: Future Consideration
 

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea