Jitterbit Harmony Evernote Update Notes Activity¶
Introduction¶
An Evernote update notes activity updates notes at an Evernote connection and is used as a target in an operation. After configuring an Evernote connection, you can configure as many Evernote activities as you like for each Evernote connection.
Create an Evernote Activity¶
An instance of an activity is created from a connection using an activity type.
To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an Activity Instance in Component Reuse.
An existing activity can be edited from these locations:
- The design canvas (see Component Actions Menu in Design Canvas).
- The project pane's Components tab (see Component Actions Menu in Project Pane Components Tab).
Accessing Menu Actions¶
Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity Actions Menu in Connector Basics.
Configure an Evernote Update Notes Activity¶
Follow these steps to configure an Evernote update notes activity:
Step 1: Enter Basic Information¶
-
Name: Enter a name to use to identify the Evernote update notes activity. The name must be unique for each update notes activity and must not contain forward slashes (
/
) or colons (:
). -
Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.
-
Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.
-
Discard Changes: After making changes, click Discard Changes to close the configuration without saving changes made to any step. A message will ask you to confirm that you want to discard changes.
Step 2: Review Data Schema¶
- Data Schema: The request and response data schemas for Evernote will be displayed. If the operation uses a transformation, the data schemas will be displayed again later during the transformation mapping process, where you can map to target fields using source objects, scripts, variables, custom values, and more.
The Evernote connector uses the Evernote SDK for Java. Refer to the SDK documentation for information on the schema fields.
-
Add Plugin(s): Plugins are Jitterbit- or user-provided applications that extend Harmony's native capabilities. To apply a plugin to the activity, click to expand this section and select the checkbox next to the plugin to be used. For additional instructions on using plugins, including details on setting any required variables used by the plugin, see Plugins Added to an Activity.
-
Refresh: Click the refresh icon
or the word Refresh to regenerate schemas from the endpoint. This action also regenerates the schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.
-
Back: Click to temporarily store the configuration for this step and return to the previous step.
-
Finished: Click to save the configuration for all steps and close the activity configuration.
-
Discard Changes: After making changes, click Discard Changes to close the configuration without saving changes made to any step. A message will ask you to confirm that you want to discard changes.
Next Steps¶
After configuring an Evernote update notes activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure an operation's operation settings, which include the ability to chain operations together that are in the same or different workflows.
Evernote update notes activities can be used as a target with these operation patterns: - Transformation Pattern - Two-transformation Pattern (as the first or second target)
Other patterns are not valid using Evernote update notes activities. See the validation patterns on the Operation Validity page.
To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.
When ready, deploy and run the operation and validate behavior by checking the operation logs.