...
| Div |
|---|
|
On this page| Table of Contents |
|---|
| maxLevel | 2 |
|---|
| exclude | On this page |
|---|
| type | flat |
|---|
| separator | pipe |
|---|
|
|
Summary
The addRepository action can be used to add repositories to a plan. However, you must know the parameter fields that each repository uses and needs. Normally, the repository provider doesn't document this. However, they can be discovered. We have documented some examples already - see Examples for AddRepository Actionaction. If the repository type you want is not already documented or you are getting errors adding a repository (perhaps because the example is out of date), then you need to discover the fields needed. There are 2 ways to discover these fields.
- Using exportPlan on an existing plan that has been created manually through the UI with the repository you want to create through automation.
- Using browser tools to discover fields from the UI similar to how this is done in How to determine fields for addTask.
We will just document the first option here.
Steps using exportPlan
| Table plus |
|---|
|
| Step | Discussion |
|---|
| Find or create a plan using the UI that has a repository configured in the plan | Use whatever parameters settings that represent the repository you would like to create through automation. | | Go to the command line and run the exportPlan action on the plan and find the repository in the exported data | You are mostly interested in the fields that are exported. If there are more than 8 fields, you may need to convert some of the fields to use the fields parameter. |
|
Examples
| Include Page |
|---|
| Examples for AddRepository Action |
|---|
| Examples for AddRepository Action |
|---|
|