Ability to upload files into manual inspection
Completed
It would really help us if we could import our existing SOPs and files into manual inspection to make our new manual inspections easier to create.
-
Official comment
Hi Richard,
Can you describe in more detail? Do you mean to convert existing check list/ manual inspection into WATS, or the option to add files to a MI during execution?
Or maybe to upload support files to WATS as a repository?Comment actions -
Hi Richard,
We have the "Attach File" step type which might be what you need?
This step type allows upload of a single file during sequence execution. What kind of file types to upload can be set in the "File Type Filters".
The max file size is currently 4 MB, but may be increased if needed.
-
What we are trying to do is link our production SOPs into the test steps.
When you setup a test you have the option to attach media and set a PDF search string. Example below.
I have tried a number of different file link locations, for example, one based on our company network, one from a dropbox like location and one from a public internet URL.
The only one that I can get to work is the public internet URL which isn't ideal for storing company standard operating procedures.
Do you know if there is a way to link to files on a network drive and have them show up?When I try this currently I get the following error information when I execute the manual inspection:
Error - WATS Reporting
Message: An Exception occured in: /resources/mediahandler.ashx
StackTrace:
Exception {
Type="Virinco.WATS.WATSException";
Message="An Exception occured in: /resources/mediahandler.ashx";
Source="";
TargetSite="";
HelpLink="";
StackTrace="";
ItemType="0";
ItemId="00000000-0000-0000-0000-000000000000";
Exception {
Type="System.UriFormatException";
Message="Invalid URI: The hostname could not be parsed.";
Source="System";
TargetSite="Void CreateThis(System.String, Boolean, System.UriKind)";
HelpLink="";
StackTrace=" at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
at System.Uri..ctor(String uriString)
at System.UriBuilder..ctor(String uri)
at Virinco.WATS.Web.Dashboard.Resources.MediaHandler.GetUri(String url) in C:\agent\_work\26\s\2018.1\Web\wats-da\Resources\MediaHandler.ashx.cs:line 108
at Virinco.WATS.Web.Dashboard.Resources.MediaHandler.GetPropertyValues(NameValueCollection nvc) in C:\agent\_work\26\s\2018.1\Web\wats-da\Resources\MediaHandler.ashx.cs:line 56
at Virinco.WATS.Web.Dashboard.Resources.MediaHandler.ProcessRequest(HttpContext context) in C:\agent\_work\26\s\2018.1\Web\wats-da\Resources\MediaHandler.ashx.cs:line 34
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)";
}
} -
Unfortunately, working with network drives and UNC paths when using skyWATS does not work very well together. This is because the skyWATS servers would need to have direct access to the internal server which the UNC path resides to.
I assume using a public URL is not optimal because of security measures?
If the public URL is behind password protection (using Basic Authorization on the hosting web server), it is possible to specify the credentials (the "key" icon next to the Media URL text field). At least that would add some security for confidential/proprietary documents.
We are looking into providing a more native support for files, most likely in the shape of an internal WATS file repository. This is, however, still in the planning stages.
Please sign in to leave a comment.
Comments
9 comments