This documentation applies to when you want your query output to go to the CUNY Tumbleweeds server. This location allows for direct or scheduled download of output/report files.
NOTE - This documentation picks up at the point you are setting the query run schedule, Process Scheduler Request. For details on getting to this point see General Query Scheduling Documentation
If the File option is selected in the Process Scheduler Request window, the Format and Distribution drop-down lists appear. The file destination can be financial reporting or campus solution reporting.
Please see hc003 or FS001 in navigation bar then the output destination will be -
HC003 (HCM/CS reporting) | sftpcsout/PSQUERY_OUT/Baruch |
FS001 (financial reporting) | sftpfsout/PSQUERY_OUT/Baruch |
Notes from Abu and Dixon - we'll translate these into the documentation
From: Abu Kamruzzaman
Sent: Wednesday, September 17, 2014 3:57 PM
To: Tabassum Lodhi
Cc: Patrick Ackerman; Dixon Berry
Subject: Scheduling Query with tumbleweeds
Hello Everyone,
I found that both query name and control id require the BAR tag. Otherwise, the query are not picked up in tumbleweed.
If control id don’t have BAR tag, you will see the Run Status “No Success”. If query name don’t have BAR tag, you will see the Run Status “Success” but the result don’t seem to appear in tumbleweed. Instance: 4947287 didn’t transfer to the tumbleweed.
Check attached images for reference.
I deleted most of the output except CU_BAR_SR_00001-4947289.csv which is a output of instance:4947289
On Sep 17, 2014, at 5:36 PM, "Dixon Berry" <Dixon.Berry@baruch.cuny.edu> wrote:
Well, my job CU_BAR_PR_00035 does come through onto Tumbleweed. My control ID is BAR~ but my query name is still CU_BAR~.
Note that if you have two identical Control ID in the system, neither are reliable in my experience. It’s difficult to know if you two identical IDs, the only way I know to find out is to do “Instance 1” to “Instance 9999999” in the Process Monitor and look for duplicates.
Also, clicking on the green swirl arrow will show you the run history for the job.
From: Abu Kamruzzaman
Sent: Wednesday, September 17, 2014 5:52 PM
To: Dixon Berry
Cc: Tabassum Lodhi; Patrick Ackerman
Subject: Re: Scheduling Query with tumbleweeds
As long as BAR tag appears anywhere in the query name it will work. My query name that worked also has CU as prefix.
From: Dixon Berry
Sent: Thursday, September 18, 2014 9:16 AM
To: Abu Kamruzzaman
Cc: Tabassum Lodhi; Patrick Ackerman
Subject: RE: Scheduling Query with tumbleweeds
OK, nice to know. By the way, it seems logical that the sequence number of the most recent file downloads would be higher than previous downloads, but that is not always the case. Only the file write date is reliable.
ISSUE occurs to sending file to Tumbleweed for CU_BAR_SR_00035:
Query | CU_BAR_SR_00035 |
---|---|
Title/Description of the query | ADID Updates Active Term Range |
Pre-Condition |
|
Test Steps (Scenario 1) |
|
Test Steps (Scenario 2) |
|
Expected Results |
|
Unexpected Results/Recommendation | According to scenario 1 & 2, the process FAILED to progress as 'Success' for Today and que for 'Next day' as recurrence. NOTE that: this query (CU_BAR_SR_00035) was replaced from original cu_bar_sr_00035 and recopied to other users. The defects are still unknown and should recommend to generate CRM to Baruch Help desk for further assistance. |
The image shown recurrence below: