Skip to content

Commit 639fc39

Browse files
author
espen.steen
committed
Wrote readme.md
1 parent 283060d commit 639fc39

1 file changed

Lines changed: 72 additions & 6 deletions

File tree

readme.md

Lines changed: 72 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,50 @@
11
# CRMScript Fetcher
22

3-
CRMScript Fetcher is a GUI application that can download CRMScripts from your SuperOffice installations, and create them as files
4-
and folders on your local PC.
5-
3+
CRMScript Fetcher is a GUI application that can download CRMScripts from your
4+
SuperOffice installations, and create the scripts as files within a
5+
folder structure on your local PC.
66

77
## About
8-
Info about CRMScript Fetcher here
98

9+
CRMScript Fetcher is useful for downloading your current scripts into a local repository,
10+
which you then may use for pushing into Github/Gitlab etc. with your preferred git client.
11+
12+
When fetching, it will create the following two folders inside your chosen directory:
13+
- Scripts
14+
- Triggers
15+
16+
Inside these folders, all scripts/triggers will be created as files with a .crmscript file extension.
17+
For Scripts, it will also recreate the exact same folder structure as the one you have in SuperOffice.
18+
19+
## Important to know
20+
21+
The software is provided "as is" without warranty of any kind.
22+
All responsibility of the usage of CRMSCript Fetcher lies on you.
23+
24+
> :warning: **When fetching, all files and folders within the "Scripts" and "Triggers" folders WILL be
25+
> deleted if they are not present in SuperOffice.**
26+
>
27+
>
28+
> This also includes files/folders that weren't created by CRMScript Fetcher to begin with, so it is not
29+
> advisable to put anything there manually.
30+
>
31+
> However, files/folders within the root directory will not be deleted, so you can put stuff there safely.
32+
33+
It is also worth noting that, technically, all files and folders within the Scripts and Triggers folders will be deleted and recreated
34+
every time you click fetch, even if you have done no changes in SuperOffice.
35+
36+
It is up to you to consider if this poses any problems for your usage.
37+
Based on my own usage, git will not detect these deletes/rewrites as changes.
38+
39+
#### About the temp backup folder
40+
Each fetch will create a "temp" folder where your current local Scripts/Triggers
41+
folders are moved into, as a failsafe in case the fetch fails during its execution.
42+
The temp folder will be deleted again upon completing the fetch, so you shouldn't normally see it.
43+
44+
If something does go wrong, you can move the contents of temp back into the root folder.
45+
46+
Sometimes, the temp folder might not be deleted correctly due to Windows permission
47+
errors. Usually this works itself out by running the fetch again.
1048

1149
## Prerequisites
1250

@@ -19,11 +57,39 @@ Info about CRMScript Fetcher here
1957

2058
## Getting Started
2159

22-
Head over to Releases on the right hand side to download.
60+
1. Head over to Releases on the right hand side to download.
61+
62+
63+
2. Unpack the zip file wherever you want
64+
65+
## How to use
66+
67+
1. Open CRMScript Fetcher.crmscript in a text editor, and copy the contents.
68+
69+
70+
2. In your SuperOffice installation, create a new script and paste the contents.
71+
Give it an include name (e.g. "crmscript_fetcher") and a secret key (or just use the one generated).
72+
73+
74+
3. Run CRMScript Fetcher.exe.
75+
76+
77+
4. Click "Add tenant"
78+
- Tenant name: Friendly name of the installation
79+
- SuperOffice Service URL: For Online environments this will be something like
80+
https://online.superoffice.com/CustXXXXX/CS
81+
- Script include ID: Your include name
82+
- Script key: Your secret key
83+
- Local directory: Click Browse to pick your directory where the folders will be created.
84+
85+
86+
5. Click Save settings
87+
2388

89+
6. Click Fetch CRMScripts to fetch!
2490

25-
## Notes
2691

92+
All your tenant settings will be saved locally in the tenant_settings.json file.
2793

2894

2995
## Built With

0 commit comments

Comments
 (0)