Clarizen Connector Advanced¶

The following items cover advanced options, tips, and links to other reference materials that may be useful for Clarizen integrations.

Clarizen Query Language (CZQL)¶

Clarizen Query Language (CZQL) can be used to enter manual query strings in place of using the wizard provided in Clarizen Connector Query. The general syntax of CZQL is provided below. For further information and examples, see Clarizen's REST API Reference Guide.

CZQL Query Syntax

SELECT field|groupingFunction[ASalias]|(Relation Query)

FROM EntityType

WHERE Condition

GROUP BY groupByFields

ORDER BY orderByFields[ASC|DESC]

LIMIT rows OFFSET startFrom

Bulk API¶

All activities provided in the Clarizen Connector (Create, Update, Query, Delete) use Clarizen's bulk API by default. Each bulk request is considered by Clarizen to be a single API request. So for example if the request returns 1,000 records, this is considered one request, not 1,000 requests.

Upsert Functionality¶

The Clarizen application does not support a native upsert functionality. As a workaround in Jitterbit, instead you can first set up a Clarizen Connector Query to pull back all IDs from the Clarizen instance. Then, depending on the results of the query:

• If the ID of the entity you want to upsert is within the query results, set up a Clarizen Connector Update activity to run. On the Update transformation, use a condition to filter out items you want to run in the Clarizen Connector Create operation.
• If the ID of the entity you want to upsert is not within the query results, set up a Clarizen Connector Create activity to run. On the Create transformation, use a condition to filter out items you want to run in the Clarizen Connector Update operation.

For further detail and examples of how to use Jitterbit to upsert data into Clarizen, see Upserting Clarizen Data with a Chain of Operations.

Outbound Messaging¶

Within your Clarizen instance, you can set up workflow rules and custom actions. This is similar to Salesforce Configuring Outbound Messages with Hosted HTTP Endpoints and similar steps can be extrapolated for the Clarizen application.

Design Patterns¶

The following design patterns may be useful for Clarizen integrations:

• Capturing Data Changes with a Harmony API or HTTP Endpoint

• Capturing Data Changes with File Sources

• Capturing Data Changes with Source Field Values

• Capture Data Changes with Table or File Changes

• Capturing Data Changes with Timestamp-based Queries

• Creating Single- or Multiple-Record Output

• Creating Transformation Iterator Dynamically

• Harmony Best Practices

• Linking Source or Target Records Using Shared IDs

• Looking Up Data During Runtime

• Looking Up Data Using a Dictionary

• Persisting Data for Later Processing Using Temporary Storage

• Persisting Inbound Data for Later Processing

• Processing Target Records Conditionally

• Running Next Operations Conditionally Using Operation Chains

• Set Up a Team Collaboration Project

• Set Up Alerting, Logging, and Error Handling

• Updating Multiple Targets from a Single Source Record

• Upserting Clarizen Data with a Chain of Operations