Skip to content

Commit 2ff3d02

Browse files
committed
Merge branch 'main' of https://github.com/swhitley/CLARiNET
2 parents e646599 + 6d92749 commit 2ff3d02

File tree

1 file changed

+43
-16
lines changed

1 file changed

+43
-16
lines changed

README.md

Lines changed: 43 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,14 @@
11
# CLARiNET
22
<img align="right" src="https://user-images.githubusercontent.com/413552/129500187-ea5a1947-16d2-46eb-ab48-2adc6553b6d8.png" width="50" />
3-
Deploy Workday Studio Integrations without Workday Studio.
43

5-
## WHY?
6-
You might be asking yourself, "Why load a CLAR file from outside of Workday Studio?"
4+
A Workday command-line interface (CLI) for working with Drive files and deploying Workday Studio integrations without Workday Studio.
5+
6+
## Drive Features
7+
- Upload files in bulk to Workday Drive. Load files for different Workday user accounts.
8+
- Send files to the Workday Drive Trash.
79

8-
Here are a few ideas. (Care to add to this list in the discussions?)
10+
## Why deploy CLAR files with CLARiNET?
11+
You might be asking yourself, "Why load a CLAR file from outside of Workday Studio?"
912

1013
- Distribute an integration to someone who is not a developer.
1114
- Enable an operations role to move an integration to production without requiring development tools.
@@ -20,33 +23,57 @@ Here are a few ideas. (Care to add to this list in the discussions?)
2023
5. You may need to install the [dotnet core runtime](https://dotnet.microsoft.com/download/dotnet/5.0/runtime).
2124
6. Optional: Download [Test.clar](https://github.com/swhitley/CLARiNET/blob/main/Test.clar) to try it out.
2225

23-
**Note:** CLARiNET calls an unpublished Workday API endpoint. Functionality is not guaranteed.
26+
**Note:** When uploading CLAR files, CLARiNET calls an unpublished Workday API endpoint. Functionality is not guaranteed.
27+
The Drive API is published and fully-supported by Workday.
28+
29+
## Uploading files to Workday Drive
30+
31+
- Ensure that a directory named `inbound` has been created alongside the `clarinet` program file. The directory will be created automatically when `clarinet` is executed.
32+
- Place each file in the inbound directory with the following file name format: {Workday User Account}\~{File Name}<br/>
33+
Example: swhitley\~MyExampleFile.txt
34+
- Enter `clarinet` on a line by itself. The application will prompt for all necessary information.
35+
- The `clarinet` command is **DRIVE_UPLOAD**.
36+
- Each file in the `inbound` directory will be uploaded to the drive for the appropriate Workday user account. The user account will be removed from the file name and the {File Name} will appear in Drive.
37+
- Once uploaded successfully, each file will be moved to the `processed` directory.
38+
39+
## Sending Drive files to the Trash
40+
- Create a comma-separated value (CSV) file with the following layout:<br/>
41+
{Workday User Account},{File Name},{Drive Document Workday ID (WID)}<br/>
42+
Example: swhitley,MyExampleFile.txt,8a8a350990e401003bb7a37564c10000
43+
- Place the file in the same folder as the `clarinet` application.
44+
- When naming the file, it will be convenient to include the word **trash**.
45+
- Enter `clarinet` on a line by itself. The application will prompt for all necessary information.
46+
- The `clarinet` command is **DRIVE_TRASH**.
47+
48+
Please note that a file is not deleted when sent to the trash. Files can be individually restored from the trash if needed.
2449

2550
## Loading a CLAR file to Workday
2651

2752
- Enter `clarinet` on a line by itself. The application will prompt for all necessary information.
53+
- The `clarinet` command is **CLAR_UPLOAD**.
2854
- If a single `.clar` file is found in the same directory, CLARiNET will automatically select that file for processing.
2955
- Run `clarinet --help` to view the available options.
3056
- Run `clarinet -w` to view the list of Workday environments and the associated numbers.
3157

32-
### Run CLARiNET from the command line using positional parameters:
58+
## Run CLARiNET from the command line using positional parameters:
3359

34-
* %1 CLAR File<br/>
35-
* %2 Cloud Collection Name<br/>
36-
* %3 Workday Environment Number (run `clarinet -w` to see the list of numbers)<br/>
37-
* %4 Tenant<br/>
38-
* %5 Username<br/>
39-
* %6 Encrypted Password (run `clarinet -e` to encrypt a password) <br/>
60+
* %1 CLARiNET Command: CLAR_UPLOAD, DRIVE_UPLOAD, DRIVE_TRASH<br/>
61+
* %2 Path or Path and File Name<br/>
62+
* %3 Parameters for the command. Enter the **Cloud Collection** name when performing a **CLAR_UPLOAD**. For other commands, defaults will be used<br/>
63+
* %4 Workday Environment Number (run `clarinet -w` to see the list of numbers)<br/>
64+
* %5 Tenant<br/>
65+
* %6 Username<br/>
66+
* %7 Encrypted Password (run `clarinet -e` to encrypt a password) <br/>
4067

41-
Example: `clarinet "C:\example_folder\Test.clar" Test 7 mytenant myusername AQAAANCMnd8BFdERjHoAwE/Cl+...G3Q=`
68+
Example: `clarinet CLAR_UPLOAD "C:\example_folder\Test.clar" Test 7 mytenant myusername AQAAANCMnd8BFdERjHoAwE/Cl+...G3Q=`
4269

4370
The entire list of parameters is not required. Prompts will appear for the parameters that are not included. These are all valid examples:
4471

45-
Example #1: `clarinet "C:\example_folder\Test.clar"`
72+
Example #1: `clarinet CLAR_UPLOAD "C:\example_folder\Test.clar"`
4673

47-
Example #2: `clarinet "C:\example_folder\Test.clar" Test 7 mytenant myusername`
74+
Example #2: `clarinet CLAR_UPLOAD "C:\example_folder\Test.clar" Test 7 mytenant myusername`
4875

49-
Example #3: `clarinet "C:\example_folder\Test.clar" Test`
76+
Example #3: `clarinet CLAR_UPLOAD "C:\example_folder\Test.clar" Test`
5077

5178
### Sample `clarinet` Run
5279
![image](https://user-images.githubusercontent.com/413552/129465336-0168f0e3-7e75-4309-83e1-8aebe9b9ae6e.png)

0 commit comments

Comments
 (0)