Motivation

There have been situations where end users need to review a sample, check relevant metrics and trigger a specific Action - for example "for a given sample, IF RapidQC has completed AND LOD>0 THEN submit "FinalAggregation" request in Pipeline's JMS queue". All of these actions to be done/initiated from within Tableau. Beyond visualization, Tableau can't do much else in terms of maintaining a "workflow" in DB, talking to external web-services like JMS and so on. That's why these job is being outsourced to our "SampleAnalyticsWorkflow" web-service - it's written in Scala so there is virtually no limit what tasks it can do for you. Tableau utilize it's UrlAction gadget to make a URL call to SAW service when appropriate.

...

"RequestFinalAggregation", "RequestTopOff", "RequestTopOffGroup", "RequestPoolCreated", "RequestSendToRework", "RequestHoldForTopOff", "RequestWaitingForNewRwData", "RequestReset", "RequestPCHoldForTopOff","RequestVolumeFinal"
1 encodes RequestFinalAggregation, 2 encodes RequestTopOff and so on

...

• requestType is the text-representation of this request (RequestFinalAggregation, RequestTopOff, etc)
• each individual item is a quintuple representing a single sample like this pdo:pdo_sample:data_type:user_name:parameters (greens are optional)

...

1. repeat it in the quintuple. Very wasteful.
2. standalone upfront URL-parameter "&user_name=JohnDoe" (economical and solid). Unfortunately as of now, Tableau's urlAction can't inject the username like this.
3. 2-step the cookie-dance (economical but might be tricky to use from within Tableau)
   1. record the user_name-cookie in the browser environment by calling this URL http://analytics:8090/api/setCookie?cookies=sampleAnalyticsWorkflow.user_name=JohnDoe (you only need to do this once for your entire session). Cookie/credentials are configured to expire after 10 minutes.
   2. and then make the main SAW call as many times as you need

...

Your environment (browser, OS, versions, etc) implicitly impose a limit on how long a URL can be. On top of that, our web-server provider (Akka-http) also impose limits on what URL-length is acceptable. (Currently akka-http limit is configured to 8194 8192 chars and can possibly be extended further but this should be done rather coservatively since it might lead to more memory consumption). So, best way to answer the question "What URL-size is safe to pass" is to try/test and see. Fortunately, if any truncation happens upstream the last EOURL parameter would definitely not make it and SAW-service can safely detect and report accordingly.

...

• step1: JOIN cognos.slxre_readgroup_metadata ON (pdo, pdo_sample, data_type) and lookup (research_project_id,collaborator_sample_id) for a given sample
• step2: send message to appropriate JMS queue

Environments

2 separate environments are provided

...