-
Notifications
You must be signed in to change notification settings - Fork 4
Writing Element Docs
On this page
Before you start, gather the information that you'll need in one place so you can easily refer to it. Here's a link to a Google Form that stores info about each element.
-
Record the element key: Call
GET/elements/keys
and search for the name of the element. -
Use the element key to get the Id. Call
GET /elements/{keyOrId}
and locate theid
at the top.Note You need the id from production, so if the element is in a different environment you can skip this step, but you'll need to run it later.
-
Record the image link. Call
GET /elements/{keyOrId}
and locateimage
. -
Export the element to gather more information.
-
Import the element and make sure that you:
- Change the Element Key to something like
docsElementname
. - Import all resources.
- Change the name of the element.
- Record the authentication type (top-right corner of Authentication section).
- Open Configuration and record the name and Configuration Key for anything not hidden on the UI.
- Open Event Configuration and record the event type.
- Record whether the element supports Transformations. Unless it's a storage type element, the answer is probably yes. You can confirm by finding
transformationsEnabled
in the payload fromGET /elements/{keyOrId}
. - Record the Bulk information:
- Upload or download: Look in the
GET /elements/{keyOrId}
payload forbulkDownloadEnabled
andbulkUploadEnabled
. - Cloud Elements or Native: Ask a developer
- Record the URL for the API docs. Do a search like "elementName API documentation".
- Record rate limit info - Search their docs or Google for any info on rate limits. It can be actual numbers or just a link.
-
Check out the master branch.
git checkout
-
Make sure that it's up to date.
git pull origin master
-
Create a branch with the name of the element.
git branch elementname
-
Check out the branch you just created.
git checkout elementname
-
Open atom or whatever editor that you're using.
atom .
-
Create a folder in docs>elements called the name of the element. If the element has two words, add a space (
adobe-sign
). -
Open _elementTemplate, and then copy all of the files in the folder to the one you created in the previous step.
If you know which authentication type or event type that the element supports, you can choose the appropriate setup, authenticate, and events files. Otherwise, just copy them all and delete the ones that you don't need.
- In Cloud Elements, find the element and authenticate an instance.
- Use the information you gathered earlier and Dashlane to complete any configuration fields.